MeeGo wiki - User contributions [en]

OBS/Community OBS/Project Areas

2011-05-05T13:13:13Z

Fabo:

These are the current projects on the MeeGo Community OBS

== MeeGo DE ==
This is where the [[ARM/N900/DeveloperEdition|MeeGo 1.2 Developer Edition for N900]] is built.

Maintainers:
* Carsten Munk / Stskeeps
* Marko Saukko / Sage
* Fathi Boudra / fabo

== MINT ==
The MeeGo Integration Project is where the MeeGo [[Release Infrastructure]] systems such as BOSS are (will be) built.

Admins:
* lbt / David Greaves
* iamer / Islam Amer

== KDE ==
The MeeGo integration project for KDE Community. It's part of:
* KDE Mobile, aims at bringing the KDE Platform and the KDE Plasma Workspace onto mobile, netbook, in-vehicule and tablets type of devices.
* Plasma Active, aims at creating a cross-device user experience for emerging devices such as tablet computers, media centers, smartphones, and more.
* Kontact Touch, an email and groupware client for touch screen devices, like smartphones, netbooks or tablets.

Maintainers:
* Fathi Boudra / fabo

OBS/Community OBS/Project Areas

2011-05-05T08:40:40Z

Fabo:

MeeGo-Meeting IRC Schedule

2011-04-12T07:02:57Z

Fabo: /* Regular Meetings */

To avoid meeting conflicts in [http://meego.com/community/irc-channel #meego-meeting], please add your meeting here with date and UTC time until we have a more robust solution. You might also want to review our [[IRC guidelines]] for the MeeGo project.

== Regular Meetings ==

'''Monday'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|MeeGo Core Bug Triage Meetings]]: Every Monday at '''7:00 UTC'''

'''Tuesday'''
* [[Quality/Meetings| QA Meetings]]: Every Tuesday at '''07:00 UTC'''
* [[SDK/Meetings/Release| SDK Meeting (Release)]]: Every Tuesday at '''08:00 UTC'''
* [[ARM/N900/DeveloperEdition/Meetings| N900 Developer Edition Team Meetings]]: Every Tuesday at '''11:00 UTC''', 14:00 EEST
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Netbook Bug Triage Meetings]]: Every Tuesday at '''13:00 UTC'''
* [[Project/Dialer/Meetings| Dialer Project Meetings]]: Every Tuesday at '''15:00 UTC''', '''18:00 EEST''', '''08:00 PST'''
* [[Community_Office/Meetings| Community Office Meeting]]: The 1st and 3rd Tuesday, alternating between '''19:00 UTC and 14:00 UTC'''
* [[Events/Meetings|Events Meeting]]: Every other Tuesday at '''17:00 UTC'''

'''Wednesday'''
* [[SDK/Meetings| SDK Meeting]]: Every Wednesday at '''05:30 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Handset Bug Triage Meetings]]: Every Wednesday at '''7:00 UTC''' to '''8:00 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MCTS Bug Triage Meetings]]: Every Wednesday at '''8:00 UTC'''
* [[L10n_meeting_schedule| Localization / L10n Meetings]]: monthly at '''15:00 UTC'''

'''Thursday'''
* [[Technical_Steering_Group_meetings| Technical Steering Group Meeting]]: Every other Thursday at '''06:00 UTC''' (Wed. 11pm Pacific)
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo N900 1.2 Critical bug tracking]]: Every Thursday at '''7:00 UTC'''
* [[ARM/N900/Meetings| MeeGo N900 Hardware Adaptation Meetings]]: Every Thursday at '''8:00 UTC'''
* [[ARM/N900/VoiceSMS/Meetings| MeeGo N900 DE Voice/SMS team meeting]]: Every Thursday at '''11:00 UTC'''

'''Friday'''
* [[ARM/N900/Browser/Meetings | Meego N900 DE Browser & Wlan team meeting ]]: Every Friday at '''7:00 UTC'''

'''Sunday'''
* [[Local_MeeGo_Networks/MeeGo_Network_Finland#Online_Community_Meetings | MeeGo Network Finland Meetings]]: The 1st and 3rd Sunday at '''15:00 UTC'''

== Ad Hoc Meetings ==

Scheduling a one-time meeting? Add it to this section.

* [[Quality/QA-tools/Arch-Meetings| MeeGo QA Tools architecture meeting]]: Thursday, 10th of Feb 2011 at '''11:00 UTC'''

=== Guidelines ===

Please refer to the [[IRC guidelines]] for more details about how to run a MeeGo IRC meeting and using #meego-meeting.

You might also be interested in these [[IRC Presentation Tips]].

SDK/Tutorials/Image Creation

2011-04-06T08:15:26Z

Fabo: /* Create QEMU images (QEMU NAND and rootfs) */

== Overview ==

== Create sysroot image(s) ==

Create the sysroot image(s) using mic2 tool:
* download core-${arch}-madde-sysroot.ks files from http://meego.gitorious.org/meego-os-base/image-configurations/trees/master/core
* use the following command line

sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=fs --arch='''${arch}''' --config='''core-${arch}-madde-sysroot.ks''' --package=tar.bz2 --release

== Create QEMU images (QEMU NAND and rootfs) ==

Create the QEMU NAND image using qflasher tool:

* 3 components are needed: a kernel file, nolo-qemu package (provides xloader/secondary binaries) and qflasher package.
** the kernel file is available with the MeeGo images for QEMU (e.g. http://download.meego.com/trunk-daily/builds/1.1.80/trunk-daily-1.1.80.12.20101223.1/handset/images/meego-handset-armv7l-qemu/)
** nolo-qemu and qflasher packages are available from non-oss repository (e.g. http://repo.meego.com/MeeGo/builds/trunk/daily/non-oss/repos/ia32/packages/i586/)
* use the following command line to create the NAND image:
$ ./qflasher -m rx51 -x xloader-qemu.bin -s secondary-qemu.bin -k meego-handset-armv7l-qemu-daily-vmlinuz-2.6.35.3-10.3-n900 -o meego-handset-armv7l-qemu-daily-nand-n900.img -p k=3072

'''Note''': qflasher can be used on all supported Linux hosts. You can extract the rpm package using
$ rpm2cpio qflasher-21-1.1.i586.rpm | cpio -idmv

* use the following command line to run QEMU:
$ touch sd-empty
$ meego-sdk-qemu-system-arm -M n900 -mtdblock meego-handset-armv7l-qemu-daily-nand-n900.img -sd sd-empty -sd meego-handset-armv7l-qemu-daily-mmcblk0p.raw -serial stdio -clock unix -redir tcp:5555:10.0.2.15:22

Create the QEMU rootfs image using mic2 tool:
* download handset-${arch}-qemu.ks files from http://meego.gitorious.org/meego-os-base/image-configurations/trees/master/SDK
* use the following command line

sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=raw --arch=${arch} --save-kernel --config='''handset-${arch}-qemu.ks''' --package=tar.bz2 --release

ARM/N900/Install/Dual Boot

2011-03-23T10:42:48Z

Fabo: /* Dual booting Maemo 5 (Fremantle) PR1.3 and MeeGo 1.1 */

== Dual booting Maemo 5 (Fremantle) PR1.3 and MeeGo 1.1 ==

WARNING: This guide is experimental and everything you do with this guide is at your own responsibility and risk and will probably void your warranty

WARNING: DO NOT RELY ON WALL CHARGER, ONLY USB CHARGING FOR 1.1 IMAGES, see [http://bugs.meego.com/show_bug.cgi?id=2260 meego bug #2260]

WARNING: If you are unable to boot anything, do NOT let the device stay in u-boot. IMMEDIATELY reflash back to Maemo. Your battery may drain otherwise. You can solve a drain situation by reflashing back to Maemo using another, charged, battery. Or charge your battery in another Nokia device using the same battery type, such as the 5800, using a wall charger. There is a [[ARM/N900/Recover From Drained Battery|guide to battery drainage solving]].

This is a simplified guide for dual-booting with u-boot on Nokia N900.

'''You must be using the PR1.3 kernel and nothing else'''. You will likely end up in a reboot loop if you don't have this otherwise. To check this, in Settings -> About product, make sure you see:

<pre>Version: 20.2010.36-2</pre>

You will need a 2 GB microSD card or bigger.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel (The software hosted in extras-devel is not ready for normal users! PLEASE PLEASE PLEASE don't play with it unless you really know what you are doing. It is recommended to disable the extras-devel repository after you have installed the package below, and do not install any updated packages that you might be notified of while extras-devel is enabled. Be ready to file proper bug reports instead of posting complaints.)
# Install the 'uboot-pr13' package from 'System' section
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.
# From http://tablets-dev.nokia.com/meego-codedrop.php (type in your IMEI), download meego-handset-armv7l-n900-final-mod-1.1.0.0.20101101.3-mmcblk0p.raw.bz2 -- we require IMEI/EULA but in practice the images are redistributable under certain conditions, see the license files for more information.
# Follow the [[ARM/N900/Install/MMC#Installing Rootfs on external MMC card|instructions for installing a rootfs on an external MMC card]] and write the image to your microSD
# Insert the microSD, put back phone back cover (otherwise, microSD card won't be properly detected at startup by MeeGo) and turn on the N900, let U-boot menu time out and MeeGo will boot.
# Enjoy!

To boot back in to Maemo turn off your phone, then either remove the microSD and then turn on your phone, or turn it on and interrupt the boot during the countdown by pressing a button and then type "run noloboot".

If you want to remove U-boot you can as root in Maemo run: apt-get install --reinstall kernel kernel-flasher

If you are unable to get back into Maemo, please follow http://wiki.maemo.org/Updating_the_tablet_firmware in order to reflash your device. This will destroy your current Maemo setup, but return your device to a working state

For the technically minded, you can flasher '-F <firmware image> -u' and 'flasher -f zImage -R' to get your original kernel back and hopefully get back to your current Maemo setup. If you have used other kernels than PR1.3 kernel as is required, this will not work.

[[Category:N900]]

ARM/N900

2011-03-23T08:31:22Z

Fabo: /* Installing MeeGo on N900 */

= MeeGo for Nokia N900 =

The Nokia N900 Hardware Adaptation Team maintains the port of MeeGo for the N900. In these pages, you can download the fruits of our work (releases) and learn more about our work and even learn how to participate in it and contribute!

WARNING: These guides are experimental and everything you do with this guide is at your own responsibility and risk and will probably void your warranty.

[[ARM/N900/DeveloperEdition|'''MeeGo 1.2 Developer Edition for N900''']]

== Releases ==

In this section, you can download installable firmware images for your N900. In each release link, there is a set of release notes and an installation guide matching the release. Please read them through before installing.

[[ARM/N900/Releases/1.0|MeeGo 1.0 for Nokia N900]], released at 26/05/2010

[http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 for Nokia N900], released at 28/10/2010

[[ARM/N900/Releases/Daily|MeeGo Handset UX Daily builds for Nokia N900]]

[[ARM/N900/Releases/Weekly|MeeGo Handset UX Weekly builds for Nokia N900]]

== Documentation ==

=== Creating MeeGo images for N900 ===

[[ARM/Creating ARM image using MeeGo Image Creator|Creating image using MeeGo Image Creator]]

=== Installing MeeGo on N900 ===

* [[ARM/N900/Install/Dual_Boot|Dual Boot Maemo 5 (Fremantle) PR1.3 and MeeGo on N900 (recommended)]]
* [[ARM/N900/Install/MMC|MMC Installation]] — MMC Installation is the other recommended way to install MeeGo on your N900 device. It installs MeeGo to an external SD card and does not destroy the data from the internal memory of the N900 device.
* [[ARM/N900/Install/chroot|Chroot install]] — Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
* [[ARM/N900/Install/NFS|NFS-Root over usb networking]] — With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
* [[ARM/N900/Install/NAND|<s>Native install</s> (not supported with current MeeGo releases)]] — Native installation method is intended only for experienced N900 hackers at this point. If you choose to try it, you are doing it completely on your own risk.
* <s>[[ARM/N900/Install/kexec|Booting MeeGo with kexec]]</s>
* [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]

=== Troubleshooting ===

[[ARM/N900/Using_Rescue_Initrd|Using Rescue Initrd]]

[[ARM/N900/Restoring_Maemo|Restoring Maemo]]

[[ARM/N900/Tips_and_Tricks/N900_USB_Networking|USB Networking / SSH / root access]]

[[ARM/N900/Recover_From_Drained_Battery|How to recover from drained battery]]

== The team and the work ==

This hardware adaptation team maintains the port of MeeGo for the N900.

Due to the use of closed components in the hardware adaptation, this team
cannot run fully in the open. However, it will strive to minimize the
non-openness in its work related to those components and the number of
those components. Closed components will be maintained exclusively
by employees and subcontractors of Nokia.

Anyone is welcome to contribute and non-member contributions will be treated
with same process and review as member contributions.

We will be adding members to the team based on merit, by acceptance by
team lead after proposal on the agenda for a sync meeting.

Team communication is in English.

[[ARM/N900/Meetings|Team synchronisation meetings are held in #meego-meeting on irc.freenode.net]] every other Thursday at 9.00 EEST (8.00 CEST, 6.00 UTC, Wednesday 23.00 PDT). They will use the meeting bot, [http://meetbot.debian.net/Manual.html instructions can be found here]. This bot will automatically generate minutes, based on our interactions with it during the meeting.

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
! Name
! Role
! Affiliation
! IRC nickname
|-
| Harri Hakulinen || Team lead || Nokia || harha
|-
| Carsten Valdemar Munk || Maintainer || Nomovok || Stskeeps
|-
| Marko Saukko || Team member || Cybercom Turku || Sage
|-
| Jouni Peltonen || Team member || Cybercom Turku || jpeltonen
|-
| Sami Sirkiä || Team member || Cybercom Turku || ssirkia
|-
| Jari Smura || Team member || Cybercom Turku || jarismura
|-
| Kalle Lampila || Team member || Cybercom Tampere || kallam
|-
| Teemu Tuominen || Team member || Cybercom Tampere || theodor
|-
| Tuukka Mäkinen || Team member || Cybercom Tampere || tukem
|-
| Ville Marjusaari || Team member || Cybercom Tampere ||
|-
| Jarkko Nikula || Team member || Atomide || jhnikula
|-
| Jan-Simon Möller || Team member || Linux Foundation || dl9pf
|-
| Alexander Kanevskiy || Team member || Nokia || kad
|-
| Felipe Contreras || Team member || Nokia || felipec
|-
| Markus Lehtonen || Team member || Nokia || marquiz
|-
| Ameya Palande || Team member || Nokia || ameya
|-
| Sakari Poussa || Team member || Nokia || spoussa
|-
| Ilkka Koskinen || Team member || Nokia || ile
|-
| Mika Laitio || Team member || Tieto || lamikr
|-
|}

Our collaboration spaces are:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'N900' for team related topics.
* [http://webchat.freenode.net/?channels=meego-arm #meego-arm IRC channel on irc.freenode.net] ([http://trac.tspre.org/merbot/freenode/%23meego-arm/ IRC channel logs])
* Gitorious team, http://meego.gitorious.org/+meego-arm-n900 and all repositories on http://gitorious.org/meego-device-adaptation prefixed with n900_
* MeeGo OBS devel:devices:n900 project
* This wiki area
* For the closed components -only-:
** an internal Nokia mailing list: meego-arm
** An internal Nokia OBS project, usually referred to as 'internal OBS'

[[Category:Hardware]]
[[Category:N900]]

ARM/N900

2011-03-23T08:31:01Z

Fabo: /* Installing MeeGo on N900 */

= MeeGo for Nokia N900 =

The Nokia N900 Hardware Adaptation Team maintains the port of MeeGo for the N900. In these pages, you can download the fruits of our work (releases) and learn more about our work and even learn how to participate in it and contribute!

WARNING: These guides are experimental and everything you do with this guide is at your own responsibility and risk and will probably void your warranty.

[[ARM/N900/DeveloperEdition|'''MeeGo 1.2 Developer Edition for N900''']]

== Releases ==

In this section, you can download installable firmware images for your N900. In each release link, there is a set of release notes and an installation guide matching the release. Please read them through before installing.

[[ARM/N900/Releases/1.0|MeeGo 1.0 for Nokia N900]], released at 26/05/2010

[http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 for Nokia N900], released at 28/10/2010

[[ARM/N900/Releases/Daily|MeeGo Handset UX Daily builds for Nokia N900]]

[[ARM/N900/Releases/Weekly|MeeGo Handset UX Weekly builds for Nokia N900]]

== Documentation ==

=== Creating MeeGo images for N900 ===

[[ARM/Creating ARM image using MeeGo Image Creator|Creating image using MeeGo Image Creator]]

=== Installing MeeGo on N900 ===

* [[ARM/N900/Install/Dual_Boot|Dual Boot Maemo 5 (Fremantle) PR1.3 and MeeGo on N900 (recommended)]]
* [[ARM/N900/Install/MMC|MMC Installation]] — MMC Installation is the recommended way to install MeeGo on your N900 device. It installs MeeGo to an external SD card and does not destroy the data from the internal memory of the N900 device.
* [[ARM/N900/Install/chroot|Chroot install]] — Chroot install is a way to try out MeeGo by running it on top of Maemo 5 on your N900 device.
* [[ARM/N900/Install/NFS|NFS-Root over usb networking]] — With NFS-root install you can run MeeGo natively on your N900, without erasing Maemo 5, without flashing or using SD card. Rootfs speed over USB is the downside.
* [[ARM/N900/Install/NAND|<s>Native install</s> (not supported with current MeeGo releases)]] — Native installation method is intended only for experienced N900 hackers at this point. If you choose to try it, you are doing it completely on your own risk.
* <s>[[ARM/N900/Install/kexec|Booting MeeGo with kexec]]</s>
* [[ARM/N900/Install/U-Boot from scratch|Install U-boot from scratch]]

=== Troubleshooting ===

[[ARM/N900/Using_Rescue_Initrd|Using Rescue Initrd]]

[[ARM/N900/Restoring_Maemo|Restoring Maemo]]

[[ARM/N900/Tips_and_Tricks/N900_USB_Networking|USB Networking / SSH / root access]]

[[ARM/N900/Recover_From_Drained_Battery|How to recover from drained battery]]

== The team and the work ==

This hardware adaptation team maintains the port of MeeGo for the N900.

Due to the use of closed components in the hardware adaptation, this team
cannot run fully in the open. However, it will strive to minimize the
non-openness in its work related to those components and the number of
those components. Closed components will be maintained exclusively
by employees and subcontractors of Nokia.

Anyone is welcome to contribute and non-member contributions will be treated
with same process and review as member contributions.

We will be adding members to the team based on merit, by acceptance by
team lead after proposal on the agenda for a sync meeting.

Team communication is in English.

[[ARM/N900/Meetings|Team synchronisation meetings are held in #meego-meeting on irc.freenode.net]] every other Thursday at 9.00 EEST (8.00 CEST, 6.00 UTC, Wednesday 23.00 PDT). They will use the meeting bot, [http://meetbot.debian.net/Manual.html instructions can be found here]. This bot will automatically generate minutes, based on our interactions with it during the meeting.

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
! Name
! Role
! Affiliation
! IRC nickname
|-
| Harri Hakulinen || Team lead || Nokia || harha
|-
| Carsten Valdemar Munk || Maintainer || Nomovok || Stskeeps
|-
| Marko Saukko || Team member || Cybercom Turku || Sage
|-
| Jouni Peltonen || Team member || Cybercom Turku || jpeltonen
|-
| Sami Sirkiä || Team member || Cybercom Turku || ssirkia
|-
| Jari Smura || Team member || Cybercom Turku || jarismura
|-
| Kalle Lampila || Team member || Cybercom Tampere || kallam
|-
| Teemu Tuominen || Team member || Cybercom Tampere || theodor
|-
| Tuukka Mäkinen || Team member || Cybercom Tampere || tukem
|-
| Ville Marjusaari || Team member || Cybercom Tampere ||
|-
| Jarkko Nikula || Team member || Atomide || jhnikula
|-
| Jan-Simon Möller || Team member || Linux Foundation || dl9pf
|-
| Alexander Kanevskiy || Team member || Nokia || kad
|-
| Felipe Contreras || Team member || Nokia || felipec
|-
| Markus Lehtonen || Team member || Nokia || marquiz
|-
| Ameya Palande || Team member || Nokia || ameya
|-
| Sakari Poussa || Team member || Nokia || spoussa
|-
| Ilkka Koskinen || Team member || Nokia || ile
|-
| Mika Laitio || Team member || Tieto || lamikr
|-
|}

Our collaboration spaces are:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'N900' for team related topics.
* [http://webchat.freenode.net/?channels=meego-arm #meego-arm IRC channel on irc.freenode.net] ([http://trac.tspre.org/merbot/freenode/%23meego-arm/ IRC channel logs])
* Gitorious team, http://meego.gitorious.org/+meego-arm-n900 and all repositories on http://gitorious.org/meego-device-adaptation prefixed with n900_
* MeeGo OBS devel:devices:n900 project
* This wiki area
* For the closed components -only-:
** an internal Nokia mailing list: meego-arm
** An internal Nokia OBS project, usually referred to as 'internal OBS'

[[Category:Hardware]]
[[Category:N900]]

ARM/N900/Ideas

2011-03-18T19:00:02Z

Fabo: /* Ideas, feedback */

== Ideas, feedback ==

* Feel free to write here. Also put your name and details here, if already want to help on something.
* First idea: want to help to make this wiki more beautiful? (from Jukka)
** I'll take that. Suggestions welcome [[User:Amigadave|Amigadave]] 10:54, 17 March 2011 (UTC)
* How about having "reply to sender" in SMS sending functionality, seems a bit vital to me :) (from Tom Swindell AKA. alterego)
** Jukka: edited that in, thanks.
* Low hanging fruit: TV-out functionality in UI. Backend works (kernel), trivial change needed for fbdev-sgx (from Carsten Munk)
** Jukka: Yes, definitely let's try. (try: 'xrandr --output TV --auto' and 'echo pal > /sys/devices/platform/omapdss/display1/timings')
* How to easily install apps/packages, any UI to ease this? (idea from qgil)
** PackageKit UI (timoph and timakima committed to implementing it)
* VSync drivers in the kernel + SGX driver + X server?
** Comment from Carsten: Already there :)
* Up to date MeeGo Qt Components for creating native-looking UIs
** Jukka: Yes, being worked on, let's see.
* Kernel and userspace support for the N900's IR port
* Camera support (taking photos + videos with the back camera, reacting correctly to the camera shutter button + camera cover)
** Jukka: Work happening also here, see CoolStuff page (meegocamera).
* Up to date Qt Mobility 1.1/1.2 packages + latest Qt 4.7.2 packaged for development of apps
** Jukka: Qt 4.7.2 and Qt Mobility 1.2 are already in trunk.
* SSH server + MAD Developer application easily installable (for deploying using Qt Creator)
** Jukka: SSH runs always, MADDE let's investigate.
** [http://meego.com/users/fabo Fathi Boudra]: mad-developer is available (it's part of MeeGo SDK packages). It should be part of MeeGo images by default (accepted) but has a blocker issue preventing its inclusion in package groups ([https://bugs.meego.com/show_bug.cgi?id=13007 bug 13007]).
* Easy way to enable/select USB mass storage mode. Control panel applet with switch between usb networking and mass storage would be fine.
* New theme. Cool new theme (or several) that is special to this DevEdition, and sets the look and feel apart from the stock MeeGo.
* Find a solution to encourage & guide developers in open to utilize traditionally "grey" areas like DSP and ISP. Afaik both have enough openness to split up oss/non-oss work and have them running side by side. See felipec's comments irc:meego-arm/log.09-17-2010/15:11.
* NEON & Floating Point Optimizations for ARM (vkvraju)
** hard-fp work active and images will be coming soon to trunk, NEON optimizations also (Jukka)
* Latest PySide (Python for Qt) 1.0 or PyQt installed by default as most/majority of the applications use python (vkvraju)
* Add/Merge to contacts an unknown number from the call history (vkvraju)
* Block a number (from calling/SMS) from the call history or contacts (vkvraju)
* Speaker/hands-free support for calling and listening to music (vkvraju)
** Jukka: Hands-free should be working already, and speaker might be workable.
* Kernel & userspace support for FM Radio & Transmitter (vkvraju)
* Creating groups in contacts. Support for groups in contacts (QtContacts?) (vkvraju)
** We are using meego-handset People application by default, which doesn't have this feature in MeeGo 1.2. Not for DevEdition at this point. (Jukka)
* Sending SMS to groups (created in contacts) and sending to random but multiple contacts at once (vkvraju)
** See previous comment (Jukka)
* Fully functional and working LED. Useful to notify when a call comes. Notify while charging (USB/Wall) and many more such uses (vkvraju)
** This would be nice to have, maybe something for the community to work on. Let's make sure the enablers are there in DevEdition (Jukka).
* Ability to switch off one or more radios/chips (FM Receiver, Transmitter, Bluetooth, WLAN, 2G/3G, GPS/A-GPS) and also the ability to change their modes via settings (vkvraju)
* Device screen calibration support (vkvraju)
** Please describe why this would be needed? (Jukka)
** I thought calibration is a must for all touch-based (especially resistive screens) devices, no? N800 and N900 are the only touch-devices I have and both have screen calibration (vkvraju)
* Device screen brightness control. Preferably in the control panel (vkvraju)
** First of all, let's get backlight control working to save battery. Fine-tuning of brightness could be part of that work. (Jukka)
* If any of the above feedbacks/ideas are already being worked on as part of the immediate next release, then please update the "Use cases" section in the main page accordingly. Thanks (vkvraju)
** Well, no. The main use cases are something DevEdition team has committed to, anything else is extra. We will make the call in the DevEdition team whether to add something to the guaranteed use cases. (Jukka)
* Have own sample-media, including some test data for Calendar, People etc. (Jukka)

[[Category:N900]]

SDK/Meetings/Release/Agenda/20110222

2011-02-22T07:59:03Z

Fabo:

Add your proposed item with name in parenthesis.

* New team member (Azadeh)

* Regular image and sysroot creation (Fathi)
** The ks files need update.
** Has the MeeGo group reorg activity finished?

* Qemu skin packages (Jun/Jackie)
** Name: meego-sdk-qemu-skin

* New scripts for meego-sdk package (Jackie)
** meego-sdk-update-target
** meego-sdk-checkversion

* Qt Simualtor (Fathi)
** Pending review

* Toolchain
** Linux update (Xu/Jackie)
*** Fedora 14 64bits support is on going
** Windows update (Wenchao/Max)

Release Engineering

2011-02-10T19:03:01Z

Fabo: /* Team */

== Release Engineering ==

The Release Engineering team manages planning and producing all the MeeGo releases, including the weekly engineering releases, milestone releases, and MeeGo product releases. The team maintains the process and tooling for organized and automated build and release creation and maintains hardware platform-specific software in MeeGo.

=== Team ===

* '''[http://meego.com/users/rolla Rolla Selbak]''' is the head of the MeeGo release engineering team. She is responsible for the MeeGo release engineering process and code line policy, and for overseeing and supporting the planning and production of the MeeGo Core OS and device category-specific releases on supported hardware platforms, while managing the MeeGo release engineering team.
* '''[http://meego.com/users/kad Alexander Kanevskiy]''' is the MeeGo Core OS release manager, responsible for planning and producing core OS releases.
* '''[http://meego.com/users/ulf Ulf Hofemeier]''' is the MeeGo Handset UX release lead, responsible for planning and producing handset releases.
* '''[http://meego.com/users/stskeeps Carsten Munk]''' is responsible for maintaining the MeeGo releases on the Nokia N900 hardware platform.

=== Terms and conventions ===

==== Supported CPU architectures ====
* '''ia32''' - 32bit [[wikipedia:Intel Atom|Intel Atom]], [[wikipedia:Intel Core 2|Intel Core 2]] or better CPU (support for [[wikipedia:SSSE3|SSSE3]] is required)
* '''armv7l''' - [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, [[wikipedia:Endianness|Little-endian]])

==== Obsoleted CPU architectures ====
* '''armv5tel''' - [[wikipedia:ARM_architecture|ARM architecture]] version 5 compatible CPUs (Thumb, [[wikipedia:Endianness|Little-endian]])

==== Release Versioning ====
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]

=== Release Content ===

For each supported category, release should contain:

* '''Repositories''' (for each supported category). Repositories contains:
** source and binary packages for supported architectures for that category
** debug packages for corresponding binary packages
** build counters of packages for different architectures should be synced (relsync)
** repository metadata (repo-md metadata, comps, ...)
* '''Images''' (for each supported category set of images and supported HW might vary). Images contains:
** filesystem image(s). flashable or usable in other way.
** source configuration files needed to re-create this images (e.g. ks file)
** log file which shows process of creating that image
** list of packages included in that image
** image specific documentation, e.g. flashing guides (optional)
** MANIFEST file which contains checksums for files in the image directory
* '''Release notes'''
** changed packages
** changes in features (new/removed)
** bugfixes information
** known issues
** location of the images
** list of supported hardware for those images
** links to all additional support information if needed
* '''QA information'''
** which image was tested on which HW.
** type of the tests.
** tests passrate
** highlights if necessary

=== Release Process ===

* [[Release_Engineering/Release_Timeline|Release lifecycle timeline]]
* [[Release_Engineering/Process|MeeGo release process]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
* [[Release_Engineering/Software_update_process|MeeGo Software update process]]

=== Release Plans ===
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]

=== Downloads ===

* [http://repo.meego.com/MeeGo/releases/ MeeGo Official Releases]
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]
** [http://repo.meego.com/MeeGo/builds/1.0.80/ Development releases for upcoming 1.1 release]

SDK/Packages group

2011-01-27T16:28:50Z

Fabo: /* Current development packages list */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 0
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 5
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 665M
| 570
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot-full.list
|-
| Core
| ia32
| 765M
| 581
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot-full.list
|-
| Handset
| armv7l
| 668M
| 5
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot-full.list
|-
| Handset
| ia32
| 768M
| 6
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot-full.list
|}

SDK/Packages group

2011-01-27T13:32:25Z

Fabo: /* Complete development packages list */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 81
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 665M
| 570
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot-full.list
|-
| Core
| ia32
| 765M
| 581
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot-full.list
|-
| Handset
| armv7l
| 668M
| 5
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot-full.list
|-
| Handset
| ia32
| 768M
| 6
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot-full.list
|}

SDK/Packages group

2011-01-27T13:32:06Z

Fabo: /* Complete development packages list */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 81
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 665M
| 570
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot-full.list
|-
| Core
| ia32
| 765M
| 581
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot-full.list
|-
| Handset
| armv7l
| 668M
| 5
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot-full.list
|-
| Handset
| ia32
| 768
| 6
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot-full.list
|}

SDK/Packages group

2011-01-27T12:54:19Z

Fabo: /* Complete development packages list */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 81
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 665M
| 570
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot-full.list
|-
| Core
| ia32
| 765M
| 581
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot-full.list
|-
| Handset
| armv7l
| 668M
| 5
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot-full.list
|-
| Handset
| ia32
| ?
| 6
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot-full.list
|}

SDK/Packages group

2011-01-27T12:33:53Z

Fabo: /* Complete development packages list */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 71
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 81
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 665M
| 548
| http://wiki.meego.com/images/Meego-core-armv7l-madde-sysroot-full.list
|-
| Core
| ia32
| 765M
| 561
| http://wiki.meego.com/images/Meego-core-ia32-madde-sysroot-full.list
|-
| Handset
| armv7l
| ?
| 7
| http://wiki.meego.com/images/Meego-handset-armv7l-madde-sysroot-full.list
|-
| Handset
| ia32
| ?
| 7
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot-full.list
|}

SDK/Release

2011-01-23T09:06:31Z

Fabo: /* Host Packages */

=== Status conventions ===

{| cellpadding="5" cellspacing="0" border="1"
! Status
|-
| style="background-color:#ffff00" | Planned
|-
| style="background-color:#00ff00" | OK/Done
|-
| style="background-color:#ff0000" | NOK/Late
|}

== Metrics ==

* [http://bugs.meego.com/metrics/?stats=MeeGo_Platform_-_All&component=MeeGo%20SDK metrics]
* [http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=product&z_axis_field=target_milestone&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+SDK+features&product=MeeGo+Tablet+Features&version=1.2&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= reports]

== Features status ==

{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK features
|version=1.2
|bar=status
|group=component
}}

{{#bugzilla:
|columns=id,component,priority,status,summary
|product=MeeGo SDK Features
|version=1.2
|severity=enhancement
|group=status
|sort=component,priority,id
}}

[http://bugs.meego.com/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=WAITING&bug_status=REOPENED&product=MeeGo%20SDK%20features&query_format=advanced&order=bug_id&query_based_on= Detailed report in Featurezilla]

== Bugs status ==

{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK
|bar=status
|group=product
|status=NEW,NEEDINFO,ASSIGNED,REOPENED
}}

{{#bugzilla:
|columns=id,component,priority,status,summary
|product=MeeGo SDK
|group=status
|sort=component,priority,id
|status=NEW,NEEDINFO,ASSIGNED,REOPENED
}}

[http://bugs.meego.com/buglist.cgi?bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=REOPENED&product=MeeGo%20SDK&query_format=advanced&order=bug_id&query_based_on= Detailed report in Bugzilla]

== Hosts status ==

* for details, see [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Host'''
| '''Status'''
|-
| Debian Lenny (5.0) i386
| style="background-color:#00ff00" | OK
|-
| Debian Lenny (5.0) amd64
| style="background-color:#00ff00" | OK
|-
| Fedora 12 i386
| style="background-color:#00ff00" | OK
|-
| Fedora 12 x86_64
| style="background-color:#00ff00" | OK
|-
| Fedora 13 i386
| style="background-color:#00ff00" | OK
|-
| Fedora 13 x86_64
| style="background-color:#00ff00" | OK
|-
| MeeGo 1.1 i586
| style="background-color:#00ff00" | OK
|-
| MeeGo Trunk i586
| style="background-color:#00ff00" | OK
|-
| Ubuntu Karmic (9.10) i386
| style="background-color:#00ff00" | OK
|-
| Ubuntu Karmic (9.10) amd64
| style="background-color:#00ff00" | OK
|-
| Ubuntu Lucid (10.04) i386
| style="background-color:#00ff00" | OK
|-
| Ubuntu Lucid (10.04) amd64
| style="background-color:#00ff00" | OK
|-
| Ubuntu Maverick (10.10) i386
| style="background-color:#00ff00" | OK
|-
| Ubuntu Maverick (10.10) amd64
| style="background-color:#00ff00" | OK
|-
| openSUSE 12 i586
| style="background-color:#00ff00" | OK
|-
| openSUSE 12 x86_64
| style="background-color:#00ff00" | OK
|-
| openSUSE 13 i586
| style="background-color:#00ff00" | OK
|-
| openSUSE 13 x86_64
| style="background-color:#00ff00" | OK
|}

== Target status ==

* for details, see [https://build.meego.com/project/monitor?project=Tools:SDK:Target Tools:SDK:Target project] on MeeGo OBS

{| cellpadding="5" cellspacing="0" border="1"
! Target !! Status
|-
| MeeGo 1.1 armv5tel
| style="background-color:#00ff00" | OK
|-
| MeeGo 1.1 armv7l
| style="background-color:#00ff00" | OK
|-
| MeeGo 1.1 i586
| style="background-color:#00ff00" | OK
|-
| MeeGo Trunk armv5tel
| style="background-color:#00ff00" | OK
|-
| MeeGo Trunk armv7l
| style="background-color:#00ff00" | OK
|-
| MeeGo Trunk i586
| style="background-color:#00ff00" | OK
|}

== Host Packages ==

{| cellpadding="5" cellspacing="0" border="1"
! Package !! Package Maintainer(s) !! Subsystem Maintainer(s) !! Requirements !! Open Bugs !! Status
|-
| arm-2009q1
| Al Nikolov
| [http://meego.com/users/kant Jarmo Kant/jake-k]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/qemu-maemo/gles-libs gles-libs]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/suihkulokki Riku Voipio/suihkulokki]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/madde madde]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| Jari Ihatsu/[http://meego.com/users/too Tomi Ollila/Domo]
|
|
| style="background-color:#00ff00" | OK
|-
| meego-qemu-ia32
| [http://meego.com/users/johnchen Zhang Chen/john]
| [http://meego.com/users/johnchen Zhang Chen/john]
|
|
| style="background-color:#00ff00" | OK
|-
| meego-sdk
| [http://meego.com/users/fabo Fathi Boudra/fabo] [http://meego.com/users/wwhbuaa Jackie Wu/Jackie] [http://meego.com/users/johnchen Zhang Chen/john]
| [http://meego.com/users/fabo Fathi Boudra/fabo] [http://meego.com/users/wwhbuaa Jackie Wu/Jackie] [http://meego.com/users/johnchen Zhang Chen/john]
|
|
| style="background-color:#00ff00" | OK
|-
| meego-sdk-i586-toolchain
| [http://meego.com/users/wwhbuaa Jackie Wu/Jackie]
| [http://meego.com/users/wwhbuaa Jackie Wu/Jackie]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meegotouch/libmeegotouch meego-sdk-libmeegotouch]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://qt.gitorious.org/qt meego-sdk-qt]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/mauricek Maurice Kalinowski/MauriceK]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/qt-creator meego-sdk-qt-creator]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/mauricek Maurice Kalinowski/MauriceK]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/qemu-maemo/qemu qemu-arm]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/suihkulokki Riku Voipio/suihkulokki]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/meego-emulator-qemugl-x86 qemu-gl]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://qt.gitorious.org/qt qt-tools]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/mauricek Maurice Kalinowski/MauriceK]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://www.guru-group.fi/~too/sw/utfs/ utfs]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| Jari Ihatsu/[http://meego.com/users/too Tomi Ollila/Domo]
|
|
| style="background-color:#00ff00" | OK
|}

== Target Packages ==

{| cellpadding="5" cellspacing="0" border="1"
! Package !! Package Maintainer(s) !! Subsystem Maintainer(s) !! Requirements !! Open Bugs !! Status
|-
| [http://meego.gitorious.org/qemu-maemo/gles-libs gles-libs]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/suihkulokki Riku Voipio/suihkulokki]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/qemu-maemo/gles-libs kmod-kfgles2]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/suihkulokki Riku Voipio/suihkulokki]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/meego-emulator-virtiogl-x86 kmod-virtiogl]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://lftp.yar.ru/ lftp]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/madde mad-developer]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| Jari Ihatsu/[http://meego.com/users/too Tomi Ollila/Domo]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/meego-sdk-qemugl-addon meego-sdk-qemugl-addon]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
| [http://meego.com/users/zhiyuan Zhiyuan Lv/Zhiyuan]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://meego.gitorious.org/meego-developer-tools/meego-simulator-launcher meego-simulator-launcher]
| [http://meego.com/users/haitao Haitao Feng/Haitao]
| [http://meego.com/users/haitao Haitao Feng/Haitao]
|
|
| style="background-color:#00ff00" | OK
|-
| [http://www.guru-group.fi/~too/sw/utfs/ utfs]
| [http://meego.com/users/fabo Fathi Boudra/fabo]
| Jari Ihatsu/[http://meego.com/users/too Tomi Ollila/Domo]
|
|
| style="background-color:#00ff00" | OK
|}

== Images ==

{| cellpadding="5" cellspacing="0" border="1"
! Image !! Target !! Vertical !! Status
|-
| MADDE sysroot
| MeeGo 1.1 armv7l
| Core
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo 1.1 i586
| Core
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo 1.1 armv7l
| Handset
| style="background-color:#ff0000" | NOK
|-
| MADDE sysroot
| MeeGo 1.1 i586
| Handset
| style="background-color:#ff0000" | NOK
|-
| MADDE sysroot
| MeeGo 1.1 i586
| Netbook
| style="background-color:#ff0000" | NOK
|-
| MADDE sysroot
| MeeGo Trunk armv7l
| Core
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo Trunk i586
| Core
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo Trunk armv7l
| Handset
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo Trunk i586
| Handset
| style="background-color:#00ff00" | OK
|-
| MADDE sysroot
| MeeGo Trunk i586
| Netbook
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo 1.1 armv7l
| Core
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo 1.1 i586
| Core
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo 1.1 armv7l
| Handset
| style="background-color:#00ff00" | OK
|-
| QEMU
| MeeGo 1.1 i586
| Handset
| style="background-color:#00ff00" | OK
|-
| QEMU
| MeeGo 1.1 i586
| Netbook
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo Trunk armv7l
| Core
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo Trunk i586
| Core
| style="background-color:#ff0000" | NOK
|-
| QEMU
| MeeGo Trunk armv7l
| Handset
| style="background-color:#00ff00" | OK
|-
| QEMU
| MeeGo Trunk i586
| Handset
| style="background-color:#00ff00" | OK
|-
| QEMU
| MeeGo Trunk i586
| Netbook
| style="background-color:#00ff00" | OK
|}

SDK/Meetings/Release/MeetingMinutes/20110118

2011-01-19T15:26:43Z

Fabo:

* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-08.02.html Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-08.02.txt Minutes (text)]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-08.02.log.html Log]

SDK/Meetings/Release/MeetingMinutes/20110111

2011-01-19T15:26:19Z

Fabo:

* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-08.10.html Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-08.10.txt Minutes (text)]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-08.10.log.html Log]

SDK/Meetings/Release/MeetingMinutes/20110118

2011-01-19T05:47:35Z

Fabo: Created page with "* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-18-08.02.html Minutes] * [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-18-08.0…"

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-18-08.02.html Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-18-08.02.txt Minutes (text)]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-18-08.02.log.html Log]

SDK/Meetings/Release/MeetingMinutes/20110111

2011-01-19T05:46:19Z

Fabo: Created page with "* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-11-08.10.html Minutes] * [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-11-08.1…"

* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-11-08.10.html Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-11-08.10.txt Minutes (text)]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2011-01-11-08.10.log.html Log]

Maintainers structure

2011-01-18T19:39:08Z

Fabo: /* qt-mtf */

== MeeGo development area structure ==

=== content-fw ===
Development area maintainers: [http://meego.com/users/lamadon Jean Luc Lamadon]

{| class="wikitable" border="1"
|-
! Packages
! Maintainers
! Additional packages' names
|-
| tracker || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| libqttracker || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| libqtsparql || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| libqtsparql-tracker-extensions || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| tumbler || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| libthumbnailer || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| maemo-video-thumbnailer || [http://meego.com/users/maimishr Maitrey Mishra]
|-
| libcontentaction || [http://meego.com/users/maimishr Maitrey Mishra]
|}

=== qt-mtf ===
Development area maintainers: [http://meego.com/users/kaitlin Kaitlin Rupert] / [http://meego.com/users/fabo Fathi Boudra]

{| class="wikitable" border="1"
|-
! Packages
! Maintainers
! Additional packages' names
|-
| automoc4 || [http://meego.com/users/fabo Fathi Boudra]
|-
| clean-device || [http://meego.com/users/kedz David Kedves]
|-
| contextkit || [http://meego.com/users/lamadon Jean-Luc Lamadon]
|-
| contextkit-maemo || [http://meego.com/users/lamadon Jean-Luc Lamadon]
|-
| libmeegochat || ?
|-
| libmeegotouch || [http://meego.com/users/msafr Miroslav Safr] || meegotouch-demos, meegotouch-config-default
|-
| libsocialweb-qml || ?
|-
| libsocialweb-qt || ?
|-
| marmazon || ?
|-
| meegotouch-applauncherd || ?
|-
| meegotouch-compositor || [http://meego.com/users/msafr Miroslav Safr]
|-
| meegotouch-controlpanel || [http://meego.com/users/gabor Gabor Juhasz]
|-
| meegotouch-controlpanelapplets || [http://meego.com/users/kedz David Kedves]
|-
| meegotouch-feedback || [http://meego.com/users/rcherian Rakesh Cherian] [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-feedbackreactionmaps || [http://meego.com/users/rcherian Rakesh Cherian] [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-home || [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-inputmethodengine || [http://meego.com/users/rcherian Rakesh Cherian] [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-inputmethodframework || [http://meego.com/users/rcherian Rakesh Cherian] [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-inputmethodkeyboard || [http://meego.com/users/rcherian Rakesh Cherian] [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-qt-style || not yet added
|-
| meegotouch-systemui || [http://meego.com/users/araujo Luis Araujo]
|-
| meegotouch-theme || [http://meego.com/users/msafr Miroslav Safr]
|-
| meegotouchcp-datetime || [http://meego.com/users/gabor Gabor Juhasz]
|-
| meegotouchcp-language || [http://meego.com/users/gabor Gabor Juhasz]
|-
| meegotouchcp-regionformat || [http://meego.com/users/gabor Gabor Juhasz]
|-
| phonon || [http://meego.com/users/fabo Fathi Boudra]
|-
| qca2 || [http://meego.com/users/fabo Fathi Boudra]
|-
| qca2-ossl || [http://meego.com/users/fabo Fathi Boudra]
|-
| qjson || ?
|-
| qmf || [http://meego.com/users/fabo Fathi Boudra]
|-
| qt || [http://meego.com/users/fabo Fathi Boudra]
|-
| qt-creator || [http://meego.com/users/fabo Fathi Boudra]
|-
| qt-mobility || [http://meego.com/users/fabo Fathi Boudra]
|-
| qt-obex-ftp-library || ?
|-
| qt-web-runtime || [http://meego.com/users/fabo Fathi Boudra]
|-
| qtwebkit || [http://meego.com/users/fabo Fathi Boudra]
|-
|}

* Development area maintainers = accepting in devel. area and submitting to Trunk:Testing
* Maintainers = submitting to devel. area

SDK/Road to 1.2

2011-01-18T18:42:17Z

Fabo: Created page with "=MeeGo 1.1.2 SDK Update= '''Version''': 1.1.2 '''Related Release''': MeeGo 1.1 SDK This update is highly recommended for all users running MeeGo 1.1 SDK. == Changes in t…"

=MeeGo 1.1.2 SDK Update=

'''Version''': 1.1.2

'''Related Release''': MeeGo 1.1 SDK

This update is highly recommended for all users running MeeGo 1.1 SDK.

== Changes in this release ==
This release includes the following changes for MeeGo 1.1 SDK:
* Ubuntu 10.10 support is added.
* MeeGo SDK now supports Windows XP and Windows 7 operating systems. For instructions, see http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows.

* The following new targets are introduced:
** meego-core-armv7l-1.1.2
** meego-handset-ia32-1.1.2
** meego-netbook-ia32-1.1.2

* The following new runtimes are introduced:
** meego-handset-ia32-qemu-1.1.2-runtime
** meego-netbook-ia32-qemu-1.1.2-runtime

* Qemu enhancement
** The OpenGL acceleration support for MeeGo image (IA32 only) running on Qemu.
** Enable ALSA as audio backend.(Linux only)
** Run MeeGo image without kvm support. (IA32 and Linux only)

* The following components have been updated:
** libmeegotouch
** libqtwebkit-devel, qmf-devel, zypper packages have been added to the sysroot
** kmod-virtiogl (Inside runtime update to enable OpenGL acceleration for IA32.)
** meego-sdk-qemugl-addon (Inside runtime update to enable OpenGL acceleration for IA32.)
** qemu (Qemu update with OpenGL acceleration for IA32 image.)

== Fixed bugs ==
The following bugs have been fixed in this release:
* http://bugs.meego.com/show_bug.cgi?id=8938: Linker error when trying to compile MTF application with i586 sysroot/toolchain
* http://bugs.meego.com/show_bug.cgi?id=11679: QEMUGL should have more check of GL capabilities before enabling GL acceleration
* http://bugs.meego.com/show_bug.cgi?id=10945: QEMU GL acceleration does not work with MeeGo 1.1 image when mcompositor takes effect
* http://bugs.meego.com/show_bug.cgi?id=10667: When start Meego Runtime the UBUNTU will lose sound
* http://bugs.meego.com/show_bug.cgi?id=11271: Qemu cannot be launched on Ubuntu 10.10, kernel could boot up, but UI does not show up due to the crash of "syuid" and "duihome"
* http://bugs.meego.com/show_bug.cgi?id=11675: Handset image (1.1 release) cannot boot to UI if "kvm" is disabled

For more information, see the bug descriptions in http://bugs.meego.com.

== Instructions for updating the SDK==
'''To upgrade the SDK in the Linux operating system''':

1. Remove the Qt Tools directory before creating the MeeGo 1.1.2 SDK target. Use the following commands:
Under 32-bits OS: sudo rm -rf /usr/lib/madde/linux-i686/tools/qt-tools-4.7.0-*
Under 64-bits OS: sudo rm -rf /usr/lib/madde/linux-x86_64/tools/qt-tools-4.7.0-*

2. Update the distribution and create the required MeeGo 1.1.2 SDK targets. For instructions, see http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux.

3. Configure the required runtimes. For instructions, see http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes.

'''To upgrade the SDK in the Windows operating system''':

1. Uninstall the previous MeeGo 1.1 SDK.

2. Install and configure MeeGo 1.1.2 SDK on your Windows development system. For instructions, see section http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows.

User:Fabo/meego.js

2011-01-13T18:57:32Z

Fabo: Blanked the page

User:Fabo/meego.js

2011-01-13T18:54:33Z

Fabo: Created page with "{{subst:wikEd}}"

SDK/Packages group

2011-01-13T18:48:32Z

SDK

2011-01-13T16:02:56Z

Fabo: /* SDK Team */

= 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]] - 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 SDK team. MeeGo SDK team consists of team members from various companies involved in MeeGo. The goal is to create one SDK suitable for all the verticals and is extend-able with plugins for more specific needs.

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

=== SDK Team ===

* [http://meego.com/users/veli Veli Kaksonen] - Program Manager
* Ville Lavonius - Product Manager
* [http://meego.com/users/bspencer Bob Spencer] - Architect
* [http://meego.com/users/fabo Fathi Boudra] - Release Manager
* Kerry Jiang
* [http://meego.com/users/wwhbuaa Jackie Wu]
* [http://meego.com/users/johnchen Zhang Chen]
* [http://meego.com/users/haitao Haitao Feng]
* Jari Ihatsu
* [http://meego.com/users/mauricek Maurice Kalinowski]
* [http://meego.com/users/kant Jarmo Kant]
* [http://meego.com/users/zhiyuan Zhiyuan Lv]
* Al Nikolov
* [http://meego.com/users/too Tomi Ollila]
* Juha Riihimäki
* [http://meego.com/users/suihkulokki Riku Voipio]
* [http://meego.com/users/juntian Jun Tian]
* Wang Wenchao
* [http://wiki.meego.com/User:Maxayu Max A Yu] ([[SDK/MeeGo SDK for Windows |MeeGo SDK for Windows]])

==== SubTeams ====

* [[SDK/Architecture]]
* [[SDK/API]]
* [[SDK/Release]]
* [[SDK/Toolchains]]
* [[SDK/QA]]
* [[SDK/Documentation]]
* [[SDK/Installation]]
* [[SDK/Qemu]]

=== 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

==== 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

2011-01-13T16:01:50Z

Fabo: /* SubTeams */

= 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]] - 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 SDK team. MeeGo SDK team consists of team members from various companies involved in MeeGo. The goal is to create one SDK suitable for all the verticals and is extend-able with plugins for more specific needs.

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

=== SDK Team ===

* [http://meego.com/users/veli Veli Kaksonen] - Program Manager
* Ville Lavonius - Product Manager
* [http://meego.com/users/bspencer Bob Spencer] - Architect
* [http://meego.com/users/fabo Fathi Boudra] - Release Manager
* Kerry Jiang
* [http://meego.com/users/wwhbuaa Jackie Wu]
* [http://meego.com/users/johnchen Zhang Chen]
* [http://meego.com/users/haitao Haitao Feng]
* Jari Ihatsu
* [http://meego.com/users/mauricek Maurice Kalinowski]
* [http://meego.com/users/kant Jarmo Kant]
* [http://meego.com/users/zhiyuan Zhiyuan Lv]
* Al Nikolov
* [http://meego.com/users/too Tomi Ollila]
* [http://meego.com/users/suihkulokki Riku Voipio]
* [http://meego.com/users/juntian Jun Tian]
* Wang Wenchao
* [http://wiki.meego.com/User:Maxayu Max A Yu] ([[SDK/MeeGo SDK for Windows |MeeGo SDK for Windows]])

==== SubTeams ====

* [[SDK/Architecture]]
* [[SDK/API]]
* [[SDK/Release]]
* [[SDK/Toolchains]]
* [[SDK/QA]]
* [[SDK/Documentation]]
* [[SDK/Installation]]
* [[SDK/Qemu]]

=== 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

==== 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/Qemu

2011-01-13T15:59:00Z

Fabo: /* The team and the work */

= MeeGo QEMU Team =

MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.

== Consumers of QEMU ==

Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.

* MeeGo Qemu
** OpenGL ES 2.0 accelerated QEMU
** http://wiki.meego.com/ARM/Meego_on_Qemu
** Smoke test: Maemo5 and latest Meego N900 images boot and display UI
* Qemugl
** OpenGL accelerated Qemu for intel images
** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools
** Smoke test: That x86 handset and netbook images boot and display UI
* OBS Qemu
** Used internaly by OBS to build ARM packages
** url?
** Smoke test: arm build round without regressions
* Scratchbox Qemu
** Used by scratchbox to allow building ARM packages
** url: merged with MeeGo Qemu.
** Smoke test: arm build round without regressions

== Development ==

The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].

=== Version control strategy ===

In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego".

$ git clone git://git.qemu.org/qemu.git
$ cd qemu
$ git remote add meego git://gitorious.org/qemu-maemo/qemu.git
$ git fetch meego

The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing
causes some pain, but that should be seen as an incentive to push the patches upstream.

Qemu head (origin/master)
|
(periodic rebase)
|
MeeGo Qemu master (meego/master)
|
|
Everyones working branches ^

Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.

Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.

=== Submitting merge requests to MeeGo QEMU ===

Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.

Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical

* Cherry-pick commits from your working branch

$ git fetch meego # Make sure you are up to date
$ git checkout -b temp-branch-name meego/master
$ git log your-local-working-branch # pick the commit-id's of changes you want
$ git cherry-pick commit-id
$ vi foo.c # cleanup if necessary
$ commit -a --amend # improve commit message if necessary
$ git push meego temp-branch-name

* rebase working branch on top of latest dvcs

$ git fetch meego
$ git checkout -b temp-branch-name your-local-working-branch
$ git rebase -i meego/master
$ # follow instructions on editor
$ git push master temp-branch-name

Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git
merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.

Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.

== Documentation ==

=== Building Qemu ===

For ARM

git clone git://gitorious.org/qemu-maemo/gles-libs.git
cd gles-libs/dgles2
./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2
make install

git clone git://gitorious.org/qemu-maemo/qemu.git
cd qemu
./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2
make

=== Creating MeeGo Qemu images for N900 ===

=== Creating MeeGo Qemu images for Intel ===

Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.

=== Troubleshooting ===

== The team and the work ==

This QEMU adaptation team maintains and develops Qemu for MeeGo.

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
! Name
! Area
! Role
! Affiliation
! IRC nickname
|-
| Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki
|-
| Juha Riihimäki || Arm system || Team member || Nokia ||
|-
| [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo
|}

Our collaboration spaces are:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.
* [http://webchat.freenode.net/?channels=meego-sdk #meego-sdk IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])
* #qemu IRC channel on irc.oftc.net
* Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo
* [https://build.meego.com/project/monitor?project=Tools:SDK:Host Tools:SDK:Host project] on MeeGo OBS
* xxx project on MeeGo OBS
* This wiki area

[[Category:SDK]]

SDK/Qemu

2011-01-13T15:56:20Z

Fabo: /* The team and the work */

= MeeGo QEMU Team =

MeeGo Qemu team maintains QEMU system emulator for MeeGo SDK and QEMU linux-user emulator for OBS builders. Legacy support for scratchbox and Nokia N900 Running Maemo5 is provided as well.

== Consumers of QEMU ==

Currently each and every consumer of QEMU under the MeeGo umbrella has their own version of Qemu. The plan is to migrate all this versions to a single repository, merge all code together, and then start tagging releases which will be same for all.

* MeeGo Qemu
** OpenGL ES 2.0 accelerated QEMU
** http://wiki.meego.com/ARM/Meego_on_Qemu
** Smoke test: Maemo5 and latest Meego N900 images boot and display UI
* Qemugl
** OpenGL accelerated Qemu for intel images
** http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools
** Smoke test: That x86 handset and netbook images boot and display UI
* OBS Qemu
** Used internaly by OBS to build ARM packages
** url?
** Smoke test: arm build round without regressions
* Scratchbox Qemu
** Used by scratchbox to allow building ARM packages
** url: merged with MeeGo Qemu.
** Smoke test: arm build round without regressions

== Development ==

The main repository For MeeGo Qemu is [http://meego.gitorious.org/qemu-maemo MeeGo Qemu on gitorious]. Upstream is at [http://www.qemu.org qemu.org].

=== Version control strategy ===

In this documentation we shall refer to upstream git as "origin" and the the MeeGo QEMU gitorious repository as "meego".

$ git clone git://git.qemu.org/qemu.git
$ cd qemu
$ git remote add meego git://gitorious.org/qemu-maemo/qemu.git
$ git fetch meego

The rule of thumb in development is "keep up to date with upstream". To achieve this, we rebase with upstream often. rebasing
causes some pain, but that should be seen as an incentive to push the patches upstream.

Qemu head (origin/master)
|
(periodic rebase)
|
MeeGo Qemu master (meego/master)
|
|
Everyones working branches ^

Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.

Being branches on top of rebased branches means one cant just "merge" changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.

=== Submitting merge requests to MeeGo QEMU ===

Gitorious provides "request merge" functionality, which can be used to propose changes to MeeGo Qemu.

Alternatively, people with commit access to MeeGo gitorious can push their branches for merging to MeeGo gitorious directly.git offers infinite amount of was to do that, but there is two that are probably most practical

* Cherry-pick commits from your working branch

$ git fetch meego # Make sure you are up to date
$ git checkout -b temp-branch-name meego/master
$ git log your-local-working-branch # pick the commit-id's of changes you want
$ git cherry-pick commit-id
$ vi foo.c # cleanup if necessary
$ commit -a --amend # improve commit message if necessary
$ git push meego temp-branch-name

* rebase working branch on top of latest dvcs

$ git fetch meego
$ git checkout -b temp-branch-name your-local-working-branch
$ git rebase -i meego/master
$ # follow instructions on editor
$ git push master temp-branch-name

Where the working branches are "temporary" in nature. Eg once the code in the working branches have been applied (via git
merge/cherry-pick/rebase or by hand), that working branch is thrown away and a new branch is created.

Being branches on top of rebased branches means one cant just "merge"changes from upstream branches - one either must rebase their own branch, or cherrypick selected changes in.

== Documentation ==

=== Building Qemu ===

For ARM

git clone git://gitorious.org/qemu-maemo/gles-libs.git
cd gles-libs/dgles2
./configure --enable-glx --enable-x11 --enable-osmesa --prefix=/opt/dgles2
make install

git clone git://gitorious.org/qemu-maemo/qemu.git
cd qemu
./configure --target-list="arm-softmmu arm-linux-user" --enable-gles2 --gles2dir=/opt/dgles2
make

=== Creating MeeGo Qemu images for N900 ===

=== Creating MeeGo Qemu images for Intel ===

Meego [http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools Qemu Image instructions] for 1.1.

=== Troubleshooting ===

== The team and the work ==

This QEMU adaptation team maintains and develops Qemu for MeeGo.

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
! Name
! Area
! Role
! Affiliation
! IRC nickname
|-
| Riku Voipio || Linux-user and Arm system || Maintainer || Nokia || suihkulokki
|-
| Juha Riihimäki || Arm system || Team member || Nokia ||
|-
| [http://meego.com/users/fabo Fathi Boudra] || || Package maintainer || Nokia || fabo
|}

Our collaboration spaces are:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QEMU' for team related topics.
* [http://webchat.freenode.net/?channels=meego-sdk #meego-sdk IRC channel on irc.freenode.net]([http://trac.tspre.org/merbot/freenode/%23meego-sdk/ IRC channel logs])
* #qemu IRC channel on irc.oftc.net
* Gitorious team, http://gitorious.org/+meego-qemu-developers and all repositories on http://meego.gitorious.org/qemu-maemo
* MeeGo OBS xxx project
* This wiki area

[[Category:SDK]]

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

2011-01-13T10:22:13Z

Fabo: Please, move this section somewhere else. That's an advanced usage already.

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===


<ol>
<li>Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>. 
Replace ${distribution}/${version} with one of the following: "debian/5.0", "ubuntu/09.10", "ubuntu/10.04" or "ubuntu/10.10".
<pre>deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ / </pre>
</li>
<li>Add the repository public key:
<pre>$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -</pre>
</li>
<li>Update the packages database:
<pre>$ sudo apt-get update</pre>
</li>
<li>To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.
<pre>$ apt-cache policy madde</pre>
</li>
</ol>

=== On Fedora ===

<ol>
<li>Go to the yum repository directory:
<pre>$ cd /etc/yum.repos.d/ </pre>
</li>
<li>Add the MeeGo SDK yum repository. 
Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".
<pre>$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
<li>Install the signing key:
<pre>$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key </pre>
</li>
<li>Update the packages database:
<pre>$ sudo yum update</pre>
</li>
</ol>

=== On MeeGo ===
<ul>
<li>To add the MeeGo SDK repository on a system running MeeGo, run the following command. 
Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".
<pre>$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
</ul>
=== On openSUSE ===
<ul>
<li>To add the MeeGo repository, run the following command. 
Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".
<pre>$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
</ul>

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

<ol>
<li>Create a MeeGo target using MADDE 
Run the command below. Replace <target> with one of
* '''meego-core-armv7l-1.1.2''': Build applications for ARM handheld devices (such as N900)
* '''meego-handset-ia32-1.1.2''': Build applications for x86 handheld devices (such as Aava)
* '''meego-netbook-ia32-1.1.2''': Build applications for x86 netbooks.
Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.
<pre>$ sudo mad-admin create -f <target> </pre>
If you encounter problems, check the [http://wiki.meego.com/MeeGo_SDK_Troubleshooting#General_SDK_Errors Troubleshooting page]
</li>
<li>To check that the target has been installed correctly, run the following. 
Replace <target> with one of the values described in the previous step
<pre>$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make
</pre>
Note: Running qmake will print "-unix is deprecated" This is not an error with the compilation. You can safely ignore this for now.
</li>
<li>To check that the qt-simple application is created for the correct target, run:
<pre>$ file build/qthello</pre>
</li>
</ol>

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

$ /opt/meego/meego-sdk-qt/bin/qmake

Note: On Ubuntu 10.10, you may need to install g++ in order for this step to work. If necessary, do this:

$ sudo apt-get install g++

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]
* [[SDK/Docs/1.1/在Linux平台开发进行MeeGo_SDK开发|在Linux平台进行MeeGo_SDK开发 - 简体中文]]

SDK/Packages group

2011-01-13T05:30:49Z

Fabo: /* Proposals */

Author: Fathi Boudra

== Introduction ==

Currently all ks files for the SDK have a huge number of packages listed, the list of packages for the SDK should be included in package groups instead.
We need to create package groups and request inclusion into the patterns rather than maintaining them in the ks files.

See http://bugs.meego.com/show_bug.cgi?id=11607

== Proposals ==

We have 2 options:
* dump current list of development packages into a packages group
* install all development package from MeeGo Core

We can have several packages group:
* based on MeeGo Core
* based on MeeGo Core and Handset
* ...

=== Current development packages list ===

The numbers are based on trunk-daily-1.1.80.14.20110107.1 images.

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
| '''Devel. packages'''
| '''Packages list'''
|-
| Core
| armv7l
| 353M
| 71
| http://wiki.meego.comimages/Meego-core-armv7l-madde-sysroot.list
|-
| Core
| ia32
| 383M
| 76
| http://wiki.meego.comimages/Meego-core-ia32-madde-sysroot.list
|-
| Handset
| armv7l
| 353M
| 71
| http://wiki.meego.comimages/Meego-handset-armv7l-madde-sysroot.list
|-
| Handset
| ia32
| 387M
| 81
| http://wiki.meego.com/images/Meego-handset-ia32-madde-sysroot.list
|}

=== Complete development packages list ===

{| cellpadding="5" cellspacing="0" border="1"
|- align="center"
| '''Vertical'''
| '''Architecture'''
| '''Size'''
|-
| Core
| armv7l
| ?
|-
| Core
| ia32
| ?
|-
| Handset
| armv7l
| ?
|-
| Handset
| ia32
| ?
|}

SDK/Packages group

2011-01-12T19:22:20Z

SDK/Tutorials/Add a new target

2011-01-12T16:39:59Z

Fabo: /* Pre-requisites */

== Overview ==

Problem statement:
* MeeGo SDK uses MADDE to manage multiple targets and developers are easy to switch between them. Basically a target includes 3 components: sysroot, runtime(qemu image) and toolchain. The toolchain is rarely changed during the development of a major MeeGo release like 1.1 or 1.2. For sysroot and runtime, they change daily since MeeGo release team creates daily build for different MeeGo profiles like Handset, Netbook, IVI and so on.
* By default, the installation of MeeGo SDK will include several targets which are created together with the major MeeGo release. But if developers want to keep tracking the latest MeeGo status, they have to manually add latest target like daily sysroot/runtime into MeeGo SDK. Adding a new target is not straightforward and not easy for developer to do.

This wiki page introduces a tool to easily add new targets into MeeGo SDK on the Linux operating system.

== Pre-requisites ==

* Install [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux | MeeGo SDK for Linux]]
* Download the [http://download3.meego.com/meego-sdk-update-target meego-sdk-update-target] tool

== Usage and examples ==
* Get help
$ ./meego-sdk-update-target

* There are some options set with default value if they are not specified on command line. You can change them for your convenience.
* The tool only supports Handset and Netbook as targets at this stage.
* The tool is a shell script and free to change for your convenience.

* To update with a new Handset MeeGo trunk build 1.1.80.13.20110104.1 from http://repo.meego.com/MeeGo/builds/trunk/
$ sudo meego-sdk-update-target -u 1.1.80.13.20110104.1 -url http://repo.meego.com/MeeGo/builds/trunk

* To update with a new Netbook MeeGo trunk-daily build trunk-daily-1.1.80.12.20101223.1 from http://download.meego.com/trunk-daily/builds/1.1.80
$ sudo meego-sdk-update-target -d netbook -u trunk-daily-1.1.80.12.20101223.1 -url http://download.meego.com/trunk-daily/builds/1.1.80

* To update with a new Handset MeeGo testing-daily build testing-daily-1.1.80.13.20110104.1 from http://download.meego.com/testing-daily/builds/1.1.80
$ sudo meego-sdk-update-target -d handset -u testing-daily-1.1.80.13.20110104.1 -url http://download.meego.com/testing-daily/builds/1.1.80

* To update with a new Handset MeeGo target with specific sysroot and runtime tarball files, you need to provide a name of the target with "-u" option
$ sudo meego-sdk-update-target -u my-target -sysroot url_to_sysroot_tar.gz -runtime url_to_runtime_tar.bz2

* You can use the following commands to update the targets to MeeGo SDK 1.1.2
$ sudo ./meego-sdk-update-target -u 1.1.2 -sysroot http://download3.meego.com/meego-core-armv7l-madde-sysroot-1.1.2-fs.tar.bz2

$ sudo ./meego-sdk-update-target -u 1.1.2 -sysroot http://download3.meego.com/meego-handset-ia32-madde-sysroot-1.1.20110106.1204-fs.tar.gz -runtime http://download3.meego.com/meego-handset-ia32-qemu-1.1.20110110.1026-raw.tar.bz2

$ sudo ./meego-sdk-update-target -u 1.1.2 -d netbook -sysroot http://download3.meego.com/meego-core-ia32-madde-sysroot-1.1.20110106.1139-fs.tar.gz -runtime http://download3.meego.com/meego-netbook-ia32-qemu-1.1.20110110.1049-raw.tar.bz2

== Create your own target (sysroot and runtime) ==

* The sysroot has to be a tar.gz or tar.bz2 and can be generated by adding following command parameters to mic2
$ sudo mic-image-creator --format=fs --package=tar.gz ...

* The runtime has to be a tar.gz or tar.bz2 and can be generated by adding following command parameters to mic2
$ sudo mic-image-creator --format=raw --package=tar.bz2 --release=release_no --compress-disk-image=none ...

* Please check help of mic-image-creator for detailed explanation of those options
$ sudo mic-image-creator --help

* You can find the ks file to create MeeGo sysroot and runtime at http://meego.gitorious.org/meego-os-base/image-configurations/trees/master/.

== Other Notes ==

* The script will add a new target, which need several GB disk space (>5GB). Please make sure you have enough disk space.
* It's better to remove some old target which is not useful. To get the target name and the runtime name, you could run:
$ sudo mad-admin list

and then run following commands to remove it:
$ sudo mad-admin remove '''<target name>'''
$ sudo mad-admin remove '''<runtime name>'''

But using above 2 commands will not totally remove the cached and already generated files for the target. To remove all of them to save disk space, you need to remove the related folder and files:

$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/targets/'''<target name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/runtimes/'''<runtime name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/sysroots/'''<sysroot name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/tools/'''<runtime name>'''
$ sudo rm -f /usr/lib/madde/linux-'''<host arch>'''/cache/'''<tarball name>'''

Note: replace '''<host arch>''' with one of the following values "i686" or "x86_64".

[[Category:Tutorial]]

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

2011-01-12T16:37:54Z

Fabo: /* Using the MeeGo SDK Qt version */

SDK/Tutorials/Add a new target

2011-01-12T16:36:34Z

Fabo:

== Overview ==

Problem statement:
* MeeGo SDK uses MADDE to manage multiple targets and developers are easy to switch between them. Basically a target includes 3 components: sysroot, runtime(qemu image) and toolchain. The toolchain is rarely changed during the development of a major MeeGo release like 1.1 or 1.2. For sysroot and runtime, they change daily since MeeGo release team creates daily build for different MeeGo profiles like Handset, Netbook, IVI and so on.
* By default, the installation of MeeGo SDK will include several targets which are created together with the major MeeGo release. But if developers want to keep tracking the latest MeeGo status, they have to manually add latest target like daily sysroot/runtime into MeeGo SDK. Adding a new target is not straightforward and not easy for developer to do.

This wiki page introduces a tool to easily add new targets into MeeGo SDK on the Linux operating system.

== Pre-requisites ==

* Install MeeGo Linux SDK. http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux.
* Download the meego-sdk-update-target from http://download3.meego.com/meego-sdk-update-target

== Usage and examples ==
* Get help
$ ./meego-sdk-update-target

* There are some options set with default value if they are not specified on command line. You can change them for your convenience.
* The tool only supports Handset and Netbook as targets at this stage.
* The tool is a shell script and free to change for your convenience.

* To update with a new Handset MeeGo trunk build 1.1.80.13.20110104.1 from http://repo.meego.com/MeeGo/builds/trunk/
$ sudo meego-sdk-update-target -u 1.1.80.13.20110104.1 -url http://repo.meego.com/MeeGo/builds/trunk

* To update with a new Netbook MeeGo trunk-daily build trunk-daily-1.1.80.12.20101223.1 from http://download.meego.com/trunk-daily/builds/1.1.80
$ sudo meego-sdk-update-target -d netbook -u trunk-daily-1.1.80.12.20101223.1 -url http://download.meego.com/trunk-daily/builds/1.1.80

* To update with a new Handset MeeGo testing-daily build testing-daily-1.1.80.13.20110104.1 from http://download.meego.com/testing-daily/builds/1.1.80
$ sudo meego-sdk-update-target -d handset -u testing-daily-1.1.80.13.20110104.1 -url http://download.meego.com/testing-daily/builds/1.1.80

* To update with a new Handset MeeGo target with specific sysroot and runtime tarball files, you need to provide a name of the target with "-u" option
$ sudo meego-sdk-update-target -u my-target -sysroot url_to_sysroot_tar.gz -runtime url_to_runtime_tar.bz2

* You can use the following commands to update the targets to MeeGo SDK 1.1.2
$ sudo ./meego-sdk-update-target -u 1.1.2 -sysroot http://download3.meego.com/meego-core-armv7l-madde-sysroot-1.1.2-fs.tar.bz2

$ sudo ./meego-sdk-update-target -u 1.1.2 -sysroot http://download3.meego.com/meego-handset-ia32-madde-sysroot-1.1.20110106.1204-fs.tar.gz -runtime http://download3.meego.com/meego-handset-ia32-qemu-1.1.20110110.1026-raw.tar.bz2

$ sudo ./meego-sdk-update-target -u 1.1.2 -d netbook -sysroot http://download3.meego.com/meego-core-ia32-madde-sysroot-1.1.20110106.1139-fs.tar.gz -runtime http://download3.meego.com/meego-netbook-ia32-qemu-1.1.20110110.1049-raw.tar.bz2

== Create your own target (sysroot and runtime) ==

* The sysroot has to be a tar.gz or tar.bz2 and can be generated by adding following command parameters to mic2
$ sudo mic-image-creator --format=fs --package=tar.gz ...

* The runtime has to be a tar.gz or tar.bz2 and can be generated by adding following command parameters to mic2
$ sudo mic-image-creator --format=raw --package=tar.bz2 --release=release_no --compress-disk-image=none ...

* Please check help of mic-image-creator for detailed explanation of those options
$ sudo mic-image-creator --help

* You can find the ks file to create MeeGo sysroot and runtime at http://meego.gitorious.org/meego-os-base/image-configurations/trees/master/.

== Other Notes ==

* The script will add a new target, which need several GB disk space (>5GB). Please make sure you have enough disk space.
* It's better to remove some old target which is not useful. To get the target name and the runtime name, you could run:
$ sudo mad-admin list

and then run following commands to remove it:
$ sudo mad-admin remove '''<target name>'''
$ sudo mad-admin remove '''<runtime name>'''

But using above 2 commands will not totally remove the cached and already generated files for the target. To remove all of them to save disk space, you need to remove the related folder and files:

$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/targets/'''<target name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/runtimes/'''<runtime name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/sysroots/'''<sysroot name>'''
$ sudo rm -rf /usr/lib/madde/linux-'''<host arch>'''/tools/'''<runtime name>'''
$ sudo rm -f /usr/lib/madde/linux-'''<host arch>'''/cache/'''<tarball name>'''

Note: replace '''<host arch>''' with one of the following values "i686" or "x86_64".

[[Category:Tutorial]]

SDK/Docs/1.1/Configuring QEMU runtimes

2011-01-12T14:02:21Z

Fabo: /* Install a MeeGo Runtime */

[[category:Meego-1.1]]

[http://wiki.qemu.org/ QEMU] is a component of the MeeGo SDK. It can run handset or netbook images under an emulator, so you can test your applications on a MeeGo operating system, even if you don't have a MeeGo device.

If you haven't already installed the SDK, see:

* [[SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux|Installing the SDK on Linux]] or [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|Installing the SDK on Windows]]

For QEMU, it is important to check your graphics capability. See [[SDK/Docs/1.1/MeeGo SDK Graphics Acceleration|this page about graphics acceleration]] for details. '''Please read this page carefully and follow the instructions on it if you are having issues starting runtimes under QEMU.'''

It is also possible to build and install QEMU manually: see the [[SDK/Docs/1.1/Building_QEMU_Tools|QEMU tools page]] for details.

The best and simplest way to use a MeeGo OS image with QEMU is to use <code>mad-admin</code> to download a runtime, and <code>mad</code> to run it. See the instructions below for how to do this.

== Install a MeeGo Runtime ==

You can get a list of available runtimes for your version of MADDE with:

$ mad-admin list runtimes
meego-handset-ia32-qemu-1.1.2-runtime (installable)
meego-netbook-ia32-qemu-1.1.2-runtime (installable)

Run the command below. Replace '''<runtime name>''' with one of
* '''meego-handset-ia32-qemu-1.1.2-runtime''': Run the MeeGo OS with handset UI.
* '''meego-netbook-ia32-qemu-1.1.2-runtime''': Run the MeeGo OS with netbook UI.

$ sudo mad-admin create -f -e '''<runtime name>'''

This will download the runtime (a ~650+ MB .bz2 file) into MADDE's <code>cache</code> directory and decompress it in the <code>runtimes</code> directory.. If network/proxy issues prevent the image from downloading, the url for the runtime can be extracted from the MADDE's <code>cache/madde.conf.d/<runtime>.conf</code> file, downloaded manually, and copied into the <code>cache</code> directory. Re-running the above command will now bypass the download and directly decompress the runtime.

After installing, you can check that the runtime is installed by running <code>mad-admin list</code> again.

$ mad-admin list runtimes
meego-handset-ia32-qemu-1.1.2-runtime (installed)
meego-netbook-ia32-qemu-1.1.2-runtime (installable)

Note that '''installed''' above indicates that the handset runtime was successfully downloaded and configured for QEMU.

== Using a runtime ==

To start an installed runtime, use the <code>mad</code> command to boot the image inside QEMU.

To start the IA32 handset runtime:
$ sudo mad remote -r '''<handset runtime name>''' poweron

Here's what the handset image looks like (this is the ''Applications'' zone):

[[File:Sdk-docs-ia32-handset-under-qemu.png|600px]]

To start the IA32 netbook runtime:
$ sudo mad remote -r '''<netbook runtime name>''' poweron

Here's what the netbook image looks like (this is ''Myzone''):

[[File:Sdk-docs-ia32-netbook-under-qemu.png|600px]]

You can now use this running image as a deployment target for Qt Creator, or log into it manually over SSH (see below).

When you've finished, use the power off icon in the emulator to switch it off (if available); or from the command line, do:
$ sudo mad remote -r '''<netbook runtime name>''' poweroff

=== Using a runtime without graphics ===

If you are having issues with running QEMU, you can try running the image without graphics to help isolate the problem. To do this, set <code>QEMU_NOGRAPHIC=yes</code> in the environment before running the emulator. For example:

$ QEMU_NOGRAPHIC=yes mad remote -r '''<handset runtime name>''' poweron

If you are then able to ssh into the running image, you can be fairly certain that your issues are graphics-related, rather than anything to do with the image itself.

=== Shortcut button in the MeeGo SDK for Windows ===

If you are using the MeeGo SDK for Windows, Qt Creator provides a shortcut button to start a QEMU runtime associated with a project, in the bottom left corner:

[[File:Meego-sdk-qtcreator-start-emulator-button.png]]

Clicking on this has the same effect as starting the QEMU runtime manually (as described above).

Once the emulator is running, the button shows a red square: when it is in this state, clicking on it again stops the emulator.

== SSH into QEMU Image ==

Any time MeeGo is running in QEMU, you can use SSH to connect to the image from a command-line terminal on the host system.

When MADDE starts QEMU, it sets up a redirect from port 6666 on the host to the SSH port (port 22) on the guest (MeeGo on QEMU). So you can log into the running QEMU image with:

$ ssh meego@127.0.0.1 -p 6666

Two user accounts are available:

# User: '''meego''', password: '''meego'''
# User: '''root''', password: '''meego'''

== Configuring access to an emulated device in Qt Creator ==

[[File:sdk-docs-QtCreator-configuring-emulator-access.png|thumb|500px]]
To configure access to an emulated device:
# Open '''Tools''' > '''Options''' > '''Projects''' > '''MeeGo Device Configurations'''.
# In the dialog box, create a new Device Configuration by clicking on '''Add'''.
# Give the new Device Configuration a name in the Configuration Name text field, and add the following settings in the other test fields:
#* Device type: choose MeeGo emulator
#* Authentication type: Password
#* Host name: 127.0.0.1
#* Ports, SSH: 6666
#*: Note that the emulator is setup with a redirect from port 6666 on localhost to the SSH port (22) of the emulated device.
#* Ports, Gdb Server: 13219 (the default)
#: '''Note:''' If this port is not free, you can select another one.
#* Connection Timeout: 30
#* User Name: root
#* Password: meego
# Click '''Apply'''.
# To test the settings, ensure that the emulated device is running, then click '''Test'''.
#: If successful, you'll see a dialog box with the message "Device configuration successful".
#: If the message "Could not connect to host" is displayed, check your setting selections and make sure that the network is connected.
# Click '''Close''' and '''OK'''.

SDK/Docs/1.1/Configuring QEMU runtimes

2011-01-12T12:30:36Z

Fabo:

[[category:Meego-1.1]]

[http://wiki.qemu.org/ QEMU] is a component of the MeeGo SDK. It can run handset or netbook images under an emulator, so you can test your applications on a MeeGo operating system, even if you don't have a MeeGo device.

If you haven't already installed the SDK, see:

* [[SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux|Installing the SDK on Linux]] or [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows|Installing the SDK on Windows]]

For QEMU, it is important to check your graphics capability. See [[SDK/Docs/1.1/MeeGo SDK Graphics Acceleration|this page about graphics acceleration]] for details. '''Please read this page carefully and follow the instructions on it if you are having issues starting runtimes under QEMU.'''

It is also possible to build and install QEMU manually: see the [[SDK/Docs/1.1/Building_QEMU_Tools|QEMU tools page]] for details.

The best and simplest way to use a MeeGo OS image with QEMU is to use <code>mad-admin</code> to download a runtime, and <code>mad</code> to run it. See the instructions below for how to do this.

== Install a MeeGo Runtime ==

You can get a list of available runtimes for your version of MADDE with:

$ mad-admin list runtimes
meego-handset-ia32-qemu-1.1.2-runtime (installable)
meego-netbook-ia32-qemu-1.1.2-runtime (installable)

Run the command below. Replace '''<runtime name>''' with one of
* '''meego-handset-ia32-qemu-1.1.2-runtime''': Run the MeeGo OS with handset UI.
* '''meego-netbook-ia32-qemu-1.1.2-runtime''': Run the MeeGo OS with netbook UI.

$ sudo mad-admin create -f -e '''<runtime name>'''

This will download the runtime (a ~650+ MB .bz2 file) into MADDE's <code>cache</code> directory and decompress it in the <code>runtimes</code> directory.. If network/proxy issues prevent the image from downloading, the url for the runtime can be extracted from the MADDE's <code>cache/madde.conf.d/<runtime>.conf</code> file, downloaded manually, and copied into the <code>cache</code> directory. Re-running the above command will now bypass the download and directly decompress the runtime.

After installing, you can check that the runtime is installed by running <code>mad-admin list</code> again.

$ mad-admin list runtimes
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime (installed)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime (installable)

Note that '''installed''' above indicates that the handset runtime was successfully downloaded and configured for QEMU.

== Using a runtime ==

To start an installed runtime, use the <code>mad</code> command to boot the image inside QEMU.

To start the IA32 handset runtime:
$ sudo mad remote -r '''<handset runtime name>''' poweron

Here's what the handset image looks like (this is the ''Applications'' zone):

[[File:Sdk-docs-ia32-handset-under-qemu.png|600px]]

To start the IA32 netbook runtime:
$ sudo mad remote -r '''<netbook runtime name>''' poweron

Here's what the netbook image looks like (this is ''Myzone''):

[[File:Sdk-docs-ia32-netbook-under-qemu.png|600px]]

You can now use this running image as a deployment target for Qt Creator, or log into it manually over SSH (see below).

When you've finished, use the power off icon in the emulator to switch it off (if available); or from the command line, do:
$ sudo mad remote -r '''<netbook runtime name>''' poweroff

=== Using a runtime without graphics ===

If you are having issues with running QEMU, you can try running the image without graphics to help isolate the problem. To do this, set <code>QEMU_NOGRAPHIC=yes</code> in the environment before running the emulator. For example:

$ QEMU_NOGRAPHIC=yes mad remote -r '''<handset runtime name>''' poweron

If you are then able to ssh into the running image, you can be fairly certain that your issues are graphics-related, rather than anything to do with the image itself.

=== Shortcut button in the MeeGo SDK for Windows ===

If you are using the MeeGo SDK for Windows, Qt Creator provides a shortcut button to start a QEMU runtime associated with a project, in the bottom left corner:

[[File:Meego-sdk-qtcreator-start-emulator-button.png]]

Clicking on this has the same effect as starting the QEMU runtime manually (as described above).

Once the emulator is running, the button shows a red square: when it is in this state, clicking on it again stops the emulator.

== SSH into QEMU Image ==

Any time MeeGo is running in QEMU, you can use SSH to connect to the image from a command-line terminal on the host system.

When MADDE starts QEMU, it sets up a redirect from port 6666 on the host to the SSH port (port 22) on the guest (MeeGo on QEMU). So you can log into the running QEMU image with:

$ ssh meego@127.0.0.1 -p 6666

Two user accounts are available:

# User: '''meego''', password: '''meego'''
# User: '''root''', password: '''meego'''

== Configuring access to an emulated device in Qt Creator ==

[[File:sdk-docs-QtCreator-configuring-emulator-access.png|thumb|500px]]
To configure access to an emulated device:
# Open '''Tools''' > '''Options''' > '''Projects''' > '''MeeGo Device Configurations'''.
# In the dialog box, create a new Device Configuration by clicking on '''Add'''.
# Give the new Device Configuration a name in the Configuration Name text field, and add the following settings in the other test fields:
#* Device type: choose MeeGo emulator
#* Authentication type: Password
#* Host name: 127.0.0.1
#* Ports, SSH: 6666
#*: Note that the emulator is setup with a redirect from port 6666 on localhost to the SSH port (22) of the emulated device.
#* Ports, Gdb Server: 13219 (the default)
#: '''Note:''' If this port is not free, you can select another one.
#* Connection Timeout: 30
#* User Name: root
#* Password: meego
# Click '''Apply'''.
# To test the settings, ensure that the emulated device is running, then click '''Test'''.
#: If successful, you'll see a dialog box with the message "Device configuration successful".
#: If the message "Could not connect to host" is displayed, check your setting selections and make sure that the network is connected.
# Click '''Close''' and '''OK'''.