m (→For advanced users: more information about QEMU images used by SDK for windows) |
(→For advanced users only: more information about QEMU images used by SDK for windows) |
||
| Line 140: | Line 140: | ||
</ol> | </ol> | ||
| - | == | + | == How to create QEMU images used by SDK for windows == |
The QEMU images for SDK on Linux could be built from the [http://meego.gitorious.org/meego-os-base/image-configurations/trees/MeeGo1.1/SDK kick start file] by using mic-image-creator tool (command to run the mic-image-creator could be found in each ks file). Ideally the images are host platform independent. However, due to the booting time and some other issues with kqemu, minor changes were done on the images obtained from ks file so that they could boot up successfully on Windows. Suppose you have had a raw image, say abc.raw, built from kick start file in hand, below are the changes needed: | The QEMU images for SDK on Linux could be built from the [http://meego.gitorious.org/meego-os-base/image-configurations/trees/MeeGo1.1/SDK kick start file] by using mic-image-creator tool (command to run the mic-image-creator could be found in each ks file). Ideally the images are host platform independent. However, due to the booting time and some other issues with kqemu, minor changes were done on the images obtained from ks file so that they could boot up successfully on Windows. Suppose you have had a raw image, say abc.raw, built from kick start file in hand, below are the changes needed: | ||
| Line 152: | Line 152: | ||
4, unmount the image | 4, unmount the image | ||
sudo umount /mnt | sudo umount /mnt | ||
| + | |||
| + | == Known issues about QEMU image and workarounds for them== | ||
This page describes how to install and configure the MeeGo 1.1 SDK on your Windows development system.
Contents |
| File | Description | Size | MD5SUM |
|---|---|---|---|
| http://download3.meego.com/MeeGoSDK/1.1/meego-1.1-sdk-beta-online-installer.exe | MeeGo SDK Windows online installer | 14MB | 0d1f92c90232641f8b638727886e6874 |
| http://download3.meego.com/MeeGoSDK/1.1/meego-1.1-sdk-beta-offline-installer.exe | MeeGo SDK Windows offline installer | 54MB | be824c3e19e849aa69582689f65eaafa |
.exe file and follow the prompts to install the SDK.C:\MeeGoSDK_1.1; replace <target_name> with the name of the target (for example, meego-handset-ia32-w32-1.1).Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application.
In "Project setup" dialog, choose "meego-handset".
Notice: The kqemu could only be used on 32-bit Windows. 64-bit Windows could not work with kqemu. You can not use emulator on 64-bit Windows. Use real device instead.
Download package from http://wiki.qemu.org/download/kqemu-1.4.0pre1.tar.gz
Get the kqemu.inf and kqemu.sys files from above package
For Windows XP system, right click the kqemu.inf file and select "install".
For Windows 7 or Windows Vista system, edit the kqemu.inf file to do below changes, and then right click the kqemu.inf, select "install".
[DefaultInstall.NT] --> [DefaultInstall] [DefaultInstall.NT.Services] --> [DefaultInstall.Services] [Uninstall.NT] --> [Uninstall] [Uninstall.NT.Services] --> [Uninstall.Services]
Start the kqemu manually. Select Start > All Programs > Accessories, click right mouse button over Command Prompt, and select "Run as administrator". In Command Prompt, run the following command:
net start kqemu
You need to start kqemu again after you reboot the system.
Get to the menu: Tools -> Options -> Projects -> MeeGo Device Configurations. Click "Add" button to add a runtime for emulator. Set "Device type" to "MeeGo emulator"; set "Authentication type" to "Password"; set "Username" to "root"; set "Password" to "meego".
Click "Projects" again on the left side. Select "Run" in the MeeGo Build/Run box at the top. Make sure that the "Device configuration" is set to "MeeGo Emulator". This will ensure that QEMU is started when you run your application. You can now launch the QEMU MeeGo emulator. Click the "Start Meego emulator" icon near the bottom left corner of Qt Creator (circled in red in the screenshot below).
After QEMU starts, click the "Run" icon to run your application. Qt Creator will package and deploy your application to QEMU and start it on the target. You can see the window of your application in QEMU.
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.
The QEMU images for SDK on Linux could be built from the kick start file by using mic-image-creator tool (command to run the mic-image-creator could be found in each ks file). Ideally the images are host platform independent. However, due to the booting time and some other issues with kqemu, minor changes were done on the images obtained from ks file so that they could boot up successfully on Windows. Suppose you have had a raw image, say abc.raw, built from kick start file in hand, below are the changes needed:
1, mount into the image
sudo mount -o loop,offset=512 abc.raw /mnt
2, edit /mnt/usr/sbin/meego-dm to add "sleep 5" to solve #10412: mouse udev not ready before starting X server while running handset image on QEMU windows
sleep 5 # new added line shopt -s execfail
3, edit /mnt/boot/extlinux/extlinux.conf to add kernel option "intel_idle.max-cstate=0" to solve #10149: Home screen can't show up after starting emulator from Qt Creator on Windows7 32bit
append ro root=/dev/sda1 vga=current intel_idle.max-cstate=0 quiet
4, unmount the image
sudo umount /mnt