| Line 1: | Line 1: | ||
| - | '''This page under construction at this moment. Contact Bob if you have questions. ETA: | + | '''This page under construction at this moment. Contact Bob if you have questions. ETA: 1am PDT''' |
== MeeGo SDK 1.2 Preview (with Tablet) == | == MeeGo SDK 1.2 Preview (with Tablet) == | ||
| Line 9: | Line 9: | ||
The MeeGo SDK 1.2 is scheduled for release near the end of May. This release if provided as an early preview of the upcoming features, with more in development. The following updates have been since the MeeGo 1.1 SDK release: | The MeeGo SDK 1.2 is scheduled for release near the end of May. This release if provided as an early preview of the upcoming features, with more in development. The following updates have been since the MeeGo 1.1 SDK release: | ||
| - | * | + | * [http://labs.qt.nokia.com/2011/03/01/qt-creator-2-1-0-released/ Qt Creator 2.1.0]; built with Qt 4.7.2 |
| - | + | * Improved Qt Quick support | |
* Support for tablet images, toolchain and QEMU image. | * Support for tablet images, toolchain and QEMU image. | ||
| - | * Additional Tablet APIs and supporting libraries | + | * Additional [http://wiki.meego.com/index.php Tablet APIs] and supporting libraries |
* Graphical installer for Linux | * Graphical installer for Linux | ||
| - | * MeeGo UX Components ( | + | * [MeeGo UX Components] (very early version) |
* UI Guidelines for tablet released | * UI Guidelines for tablet released | ||
| Line 30: | Line 30: | ||
Any reasonably modern IA hardware. For Windows-based systems, the graphics and CPU virtualization are limited and a faster system may be necessary to use the virtual machine with software rendering. | Any reasonably modern IA hardware. For Windows-based systems, the graphics and CPU virtualization are limited and a faster system may be necessary to use the virtual machine with software rendering. | ||
* Systems known to work: Intel Core 2 Quad CPU, Q8200, i5 or i7 processor-based systems. | * Systems known to work: Intel Core 2 Quad CPU, Q8200, i5 or i7 processor-based systems. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | + | '''Software:'''[[br]] | |
| + | Windows XP w/SP3 and Windows 7 (32-bit systems can run virtual machine. 64-bit systems can use SDK but will need a device to run/debug)[[br]] | ||
| + | Ubuntu 10.04, 10.10 (''not KUbuntu''; Fedora 13, 14 (32-bit and 64-bit systems supported)[[br]] | ||
| + | See also: [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support MeeGo SDK Host OS Support page].[[br]] | ||
| + | '''Filesystem:''' [[br]] | ||
| + | The MeeGo SDK should be installed on a hardlink-capable filesystem (Unix file systems or NTFS. FAT filesystems are not hardlink-capable and not supported.)[[br]] | ||
| - | * | + | === Notes / Known Issues ===[[br]] |
| - | + | * In Windows, the virtual machine (QEMU) relies on kqemu to provide CPU virtualization support. On some machines this does not work. If you have trouble, please see [http://wiki.meego.com/SDK/Docs/1.1/Troubleshooting#QEMU_SDK_Errors troubleshooting].[[br]] | |
| - | + | * A bug in package dependencies makes uninstalling the SDK in KUbuntu remove critical system files. KUbuntu is not supported at this time. | |
| - | + | * When uninstalling, everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed. | |
| - | + | ||
| - | * | + | |
| - | * | + | |
| - | + | ||
| - | == Download and setup the MeeGo SDK == | + | === Download and setup the MeeGo SDK === |
<ol> | <ol> | ||
This page under construction at this moment. Contact Bob if you have questions. ETA: 1am PDT
Contents |
This tutorial describes how to use the MeeGo SDK 1.2 Preview. It contains support for the recently released tablet images.
The MeeGo SDK 1.2 is scheduled for release near the end of May. This release if provided as an early preview of the upcoming features, with more in development. The following updates have been since the MeeGo 1.1 SDK release:
The following related SDK documentation is useful for getting familiar with the application development lifecycle:
Additional applicable, up-to-date, generic MeeGo development information can be found at:
Hardware Any reasonably modern IA hardware. For Windows-based systems, the graphics and CPU virtualization are limited and a faster system may be necessary to use the virtual machine with software rendering.
Software:br Windows XP w/SP3 and Windows 7 (32-bit systems can run virtual machine. 64-bit systems can use SDK but will need a device to run/debug)br Ubuntu 10.04, 10.10 (not KUbuntu; Fedora 13, 14 (32-bit and 64-bit systems supported)br See also: MeeGo SDK Host OS Support page.br Filesystem: br The MeeGo SDK should be installed on a hardlink-capable filesystem (Unix file systems or NTFS. FAT filesystems are not hardlink-capable and not supported.)br
=== Notes / Known Issues ===br
| File | Description | Size |
|---|---|---|
| http://apollo.jf.intel.com/tablet/sdk/installer/meego-sdk-1.2-preview-installer-full-tablet.exe | MeeGo SDK Windows installer | 1.5G |
.exe file and follow the prompts to install the SDK.Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application.
In "Project setup" dialog, choose "meego-tablet".
"Shadow build” should be disabled before build an app. To do that, select “Projects” button in the left side of Qt Creator, and uncheck “Shadow build” in “Build Settings”.
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).
Note: You can also start the Qemu from MADDE terminal. For that you need to go to Start > Programs > MeeGoSDK > MADDE Terminal. In the terminal type:
mad list
to see the runtime and target names, and then type:
mad remote -r <runtime> poweron
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.
How to SSH into QEMU Image
Anytime MeeGo is running in QEMU, you can use SSH to connect to the image from another terminal on the host system.
$ ssh meego@127.0.0.1 -p 6666
Two user accounts are available in the MeeGo images:
User: meego Password: meego
User: root Password: meego
If user failed to connect to MeeGo image through ssh, please refer to item 9 of trouble shooting to check the sshd daemon in client.
The performance of QEMU emulator
Two factors impacts the emulator's performance most:
The kqemu module requires the host windows system to be 32-bit; the graphic acceleration requires the host to have powerful hardware graphic acceleration. The best performance could be achieved if both factors run well. If neither of above is available, the emulator will be extremely slow.
Suppose that the graphic card on host is not tha powerful, one way to improve UI performance is to alter the UI program not to use opengl. Below are the steps:
$ ssh meego@127.0.0.1 -p 6666 $ su $ vi /etc/xdg/autostart/meego-ux-daemon.desktop #remove the "--opengl" option $ exit
sudo zypper ref sudo zypper install utfs-client sudo zypper install mad-developer
rpm -i mad-developer-2.0-2.1.i586.rpm
You need to install Debugging Tools for Windows for debugging apps with simulator.