MeeGo wiki - User contributions [en]

SDK/Build MeeGo SDK for Windows

2011-06-14T07:51:43Z

Maxayu: /* MADDE */

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''Prerequisites'''
* [http://www.microsoft.com/ Windows OS (XP/Vista/7)]
* [[SDK/MeeGo SDK for Windows|MeeGo SDK for Windows]]
* [http://www.microsoft.com/express/Downloads/#2008-All Visual Studio 2008]
* [http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe Qt for Open Source on Windows (VS2008) - Earlier than Qt Creator 2.1.0]
* [http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.2-vs2008.exe Qt for Open Source on Windows (VS2008) - Qt Creator 2.1.0 or later]
* [http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi Debugging Tools for Windows (dbg_x86)]

Note: In case of build failure, please make sure webkit is mentioned inside <code>$QTDIR/mkspecs/qconfig.pri</code> file in the <code>QT_CONFIG</code> list, if it is not there, add it at the end of <code>QT_CONFIG</code< list, e.g.:
QT_CONFIG += webkit

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in (Due to attica is not supported).

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

5. Build jom to generate jom.exe

Fetch the source code of jom from http://gitorious.org/qt-labs/jom.

Extract jom.tar.gz and run the below commands under the directory of jom in ''Qt Command Prompt''.

>qmake
>nmake

Copy .\bin\jom.exe to %TARGET_LOCATION%\bin

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Some dist files can be found at http://www.iki.fi/too
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

You need to build it on Linux OS.

''' - Pre-Build'''
* Download source code of each package into $HOME/cross-build/src
** mpc, binutils, gcc, gdb
** http://build.meego.com/project/show?project=devel%3Atools%3Asdk%3Ahost%3Atoolchain%3AMeeGo%3A1.2%3ASource
** gmp, mpfr, zlib, expat
** http://build.meego.com/project/show?project=Trunk
** libiconv
** You need to download it from its official website.
** Extract each tar ball into a separate folder and apply all patches. For instance,
$patch -p1 -i ../gcc44-hack.patch
* Download sysroot and Linux Toolchain into $HOME/cross-build/i386-w32
** Download sysroot of meego-core-ia32-1.1.2
** http://download3.meego.com/meego-core-ia32-madde-sysroot-1.1.20110106.1139-fs.tar.gz
** Extract it into $HOME/cross-build/i386-w32/sysroot. The following folder will be under the this directory,
** bin, boot, dev, etc, ..., usr, var
** Download Linux Toolchain
** http://download3.meego.com/meego-sdk-i586-toolchain-1.1-w32_i686.tar.gz
** Extract it into $HOME/cross-build/i386-w32/build-target. The following folder will be under the this directory,
** bin, i586-meego-linux-gnu, include, lib, libexec, share
* Download build script into $HOME/cross-build
** http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh
** Modify the corresponding line in the script
target=i586-meego-linux-gnu
i586-meego-linux-gnu should be the folder name which is under 'build-target'
gmpv=gmp-4.3.1
mpfrv=mpfr-2.4.1
...
gdbv=gdb-7.1
Each package should be the folder name which is under 'src'
HOME=/home/user
HOME should be your home directory
PARAL="-j8"
8 indicates 2 * Number of CPU, i.e., 4 processors now. Change it according to actual case.

'''FAQs'''

In line 98, when building zlib, remove 'rc' if error occurs.
AR='i586-mingw32msvc-ar' \

''' -Build'''
$cd /path/to/cross-build
$./i386-toolchain-w32-meego.sh

''' -Post Build'''

Compress the build result into meego-toolchain.tar.gz
cd i386-w32
mv tools meego-toolchain
tar czf meego-toolchain.tar.gz meego-toolchain

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==
Source code of IFW can be downloaded from: http://qt.gitorious.org/qt-labs/installer-framework

Check the document in the source tree on how to build it.

You'd better build a static IFW, and you'll need to build static Qt for it.

===Build static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

[[Category:SDK]]

SDK/Docs/1.1/Getting started with the MeeGo SDK for Windows

2011-04-28T14:36:20Z

Maxayu: Undo revision 37450 by Sulamita (talk): The change should be for MeeGo 1.2 SDK, not for MeeGo 1.1 SDK. Thanks!

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

This page describes how to install and configure the MeeGo 1.1 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [[SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support|the support page]].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.1.2/meego-1.1-sdk-update-installer.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>54MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system. This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Use Qt Creator to develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

=== Configure Qt Creator to work with real devices ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

== Known issues about QEMU image and workarounds for them==
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

==Other known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

File:Meego-sdk-installer-comp.png

2011-04-20T08:32:54Z

Maxayu:

File:Master.png

2011-04-20T08:31:44Z

Maxayu:

SDK/Docs/1.2/MeeGo SDK 1.2 Preview

2011-04-11T08:36:43Z

Maxayu: /* MeeGo SDK 1.2 Preview (with Tablet) */

== MeeGo SDK 1.2 Preview (with Tablet) ==
This page describes how to use the MeeGo SDK 1.2 Preview. It contains support for the recently released tablet images.

MeeGo applications can be written using Qt (a rich C++ application framework) or Qt Quick (a Javascript-like declarative language). The MeeGo SDK includes Qt Creator IDE with GUI builder to enable streamlined development. It is currently available for use on Linux or Windows workstations as shown below. The MeeGo SDK creates a virtual environment on your workstation that replicates direct development on a MeeGo OS-based system [http://meego.com/developers/meego-application-development-cycle (More...)]

=== Prerequisites ===
'''Hardware''' <br>
* Any reasonably modern IA hardware. For systems where the graphics or CPU virtualization are limited a faster system will be needed to use the virtual machine.
* Systems known to work: Intel Core 2 Quad CPU, Q8200, i5 or i7 processor-based systems.

'''Software:'''
* 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)
* Fedora 12, 13 (14 very soon); Ubuntu 10.04, 10.10 (''not KUbuntu'', see note at bottom); (32-bit and 64-bit systems supported)
* See also: [[SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support|MeeGo SDK Host OS Support page]].

'''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.)

=== Download and Install ===
Follow the links below to install the SDK
* '''[[SDK/Docs/1.2/MeeGo_SDK_1.2_Preview_for_Windows|Instructions for Windows]]'''
* '''[[SDK/Docs/1.2/MeeGo_SDK_1.2_Preview_for_Linux|Instructions for Linux]]'''

=== SDK Features and Supporting Information ===
This version of the SDK is provides a preview of the following features:

* [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.
* Additional [[SDK/MeeGo_UX_Features|MeeGo UX Features]] and supporting libraries
* Graphical installer for Linux
* [[MeeGo_UX_Components|MeeGo UX Components]] (early version)
* [http://meego.com/sites/all/files/users/admin/meego_touch_ui_v1.2.pdf UI Guidelines] for tablet development

=== Further Information ===
The following related SDK documentation is useful for getting familiar with the application development lifecycle:
* [http://meego.com/developers/meego-application-development-cycle MeeGo Developer Story]
* [http://apidocs.meego.com/1.1/core/html/index.html MeeGo API], [http://apidocs.meego.com/1.1/platform/html/index.html Platform API]
* [[SDK/Docs/1.1/Creating_Hello_World|Qt Development: Creating Hello World]]

Additional applicable, up-to-date, generic MeeGo development information can be found at:
* http://meego.com/developers
* [[SDK/Docs/1.1]]

=== Notes / Known Issues ===
* '''KUbuntu is not supported at this time'''. Uninstalling the SDK in KUbuntu removes critical system files. See [https://bugs.meego.com/show_bug.cgi?id=14925 bug #14925].
* 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 [[SDK/Docs/1.1/Troubleshooting#QEMU_SDK_Errors|troubleshooting]].
* When uninstalling, everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed.
* QEMU does not launch in Ubuntu 10.10 with some old kernel versions. Need to be 2.6.35.25 or newer. See [https://bugs.meego.com/show_bug.cgi?id=10075 bug #10075]

SDK/Docs/1.2/MeeGo SDK 1.2 Preview

2011-04-11T08:36:21Z

Maxayu:

== MeeGo SDK 1.2 Preview (with Tablet) ==
This page describes how to use the MeeGo SDK 1.2 Preview. It contains support for the recently released tablet images.

MeeGo applications can be written using Qt (a rich C++ application framework) or Qt Quick (a Javascript-like declarative language). The MeeGo SDK includes Qt Creator IDE with GUI builder to enable streamlined development. It is currently available for use on Linux workstations as shown below. The MeeGo SDK creates a virtual environment on your workstation that replicates direct development on a MeeGo OS-based system [http://meego.com/developers/meego-application-development-cycle (More...)]

=== Prerequisites ===
'''Hardware''' <br>
* Any reasonably modern IA hardware. For systems where the graphics or CPU virtualization are limited a faster system will be needed to use the virtual machine.
* Systems known to work: Intel Core 2 Quad CPU, Q8200, i5 or i7 processor-based systems.

'''Software:'''
* 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)
* Fedora 12, 13 (14 very soon); Ubuntu 10.04, 10.10 (''not KUbuntu'', see note at bottom); (32-bit and 64-bit systems supported)
* See also: [[SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support|MeeGo SDK Host OS Support page]].

'''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.)

=== Download and Install ===
Follow the links below to install the SDK
* '''[[SDK/Docs/1.2/MeeGo_SDK_1.2_Preview_for_Windows|Instructions for Windows]]'''
* '''[[SDK/Docs/1.2/MeeGo_SDK_1.2_Preview_for_Linux|Instructions for Linux]]'''

=== SDK Features and Supporting Information ===
This version of the SDK is provides a preview of the following features:

* [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.
* Additional [[SDK/MeeGo_UX_Features|MeeGo UX Features]] and supporting libraries
* Graphical installer for Linux
* [[MeeGo_UX_Components|MeeGo UX Components]] (early version)
* [http://meego.com/sites/all/files/users/admin/meego_touch_ui_v1.2.pdf UI Guidelines] for tablet development

=== Further Information ===
The following related SDK documentation is useful for getting familiar with the application development lifecycle:
* [http://meego.com/developers/meego-application-development-cycle MeeGo Developer Story]
* [http://apidocs.meego.com/1.1/core/html/index.html MeeGo API], [http://apidocs.meego.com/1.1/platform/html/index.html Platform API]
* [[SDK/Docs/1.1/Creating_Hello_World|Qt Development: Creating Hello World]]

Additional applicable, up-to-date, generic MeeGo development information can be found at:
* http://meego.com/developers
* [[SDK/Docs/1.1]]

=== Notes / Known Issues ===
* '''KUbuntu is not supported at this time'''. Uninstalling the SDK in KUbuntu removes critical system files. See [https://bugs.meego.com/show_bug.cgi?id=14925 bug #14925].
* 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 [[SDK/Docs/1.1/Troubleshooting#QEMU_SDK_Errors|troubleshooting]].
* When uninstalling, everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed.
* QEMU does not launch in Ubuntu 10.10 with some old kernel versions. Need to be 2.6.35.25 or newer. See [https://bugs.meego.com/show_bug.cgi?id=10075 bug #10075]

SDK/Windows

2011-04-11T08:35:39Z

Maxayu:

== Download and use the MeeGo SDK for Windows==
* Latest [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the MeeGo SDK for Windows==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Meetings/20110406 Weekly

2011-04-07T02:09:17Z

Maxayu: /* Windows port (Max) */

= MeeGo SDK Weekly Meeting 20110406 =

This document contains status update of 20110406.

== Conventions of this document ==

* AP: = Action point agreed on this meeting
* yyyymmdd AP: = Action point agreed on previous meeting
* yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
* yyyymmdd AP DONE: = Action point done
* yyyymmdd AP CANCELLED: = Action point cancelled
* AGREE: = Item that has been agreed by the team
* POSTPONED: = Agenda item postponed from last meeting
* OLD: = Info from previous meeting (delete during the meeting)

== Status ==

=== SDK Program (Veli) ===

* Nokia changes...

==== Features (Ville) ====

=== Architecture (Bob) ===

(Meetings held weekly, as needed)

* http://wiki.meego.com/SDK/Architecture

Topics for future meetings:
* How to speed up MeeGo SDK
** Install (reduce size, target/sysroot management)
** Deploy/debug (QEMU acceleration, deploy w/o packaging, etc)
* rsync: Using QEMU files for sysroot
** http://wiki.meego.com/SDK/Sysroot_extension
* Release process (discussion started)
* Windows builds (server - http://bugs.meego.com/show_bug.cgi?id=11762, process)
* How to identify the installed MeeGo SDK version (registry key, file, gconf)

* March 30th Meeting
** Maurice: Qt Creator 2.2 review
** Fathi: sysroot "sliming" scheduled. Fathi sent an email status.
** Edmondas: QEMU use for sysroot

Covered in past weeks (Resolutions here: http://piratepad.net/qqICWdiYLl )
* Thurs 20th Meeting
** Package group - list of devel packages in sysroot
*** Study on http://wiki.meego.com/SDK/Packages_group
** Qt Creator rc1 promotion and QA

* Thurs 13th Meeting
** Accomodate 3rd party libraries in addition to sysroot on Windows and Linux
** Feature 10949 - [FEA] Make the installation of MeeGo SDK for Linux easier http://bugs.meego.com/show_bug.cgi?id=10949

** AP: Add minutes to: http://wiki.meego.com/SDK/Meetings (Bob) DONE.

=== Releasing (Fathi) ===

* feature freeze - bug fix only
** exceptions: Toolchains and Qt simulator
* hardfp toolchain into MeeGo Trunk
** SDK toolchain to update/promote
** AP: ks files to update - new images (Fathi)
** AP: update madde configuration for ARM toolchain (Fathi)
* Full toolchain upgrade to 1.2 is on the way for all architectures IA32/ARM softfp and hardfp
** Pending windows toolchain integrated - Windows SDK is using 1.1 toolchains - Use 1.2 now (Max)
* AP: Qt Simulator to review and promote (Fathi)

=== Windows port (Max) ===

* Preview 7 has been released
* AP: ARM hardfp toolchain should be provided by Al
* AP: Al to create a wiki page about the windows build server

=== Mac OS X port (David) ===

* David was not present

=== Toolchains (JuhaK) ===

* Proposing to properly configure the sdk toolchain to use cloog library, which it currently doesn't. Using cloog will enable the graphite loop optimizer in gcc.
* Proposing updates to the MeeGo 1.3 devel:toolchain build dependency packages (mpfr, gmp, cloog) and to configure the arm toolchain to use cloog too. This has been disabled because of some failures a long time ago.
* arm glibc (>= 2.12) build problems solved last week

=== Documentation (Taru) ===

* Taru Laine will be on holiday from 15 to 25 April.
* The agenda for this week's documentation status meeting is here: http://wiki.meego.com/SDK/Documentation/MeetingMinutes/20110406#Agenda
** This week the aim of the meeting is to go through the status of each content area in the http://wiki.meego.com/Documentation_Backlog_for_MeeGo_1.2 and see if there are any blocks or open issues that prevent progress on a specific task.
* Work on Linux setup instructions will start next week. Fathi Boudra has an action point of assigning a member of his team to create draft instructions based on MeeGo 1.1 SDK documentation. After that, Taru will go through the instructions during week 17.
* New MeeGo 1.2 SDK features in Bugzilla needed for creating instructions for developing with MeeGo chroot and Xephyr. Bob Spencer has an action point on this.
* Draft content for MeeGo API reference documentation and Glossary is available.
* Open issues:
** Which performance testing tools are supported by MeeGo 1.2 SDK?
** Installation/packaging instructions for OBS - are these included in the developer library?
** Sample applications: can the feature be reassigned?

=== QA (Juha) ===

* All QA reports at http://qa-reports.meego.com/
* Feature status :
** Released :
*** total 1
*** test case exists 0
** Resolved :
*** total 13
*** test case exists 7
** Accepted :
*** 76 for 1.2 (total 107)
*** test case exists 13 for 1.2
* Testing
** Testing done last week for [[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110329.5/images/meego-core-armv7l-madde-sysroot/ meego-core-armv7l-madde-sysroot-1.1.99.0.20110329.5]] on Ubuntu 10.10 32bit and Fedora13 32bit.
*** Results updated to http://qa-reports.meego.com/1.2/Sdk/Basic%20Feature%20Testing/N900 .
*** Valid bugs on both distros : #12335 MTF app build, #13831 MTF app widgets, #14910 app launch on device, #14914 qemu launch
*** Valid bugs on Ubuntu : #12853 libattica, #13171 OBS plugin, #14912 wlan debug
*** Valid bugs on Fedora : #12561 uninstallation, #12820 install libattica, #12821 plugin errors on qtcreator start
** Testing not started for http://repo.meego.com/MeeGo/builds/trunk/1.1.99.1.20110405.3/ because no tar of sysroot available.
** Testlink (tl.meego.com) is not available, but it's been informed to Intel.

* Basic Feature Testing(build 1.1.90.8.20110322.2)
** Ubuntu 10.10
*** Netbook qemu -11p/0f
*** Netbook sysroot -25p/0f
** Fedora 13
*** Netbook qemu -11p/0f
*** Netbook sysroot -25p/0f
*** Netbook image -11p/0f
*** Handset qemu -13p/2f(failed on [https://bugs.meego.com/show_bug.cgi?id=14874 #14874])
*** Handset Sysroot -27p/0f
**Critical bugs pending: [[https://bugs.meego.com/show_bug.cgi?id=12865 #12865], [https://bugs.meego.com/show_bug.cgi?id=14529 #14529], [https://bugs.meego.com/show_bug.cgi?id=14897 #14897], [https://bugs.meego.com/show_bug.cgi?id=14893 #14893], [https://bugs.meego.com/show_bug.cgi?id=13007 #13007], [https://bugs.meego.com/show_bug.cgi?id=13832 #13832], [https://bugs.meego.com/show_bug.cgi?id=11607 #11607], [https://bugs.meego.com/show_bug.cgi?id=12073 #12073], [https://bugs.meego.com/show_bug.cgi?id=12085 #12085], [https://bugs.meego.com/show_bug.cgi?id=13943 #13943], [https://bugs.meego.com/show_bug.cgi?id=9790 #9790]]

* Total Bug Count(368)
** Critical - New:5 ,NeedInfo:1 ,Assigned:4 ,Waiting for upstream:0 ,Reopened:1 , Resolved:11 ,Released:0 ,Verified:19 ,Closed:0
** Major - New:10 ,NeedInfo:1 ,Assigned:3 ,Waiting for upstream:0 ,Reopened:1 , Resolved:11 ,Released:0 ,Verified:30 ,Closed:1
** Normal - New:101 ,NeedInfo:3 ,Assigned:29 ,Waiting for upstream:1 ,Reopened:6 , Resolved:49 ,Released:16 ,Verified:44 ,Closed:4
** Trivial - New:3 ,NeedInfo:0 ,Assigned:0 ,Waiting for upstream:0 ,Reopened:0 , Resolved:1 ,Released:1 ,Verified:3 ,Closed:0
** Enhancement - New:5 ,NeedInfo:0 ,Assigned:0 ,Waiting for upstream:0 ,Reopened:0 , Resolved:1 ,Released:1 ,Verified:3 ,Closed:0

* Test transition is still in progress.
* Review test cases on tl (BMC#12536)
* Formalize bug handling workflow

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-03-16T03:03:30Z

Maxayu: /* Notes and caveats */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2-4.7.1
*** meego-netbook-ia32-1.1.2-4.7.1
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.2</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>
* '''Note: If the image of an earlier version prior to 1.2 is used, the mad-developer should be installed on device manually before the application is deployed. The following two approaches are alternative.'''
<ol>
<li> Download the repo file from http://download.meego.com/live/Trunk/standard/Trunk.repo to /etc/zypp/repos.d. Then install mad-developer</li>
sudo zypper ref
sudo zypper install utfs-client
sudo zypper install mad-developer
<li> Download the rpm package from http://download.meego.com/live/Trunk/standard/i586/mad-developer-2.0-2.1.i586.rpm (OR http://download.meego.com/live/Trunk/standard/armv7l/mad-developer-2.0-2.7.armv7l.rpm for arm.). Then install rpm package.</li>
rpm -i mad-developer-2.0-2.1.i586.rpm
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. To meet this requirement, you can install one of the following software:
** Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP).
** Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en). This is for Windows 7 only.
[[File:Untitled2.png|600px]]

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browse and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* In "Toolchain:", browse and select "Microsoft Visual C++ Compilers 9.0 (x86)" if you installed "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1", or select "Microsoft Visual C++ Compilers 8.0 (x86)" if you installed "Microsoft Visio C++ 2008 Express Edition".
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information. If the simulator cannot be load automatically from Qt Creator, you can launch it once manually by double clicking the icon of "<MEEGO_SDK>\Simulator\Application\simulator.exe" in Explorer.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Build MeeGo SDK for Windows

2011-03-11T07:31:32Z

Maxayu: /* IFW */

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1 rc1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''- Prerequisite'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Installation</th><th>Linking</th></tr>
<tr><td>Windows OS (XP/Vista/7)</td><td>http://www.microsoft.com</td>
<tr><td>MeeGo SDK for Windows</td><td>http://wiki.meego.com/SDK/MeeGo_SDK_for_Windows</td></tr>
<tr><td>Visual Studio 2008</td><td>http://www.microsoft.com/express/Downloads/#2008-All</td></tr>
<tr><td>Qt for Open Source on Windows (VS2008)</td><td>http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe</td></tr>
</table>

Note: In case of build failure, please make sure webkit is mentioned inside $QTDIR/mkspecs/qconfig.pri file in the QT_CONFIG list, if it is not there, add it at the end of QT_CONFIG list, e.g.: QT_CONFIG += webkit

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in.

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin.

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin.

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

I used this script http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh to build toolchain for IA, which is based on toolchain-w32.sh (for ARM).

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==
Source code of IFW can be downloaded from: http://qt.gitorious.org/qt-labs/installer-framework

Check the document in the source tree on how to build it.

You'd better build a static IFW, and you'll need to build static Qt for it.

===Build static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

SDK/Windows

2011-03-11T07:28:41Z

Maxayu: /* BKMs on building the SDK for Windows */

SDK/Windows

2011-03-11T07:28:24Z

Maxayu: /* Download and use the SDK for Windows */

== Download and use the MeeGo SDK for Windows==
* Latest [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK for Windows==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Windows

2011-03-11T07:27:55Z

Maxayu: /* Getting started with the SDK for Windows */

== Download and use the SDK for Windows==
* Latest [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK for Windows==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Build MeeGo SDK for Windows

2011-03-08T02:40:44Z

Maxayu: /* Qt Creator 2.1 rc1 */

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1 rc1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''- Prerequisite'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Installation</th><th>Linking</th></tr>
<tr><td>Windows OS (XP/Vista/7)</td><td>http://www.microsoft.com</td>
<tr><td>MeeGo SDK for Windows</td><td>http://wiki.meego.com/SDK/MeeGo_SDK_for_Windows</td></tr>
<tr><td>Visual Studio 2008</td><td>http://www.microsoft.com/express/Downloads/#2008-All</td></tr>
<tr><td>Qt for Open Source on Windows (VS2008)</td><td>http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe</td></tr>
</table>

Note: In case of build failure, please make sure webkit is mentioned inside $QTDIR/mkspecs/qconfig.pri file in the QT_CONFIG list, if it is not there, add it at the end of QT_CONFIG list, e.g.: QT_CONFIG += webkit

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in.

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin.

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin.

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

I used this script http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh to build toolchain for IA, which is based on toolchain-w32.sh (for ARM).

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==

===Build static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

SDK/Build MeeGo SDK for Windows

2011-03-08T02:19:10Z

Maxayu:

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1 rc1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''- Prerequisite'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Installation</th><th>Linking</th></tr>
<tr><td>Windows OS (XP/Vista/7)</td><td>http://www.microsoft.com</td>
<tr><td>MeeGo SDK for Windows</td><td>http://wiki.meego.com/SDK/MeeGo_SDK_for_Windows</td></tr>
<tr><td>Visual Studio 2008</td><td>http://www.microsoft.com/express/Downloads/#2008-All</td></tr>
<tr><td>Qt for Open Source on Windows (VS2008)</td><td>http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe</td></tr>
</table>

Note: After Qt for Open Source on Windows has been installed, the [[Media:qt_webkit_version.pri]] file is required to copy to $QTDIR/mkspecs/modules to link Qt WebKit library.

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in.

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin.

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin.

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

I used this script http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh to build toolchain for IA, which is based on toolchain-w32.sh (for ARM).

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==

===Build static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

SDK/QA

2011-03-04T06:39:18Z

Maxayu: Undo revision 32426 by Maxayu (Talk)

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to [[Quality/Bugtriage]]. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Veli Kaksonen (Nokia), Bob Spencer(Intel), Kerry Jiang (Intel), Arcadie Prepelita(Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in '''1 business day''' and decide if accept these new bugs. Bug owners should accept the bugs for her/him in '''1 business day'''. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [http://wiki.meego.com/SDKTestPlan SDK Test Plan]

== Test Report ==
*[http://wiki.meego.com/Quality/SDKTestReports MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20110301 20110301 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101109 20101109 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101102 20101102 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101026 20101026 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101019 20101019 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101012 20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100928 20100928 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100921 20100921 Meeting Minutes]]

SDK/QA

2011-03-04T06:28:02Z

Maxayu: /* Bug Triage */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [http://wiki.meego.com/SDKTestPlan SDK Test Plan]

== Test Report ==
*[http://wiki.meego.com/Quality/SDKTestReports MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20110301 20110301 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101109 20101109 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101102 20101102 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101026 20101026 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101019 20101019 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101012 20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100928 20100928 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100921 20100921 Meeting Minutes]]

SDK/QA

2011-03-04T06:14:30Z

Maxayu: /* Bug Triage */

SDK/QA

2011-03-04T06:12:45Z

Maxayu: /* Bug Triage */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to [[Quality/Bugtriage]]. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Bob Spencer(Intel), Arcadie Prepelita(Intel), Veli Kaksonen (Nokia), Kerry Jiang (Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in '''1 business day''' and decide if accept these new bugs. Bug owners should accept the bugs for her/him in '''1 business day'''. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [http://wiki.meego.com/SDKTestPlan SDK Test Plan]

== Test Report ==
*[http://wiki.meego.com/Quality/SDKTestReports MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20110301 20110301 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101109 20101109 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101102 20101102 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101026 20101026 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101019 20101019 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101012 20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100928 20100928 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100921 20100921 Meeting Minutes]]

Quality/Bugtriage

2011-03-04T06:08:23Z

Maxayu:

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:
[[File:bug_triage_process.jpg]]

== MeeGo Bug Triage Guide ==
Check the [http://wiki.meego.com/Quality/Bugtriage_Guide Triage Guide] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || Juha Peisanen, Daniel Mihai, Fathi Boudra, Jackie Wu, Max Yu
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** Time: Every Thursday at 12:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: TBD
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

SDK/QA

2011-03-04T03:20:11Z

Maxayu: /* Bug Triage */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to http://moblin.intel.com/wiki/MeeGo_Bugzilla_and_Bug_Triage. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Bob Spencer(Intel), Arcadie Prepelita(Intel), Veli Kaksonen (Nokia), Kerry Jiang (Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in '''1 business day''' and decide if accept these new bugs. Bug owners should accept the bugs for her/him in '''1 business day'''. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [http://wiki.meego.com/SDKTestPlan SDK Test Plan]

== Test Report ==
*[http://wiki.meego.com/Quality/SDKTestReports MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20110301 20110301 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101109 20101109 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101102 20101102 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101026 20101026 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101019 20101019 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101012 20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100928 20100928 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100921 20100921 Meeting Minutes]]

SDK/QA

2011-03-04T03:18:39Z

Maxayu: /* Process */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to http://moblin.intel.com/wiki/MeeGo_Bugzilla_and_Bug_Triage. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Bob Spencer(Intel), Arcadie Prepelita(Intel), Veli Kaksonen (Nokia), Kerry Jiang (Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in 1 business day and decide if accept these new bugs. Bug owners should accept the bugs for her/him in 1 business day. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [http://wiki.meego.com/SDKTestPlan SDK Test Plan]

== Test Report ==
*[http://wiki.meego.com/Quality/SDKTestReports MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20110301 20110301 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101109 20101109 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101102 20101102 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101026 20101026 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101019 20101019 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20101012 20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100928 20100928 Meeting Minutes]]
*[[http://wiki.meego.com/SDK/QA/MeetingMinutes/20100921 20100921 Meeting Minutes]]

SDK/QA

2011-03-04T03:15:43Z

Maxayu: /* Process */

SDK/QA

2011-03-04T03:13:55Z

Maxayu: /* Bug Triage */

SDK/QA

2011-03-04T03:12:51Z

Maxayu: /* Process */

SDK/QA

2011-03-04T03:09:59Z

Maxayu: /* Team */

SDK/Build MeeGo SDK for Windows

2011-03-02T02:02:45Z

Maxayu: /* Built static Qt for IFW */

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1 rc1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''- Prerequisite'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Installation</th><th>Linking</th></tr>
<tr><td>Windows OS (XP/Vista/7)</td><td>http://www.microsoft.com</td>
<tr><td>MeeGo SDK for Windows</td><td>http://wiki.meego.com/SDK/MeeGo_SDK_for_Windows</td></tr>
<tr><td>Visual Studio 2008</td><td>http://www.microsoft.com/express/Downloads/#2008-All</td></tr>
<tr><td>Qt for Open Source on Windows (VS2008)</td><td>http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe</td></tr>
</table>

Note: After Qt for Open Source on Windows has been installed, the [[Media:qt_webkit_version.pri]] file is required to copy to $QTDIR/mkspecs/modules to link Qt WebKit library.

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in.

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin.

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin.

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

I used this script http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh to build toolchain for IA, which is based on toolchain-w32.sh (for ARM).

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==

===Build static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

SDK/Windows

2011-03-02T01:55:19Z

Maxayu: /* BKMs on building the SDK */

== Getting started with the SDK for Windows==
* Latest [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK for Windows==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Windows

2011-03-02T01:55:00Z

Maxayu: /* Getting started with the SDK */

SDK/Windows

2011-03-02T01:53:38Z

Maxayu: /* Getting started with the SDK */

== Getting started with the SDK ==
* Latest [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Windows

2011-03-02T01:52:32Z

Maxayu: /* Getting started with the SDK */

== Getting started with the SDK ==
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview for Windows]]
* MeeGo 1.2 SDK Preview 3 for Windows with a snapshot of the tablet target - http://appdeveloper.intel.com/en-us/article/installing-meego-sdk-windows
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Build MeeGo SDK for Windows

2011-03-01T07:15:37Z

Maxayu: /* Qt Simulator */

These are the BKMs to build MeeGo SDK for Windows. This implemented a part of [http://bugs.meego.com/show_bug.cgi?id=10971 Feature 10971 - Build MeeGo SDK for Windows in a public server]. For more information about MeeGo SDK for Windows, please check [[SDK/MeeGo SDK for Windows]].

[[User:Maxayu|Maxayu]] 09:17, 22 December 2010 (UTC)

==Qt Creator 2.1 rc1==

To build Qt Creator, you need to build on Windows OS and the below steps are following the spec file of the rpm package (http://build.meego.com/package/show?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost).

'''- Prerequisite'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Installation</th><th>Linking</th></tr>
<tr><td>Windows OS (XP/Vista/7)</td><td>http://www.microsoft.com</td>
<tr><td>MeeGo SDK for Windows</td><td>http://wiki.meego.com/SDK/MeeGo_SDK_for_Windows</td></tr>
<tr><td>Visual Studio 2008</td><td>http://www.microsoft.com/express/Downloads/#2008-All</td></tr>
<tr><td>Qt for Open Source on Windows (VS2008)</td><td>http://get.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-vs2008.exe</td></tr>
</table>

Note: After Qt for Open Source on Windows has been installed, the [[Media:qt_webkit_version.pri]] file is required to copy to $QTDIR/mkspecs/modules to link Qt WebKit library.

In the spec file, the following tasks are performed.

'''- Pre-Build'''

* Access http://build.meego.com/package/files?package=meego-sdk-qt-creator&project=devel%3Atools%3Asdk%3Ahost
** Download tar ball qt-creator-*-src.tar.gz
** Download all patches file
** Download mtf.png image file
* Extract all compressed files
* Apply all patches
* Copy images to corresponding paths

Launch ''MADDE Terminal'' (Start -> All Programs -> MeeGo SDK -> MADDE Terminal), and run below commands in the extracted directory of Qt Creator source code. For instance,

$patch -p1 -i ../meego-2.1_20110130.patch
$patch -p1 -i ../ftbfs_missing_webkit.patch
$patch -p1 -i ../ftbfs_allow-shlib-undefined_no-undefined.patch
$patch -p1 -i ../buildservice_plugin_20110104.patch
$patch -p1 -i ../install_qtquickplugin.patch
$cp -rf src/plugins/qt4projectmanager/qt-maemo/images src/plugins/qt4projectmanager/qt-meego/
$install -D -p -m 0644 ../mtf.png src/plugins/qt4projectmanager/wizards/images/mtf.png

Edit src/plugins/plugins.pro and comment the below line to disable the BuildService plug-in.

# plugin_buildservice \

'''- Build'''

Launch ''Qt Command Prompt'' (Start -> All Programs -> Qt by Nokia (VS2008 OpenSource) -> Qt Command Prompt). Run the below commands in an independent build directory, which can be created in parallel with the source directory and named 'qt-creator-*-rc1-build'.

>qmake -r DEFINES+=QTCREATOR_WITH_QML CONFIG-=console -config release ..\qt-creator-2.1.0-rc1-src\qtcreator.pro
>nmake

'''- Post Build'''

After building successfully, we manually copy everything via

1. xcopy /Y /R /E /EXCLUDE:%SCRIPT_DIRECTORY%\install_creator_step_excludes.txt %REPOSITORY_DIRECTORY%\creator %TARGET_LOCATION%\

* %SCRIPT_DIRECTORY%: The path of the script file install_creator_step_excludes.txt. It can be downloaded from here [[Media:install_creator_step_excludes.txt]].

* %REPOSITORY_DIRECTORY%: The build directory of Qt Creator, which should already contain \bin, \lib, \share and \src.

* %TARGET_LOCATION%: Create an independent folder manually to store the target files, which named 'QtCreator'.

For instance,

>xcopy /Y /R /E /EXCLUDE:C:\bin_win\install_creator_step_excludes.txt C:\build\qt-creator\qt-creator-2.1.0-rc1-build C:\build\data\qtcreator

2. xcopy /y %REPOSITORY_DIRECTORY%\creator\lib\qtcreator\plugins\Nokia\Find.dll %TARGET_LOCATION%\lib\qtcreator\plugins\Nokia\

There missed a file Find.dll unfortunately, which can be copied manually. For instance,

>xcopy /y C:\build\qt-creator\qt-creator-2.1.0-rc1-build\lib\qtcreator\plugins\Nokia\Find.dll C:\build\data\qtcreator\lib\qtcreator\plugins\Nokia\

3. Copy all the .dll and .exe files from C:\qt\4.7.1\bin to %TARGET_LOCATION%\bin.

4. Copy the following plugins to the corresponding subdirectories of %TARGET_LOCATION%\bin.

imageformats
imageformats/qgif4.dll
imageformats/qico4.dll
imageformats/qjpeg4.dll
imageformats/qmng4.dll
imageformats/qsvg4.dll
imageformats/qtiff4.dll
iconengines
iconengines/qsvgicon4.dll
sqldrivers
sqldrivers/qsqlite4.dll
codecs
codecs/qcncodecs4.dll
codecs/qjpcodecs4.dll
codecs/qkrcodecs4.dll
codecs/qtwcodecs4.dll
accessible
accessible/qtaccessiblewidgets4.dll

Compress the directory QtCreator into qtcreator.7z package.

==MADDE==

You need to build it on Linux OS.

''' - Pre-Build'''
* Access http://build.meego.com/package/files?package=madde&project=devel%3Atools%3Asdk%3Ahost to download madde-*.tar.gz
* MADDE builds if you have all required distfiles in place
* Additionally this requires that required packages are installed on build system (wine & mingw cross-compiler among other things)
* Download the script file file [[Media:Berlin-gatherer.sh‎]]
* Please change the following line in /usr/i586-mingw32msvc/include/stdint.h from:
typedef signed char int8_t;
To:
//typedef signed char int8_t; !!!! XXX XXXX The change in the next line is a tmp edit for building MADDE only. Please change it back to this line ASAP.
typedef char int8_t;

''' -Build'''
$cd /path/to/madde
$make w32 SUMO=meego
$../berlin_gatherer.sh -e _build

==qt-tools 4.7.1==

Follow instructions on http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/docs/QtToolsForMadde.rst . Which contains my modifications.

The patch mentioned in the above link can be downloaded from here: [[Media:Qt qtmake option.cpp.patch]].

mgen and mmoc from libmeegotouch need to be added. Source code of libmeegotouch can be downloaded from http://build.meego.com/package/show?package=libmeegotouch&project=Trunk.

===mgen===

To build mgen, create a file "make.bat" by copy the following lines:

set MYQTDIR=C:\Qt\4.7.1
set CL=/I%MYQTDIR%\include\QtGui /I%MYQTDIR%\include\QtCore /I%MYQTDIR%\include
set LIBRARY_PATH=%MYQTDIR%\lib
cl mgen.cpp mgen_processor.cpp %LIBRARY_PATH%\QtGui4.lib %LIBRARY_PATH%\QtCore4.lib %LIBRARY_PATH%\QtCore4.lib

Put the file "make.bat" into "mgen" sub-directory of libmeegotouch, and invoke it to build mgen.

==Toolchain==

I used this script http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/i386-toolchain-w32-meego.sh to build toolchain for IA, which is based on toolchain-w32.sh (for ARM).

==Qt Simulator==

Refer to: http://developer.qt.nokia.com/wiki/Qt_Simulator and http://build.meego.com/package/view_file?file=qt-simulator.spec&package=qt-simulator&project=devel%3Atools%3Asdk%3Ahost&srcmd5=e45d364bbac25fb09e70f49e9650177c (require login. Download source code from here.)

Source code of simulator need to be patched by [[Media:Simulator.patch]].

Create a directory "simulator-depends".

Use the bat file [[Media:Make_bat.txt]] to build it. While you need to apply the following work around after building simulator-mobility and before building simulator.
cd simulator-mobility-1.1.0~git1/plugins/sensors/simulator/
mv main.cpp main.cpp.sav

==IFW==

===Built static Qt for IFW===
configure -static -no-webkit -no-qt3support -no-dbus -no-multimedia -no-phonon -fast -no-opengl -exceptions -nomake demos -nomake examples -nokia-developer -qt-sql-sqlite -plugin-sql-sqlite

"-qt-sql-sqlite -plugin-sql-sqlite" are work around for buiding IFW.

File:Install creator step excludes.txt

2011-02-25T09:29:20Z

Maxayu: uploaded a new version of "File:Install creator step excludes.txt"

File:Install creator step excludes.txt

2011-02-25T09:28:58Z

Maxayu: uploaded a new version of "File:Install creator step excludes.txt"

SDK/MeeGo SDK for Windows

2011-02-15T08:24:26Z

Maxayu: moved SDK/MeeGo SDK for Windows to SDK/Windows

#REDIRECT [[SDK/Windows]]

SDK/Windows

2011-02-15T08:24:26Z

Maxayu: moved SDK/MeeGo SDK for Windows to SDK/Windows

== Getting started with the SDK ==
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview Version for Windows]]

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== BKMs on building the SDK==
* [[SDK/Build MeeGo SDK for Windows]]

SDK

2011-02-15T08:22:21Z

Maxayu: /* Using the SDK */

= MeeGo SDK =

This is the entry page of MeeGo SDK. From here you can find info about using MeeGo SDK and about SDK development.

== Using the SDK ==

* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux]] - Main page pointed from http://meego.com/developers
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows]]
* [[SDK/Docs/1.1]] - For more information about MeeGo SDK 1.1 (beta)
* [[SDK/Testing]] - Instruction on how to install and test the weekly release. NOTE: weekly releases can be totally broken. Use stable unless you know what you are doing.

== Contact ==

MeeGo SDK team can be found here:
* '''IRC''': #meego-sdk on Freenode. [http://trac.tspre.org/merbot/freenode/%23meego-sdk/ Logs.]
* '''Mailing list''': [http://lists.meego.com/listinfo/meego-sdk MeeGo-SDK].

Visit the [http://wiki.meego.com/Mailing_list_guidelines mailing guidelines page] for more details about participating on MeeGo mailing lists and IRC channels.

== SDK Development ==

SDK development is done by the MeeGo.com SDK Program under MeeGo Program Office. MeeGo SDK team consists of team members from various companies involved in MeeGo. The goal is to create one SDK suitable for all the official MeeGo verticals. SDK also needs to be extend-able with plugins for more specific needs.

* [[SDK/Road_to_1.1]]
* [[SDK/Road_to_1.2]]

=== SDK Program Organization ===

==== Management ====

* [http://meego.com/users/veli Veli Kaksonen] - Program Manager
* Ville Lavonius - Product Manager
* [http://meego.com/users/bspencer Bob Spencer] - Architect
* Kerry Jiang - Engineering Manager / China

==== Domains ====

* [[SDK/Architecture]] - [http://meego.com/users/bspencer Bob Spencer] - Architecture Team Lead
** [http://meego.com/users/fabo Fathi Boudra]
** [http://meego.com/users/wwhbuaa Jackie Wu]
** [http://meego.com/users/mauricek Maurice Kalinowski]

* [[SDK/API]] - N/A - API Team Lead

* [[SDK/Release]] - [http://meego.com/users/fabo Fathi Boudra] - Release Team Lead
** [http://meego.com/users/wwhbuaa Jackie Wu]

* [[SDK/Windows]] - [http://wiki.meego.com/User:Maxayu Max A Yu] - Windows Port Lead

* [[SDK/MacOSX]] - N/A - Mac OS X Port Lead

* [[SDK/QA]] - Jaya Uppalapati - QA Team Lead
** Juha Peisanen
** Arcadie Perpelita
** Daniel Mihai
** Laura Piekkola

* [[SDK/Documentation]] - Taru Laine - Documentation Team Lead
** Elliot Smith
** Ronan MacLaverty
** Murali Punaganti
** Bob Spencer

==== Subsystems ====

* [[SDK/Installer]] - N/A - Installer Team Lead
** N/A

* [[SDK/QtCreator]] - [http://meego.com/users/mauricek Maurice Kalinowski] - Qt SDK responsible
** [http://meego.com/users/johnchen Zhang Chen]

* [[SDK/Toolchains]] - [http://meego.com/users/kant Jarmo Kant] - Toolchains Subsystem Maintainer / Team Lead
** Al Nikolov - ARM
** Xu U Zhang - Intel

* [[SDK/MADDE]] - Jari Ihatsu - MADDE Subsystem Maintainer / Team Lead
** [http://meego.com/users/too Tomi Ollila]
** Wang Wenchao

* [[SDK/Qemu]] - [http://meego.com/users/suihkulokki Riku Voipio] - Qemu Subsystem Maintainer / Team Lead
** [http://meego.com/users/zhiyuan Zhiyuan Lv]
** Juha Riihimäki
** [http://meego.com/users/haitao Haitao Feng]
** [http://meego.com/users/juntian Jun Tian]

=== Meetings ===

* [[SDK/Meetings]] - Meetings - agenda, minutes

=== Proposals & Studies ===

Proposals & Studies about MeeGo SDK. Feel free to write one.. :)

==== Active ====

* [[SDK/Bugzilla_Components]] - List of products and components in Bugzilla
* [[SDK/Two_weeks_delay_proposal]] - Proposal about two weeks delay in releasing SDK after MeeGo release
* [[SDK/Installers_study]] - Pros and cons about different installing possibilities
* [[SDK/Installation_Proposal]] -- Proposal for discussion on MeeGo SDK installation (Bob)
* [[SDK/Team_Proposal]] - SDK team, members, roles, responsibilities
* [[SDK/Managing_MADDE_Components_proposal]] - Proposal on how to add/remove/update madde components.
* [[SDK/Packaging_proposal]] - Proposal on how to package MeeGo application for deployment and uploading to App stores.
* [[SDK/Packages_group]] - Proposal for packages group
* [[SDK/Sysroot_extension]] - Proposal on how to extend sysroot by adding additional libraries

==== Closed ====

* lorem ipsum

== Misc material not yet in right place ==

Let's gather here links to all the documents we have. Then later we can review those and move those under /SDK/.

* [[SDK/MeeGo_1.1_Application_SDK_Project_Plan]] - (work in progress)
* [[SDK/Release_Tasks]]
* [[SDK/MADDE_distfiles]]
* [[SDK/Comparison]]
* [[SDK/Road_to_1.1.2]]
* [[SDK/Tutorials]]
* link1
* link2

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-12T04:26:58Z

Maxayu: /* Add Qt Simulator target */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.2</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. To meet this requirement, you can install one of the following software:
** Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP).
** Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en). This is for Windows 7 only.
[[File:Untitled2.png|600px]]

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browse and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* In "Toolchain:", browse and select "Microsoft Visual C++ Compilers 9.0 (x86)" if you installed "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1", or select "Microsoft Visual C++ Compilers 8.0 (x86)" if you installed "Microsoft Visio C++ 2008 Express Edition".
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information. If the simulator cannot be load automatically from Qt Creator, you can launch it once manually by double clicking the icon of "<MEEGO_SDK>\Simulator\Application\simulator.exe" in Explorer.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-12T04:22:45Z

Maxayu: /* Build an app for Qt Simulator, and run it with Qt Simulator */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.2</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. To meet this requirement, you can install one of the following software:
** Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP).
** Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en). This is for Windows 7 only.
[[File:Untitled2.png|600px]]

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browse and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* In "Toolchain:", browse and select "Microsoft Visual C++ Compilers 9.0 (x86)" if you installed "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1", or select "Microsoft Visual C++ Compilers 8.0 (x86)" if you installed "Microsoft Visio C++ 2008 Express Edition".
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

File:Untitled2.png

2011-02-12T04:20:06Z

Maxayu:

File:Untitled.png

2011-02-12T04:19:45Z

Maxayu: uploaded a new version of "File:Untitled.png": Reverted to version as of 10:29, 8 November 2010

File:Untitled.png

2011-02-12T04:19:07Z

Maxayu: uploaded a new version of "File:Untitled.png"

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-12T04:16:39Z

Maxayu: /* Build an app for Qt Simulator, and run it with Qt Simulator */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.2</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. To meet this requirement, you can install one of the following software:
** Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP).
** Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en). This is for Windows 7 only.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browse and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* In "Toolchain:", browse and select "Microsoft Visual C++ Compilers 9.0 (x86)" if you installed "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1", or select "Microsoft Visual C++ Compilers 8.0 (x86)" if you installed "Microsoft Visio C++ 2008 Express Edition".
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Windows

2011-02-01T07:53:12Z

Maxayu:

SDK/Windows

2011-02-01T07:52:02Z

Maxayu:

==Get support==
* MeeGo Bugzilla
** URL: http://bugs.meego.com
** Product name: MeeGo SDK
** Bug summary: Please have "[Windows]" in the begining of your bug summary.
* MeeGo SDK mailing list
**http://lists.meego.com/listinfo/meego-sdk

== Getting started with the SDK ==

* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.1 SDK for Windows]]
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|MeeGo 1.2 SDK Preview Version for Windows]]

== BKMs on building the SDK==
* [[SDK/Build MeeGo SDK for Windows]]

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T07:51:11Z

Maxayu: /* Download and setup the MeeGo SDK */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.2</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browser and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T07:48:55Z

Maxayu: /* Add Qt Simulator target */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browser and select qmake location: ''<MEEGO_SDK>\Simulator\Qt\bin\qmake.exe''. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T07:48:32Z

Maxayu: /* Add Qt Simulator target */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browser and select qmake location: <MEEGO_SDK>\Simulator\Qt\bin\qmake.exe. Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T07:47:27Z

Maxayu: /* Add Qt Simulator target */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browser and select qmake location: <MEEGO_SDK>\Simulator\Qt\bin\qmake.exe
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is C:\MeeGoSDK_1.2.
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T07:44:45Z

Maxayu: /* Build an app for Qt Simulator, and run it with Qt Simulator */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.

==== Add Qt Simulator target ====
* Launch Qt Creator
* Go to Tools->Options->Qt4->Qt Versions
* Click the "+" to add a new "Qt Version"
* In "Version name", provide a name.
* In "qmake locations:", browser and select C:\MeeGoSDK_1.2\Simulator\Qt\bin\qmake
* Build
* To use the simulator, please refer to http://doc.qt.nokia.com/qtsimulator-1.1/simulator-starting.html for more information.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].

SDK/Docs/1.2/Getting started with the MeeGo SDK for Windows

2011-02-01T06:12:30Z

Maxayu: /* Develop MeeGo Applications */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:windows]]

'''Note: MeeGo 1.2 SDK has not been released yet. This page contains instructions for downloading and installing the preview version. '''

This page describes how to install and configure the MeeGo 1.2 SDK on your Windows development system. For more information about MeeGo SDK for Windows, check [[SDK/MeeGo_SDK_for_Windows]].

== Prerequisites ==

* '''Hardware:''' Any reasonably modern IA hardware, such as 32-bit Intel Atom or Intel Core 2 CPU.
** The SDK version of QEMU relies on kqemu to provide CPU virtualization support, but on some machines with this support, images will still not run. This is believed to be related to certain types of CPU. Below are some details of tested hardware:
*:* Known to work: Intel(R) Core(TM) 2 Quad CPU, Q8200; Intel(R) i5 and i7
*:* Known not to work: Intel(R) Core(TM) 2 Duo P9400 in Thinkpad T400; Intel(R) Core(TM)2 Q9400 in HP7900 Ultra-slim
* '''Software:''' Only Windows XP 32-bit and Windows 7 32-bit are officially supported.
*: Currently the QEMU emulator only works for IA targets on 32-bit Windows. If you are using 64-bit Windows, QEMU is not available.
*: For support status and issues using other host operating systems, see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Filesystem:''' MeeGo SDK should be installed on a hardlink-capable filesystem such as NTFS. FAT* filesystems are not hardlink-capable and not supported.

=== Notes and caveats ===

* '''QEMU runtimes and targets''': The following pre-defined targets and runtimes are the only ones which have been verified on Windows:
** Targets:
*** meego-handset-ia32-1.1.2
*** meego-netbook-ia32-1.1.2
*** meego-core-armv7l-1.1.2
** Runtimes:
*** meego-handset-ia32-qemu-1.1.20110110.1026-runtime
*** meego-netbook-ia32-qemu-1.1.20110110.1049-runtime
*: '''Others may be listed by MADDE, but are not guaranteed to work.'''
* '''Uninstalling:''' Everything you've installed as part of the SDK, ''including MADDE targets and runtimes'', will be removed if you run the MeeGo SDK uninstaller.
* '''Commands:''' Terminal commands in the instructions below are prefaced with "$". Do not include $ when entering the commands in your terminal.

== Download and setup the MeeGo SDK ==

<ol>
<li>Download the MeeGo SDK installer:</li>
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>Description</th><th>Size</th></tr>
<tr><td>http://download3.meego.com/MeeGoSDK/1.2/meego-1.2-sdk-offline-installer-0127.exe</td>
<td>MeeGo SDK Windows installer</td>
<td>~400MB</td>
</tr>
</table>
<li>Double-click on the downloaded <code>.exe</code> file and follow the prompts to install the SDK.</li>
<li>'''If you are using Windows XP, please download a small file vcredist_x86.exe (Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)) from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2 and install it to your system.''' This is not needed for Windows 7.
<li>Launch MADDE Terminal with ''Start > All Programs > MeeGo SDK > MADDE Terminal''.</li>
<ol>
<li> Run something like "export http_proxy=XXX" if you are in an intranet.</li>
<li> Run "mad-admin create -f meego-handset-ia32-w32-1.1" to create target "meego-handset-ia32-w32-1.1". Some huge files will be downloaded automatically.</li>
<li> Run "mad-admin create -e -f meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime" to create a runtime "meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime". Some huge files will be downloaded automatically.</li>
<ul>
<li><b>Known issue:</b>If there is error like "/bin/mad-admin: line 25: __ml_path__/madlib/madlib.sh:" No such file or directory.". Run the /postinstall/postinstall.sh to fix paths and try again.(see bug report http://bugs.meego.com/show_bug.cgi?id=11605)</li>
</ul>
</ol>
<li>Launch Qt Creator with ''Start > All Programs > MeeGo SDK > QtCreator''.</li>
<li> Configure Qt Creator to support MeeGo sysroot. Inside Qt Creator, follow these steps:
<ol>
<li>From the ''Tools'' menu, choose ''Options''.</li>
<li>Click into the ''Qt4'' section, and make sure the ''Qt Versions'' tab is open.</li>
<li>Click the ''+'' button, and then fill the ''Version name'' and the ''qmake location'' of the MeeGo target:
<ul>
<li>''Version name:'' '''meego-handset'''</li>
<li>''qmake location:'' '''<MEEGO_SDK>\MADDE\targets\<target name>\bin\qmake.exe'''<br/>
Replace <MEEGO_SDK> with the directory where you installed MeeGo SDK; the default is <code>C:\MeeGoSDK_1.1</code>; replace <target_name> with the name of the target (for example, '''meego-handset-ia32-w32-1.1''').</li>
<li>Once added, select the new entry and click on the ''Rebuild'' button (bottom right) to build the debugging helper for this Qt version. This enables you to use debugging from Qt Creator.</li>
</ul>
The result should look like this:<br/>
[[File:Meego-sdk-qt4.png|800px]]
</li>
</ol>

</ol>

== Develop MeeGo Applications ==
<ol>

<li> '''Create a MeeGo touch project (for handset) or Qt Gui project (for netbook) ''' </li>
Go to the menu: File -> New File or Project -> Qt Application Project -> Meego Touch Framework Application. <br/>
[[File:Windows_sdk_2.png]]

In "Project setup" dialog, choose "meego-handset".

[[File:Meego-sdk-project-setup.png]]

<li> '''Disable shadow build'''</li>

'''"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”. '''
</ol>
===Run an app within the QEMU Emulator===
<ol>
<li> '''Set up emulator: Install kqemu accelerator for QEMU on 32-bit Windows system'''</li>
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.

<li> '''Configuration for a MeeGo Emulator device''' </li>

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".<br/>
[[File:Meego-sdk-emulator.png|800px]]

<li> '''Set Run Configuration''' </li>
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).<br>
[[File:Meego-sdk-run-settings.png|800px]]

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

<li> '''Build, run and deploy the application'''</li>
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.<br>
[[File:Qemu-handset.png|800px]]

<li> '''Debug the application'''</li>
You can also debug the application by clicking the "Debug" icon. Setting breakpoints and stepping are the same as local applications.<br>
[[File:Qemu-handset-debug.png|800px]]
</ol>

====More about QEMU Emulator====
===== 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.
<ol><li>Launch QEMU with MeeGo image </li>
<li>From a terminal on the host, connect to the running image</li>
$ ssh meego@127.0.0.1 -p 6666
</ol>
Two user accounts are available in the MeeGo images:<br>
User: meego Password: meego<br>
User: root      Password: meego<br>

===== Known issues about QEMU image and workarounds for them=====
*[http://bugs.meego.com/show_bug.cgi?id=10412 Bug #10412: mouse udev not ready before starting X server while running handset image on QEMU windows]
<ol>
<li>SSH into QEMU runtime as root user.</li>
<li>edit /usr/sbin/meego-dm to add "sleep 5" </li>
sleep 5 # new added line
shopt -s execfail
</ol>
*[http://bugs.meego.com/show_bug.cgi?id=9737 Bug #9737: Fail to run application in Qemu]
<ol>
<li> SSH into QEMU runtime as root user.</li>
<li> Invoke the following command:</li>
rm -rf /etc/ssh/*key*
</ol>

===== For advanced users only: 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:

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 [http://bugs.meego.com/show_bug.cgi?id=10412 bug #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 [http://bugs.meego.com/show_bug.cgi?id=10149 bug #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

=== Run an app within a real device ===
<ol>
<li> Go to Tools -> Options -> Projects -> MeeGo Device Configurations and click "Add" button. Select "Remote Device" for "Device type", input other information and give a name for this configuration</li>
[[File:Real-device.png|800px]]
<li> Open your project and in the "Projects" mode, click "Run" in the little MeeGo target window, and select the configuration you just created in "Device Configuration"</li>
[[File:Meego-sdk-run-settings-real-device.png|800px]]
<li> Launch terminal inside the device, and run command "xhost +" in it. </li>
<li> Click "Run" or "Debug" on the lower left corner of Qt Creator to run or debug your application on the configured Device.</li>
</ol>

=== Build an app for Qt Simulator, and run it with Qt Simulator===
* '''Note: MTF apps cannot be built with simulator currently, while Qt apps can be built.'''
* Microsoft C++ Compiler is required to build apps for Qt Simulator. You can install Microsoft Visio C++ 2008 Express Edition (http://www.microsoft.com/express/Downloads/#2008-Visual-CPP) to meet this requirement. It is free.
* Select qmake executable for Qt Simulator
** It should be "C:\MeeGoSDK_1.2\Simulator\Qt\bin\qmake" if you installed SDK to default install directory.

==== Install Debugging Tools for Windows====
You need to install Debugging Tools for Windows for debugging apps with simulator.

* Launch Qt Creator
* Select Tools->Option->Debugger->Cdb, check 'CDB'
*Click the hyperlink of "Debugging Tools for Windows"
[[File:Qt-creator-option-debugger-cdb.png|600px]]
*Download the previous versions of debugging tools for Windows (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi)
[[File:Web-page-download-debugging-tools.png|600px]]
* If the CDB path had not been configured preperly, click 'Auto Detect' button to set it manually.

==Known issues and workarounds==

Please refer to [[SDK/Docs/1.1/Troubleshooting]].