MeeGo wiki - User contributions [en]

SDK/Toolchains/Meetings/Notes20110408

2011-04-11T14:14:17Z

Kaltsi: /* General News */

=== Date and Time ===
Friday 2011-04-08 @07.00 - 08.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Martti Lumme

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* gcc 4.6.0 has been released
** consider using gcc 4.6.1 for MeeGo 1.3 if it is released in time (June/Jul timeframe)

* Updated versions of cloog, gmp, mpfr in devel:toolchain and enabled cloog also for arm and cross toolchains.

=== Status ===
==== Intel ====
* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** Austin's team will try to figure out the necessary minimal patch for binutils to fix a bug in Fedora 14 builds.

==== ARM ====
*
=== Decisions ===
* Enable armv8el for devel:toolchain too

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation DONE. (diff is over 10 MB)
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

SDK/Toolchains/Meetings/Notes20110408

2011-04-11T14:13:37Z

Kaltsi: /* General News */

=== Date and Time ===
Friday 2011-04-08 @07.00 - 08.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Martti Lumme

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* Updated versions of cloog, gmp, mpfr in devel:toolchain and enabled cloog also for arm and cross toolchains.

=== Status ===
==== Intel ====
* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** Austin's team will try to figure out the necessary minimal patch for binutils to fix a bug in Fedora 14 builds.

==== ARM ====
*
=== Decisions ===
* Enable armv8el for devel:toolchain too

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation DONE. (diff is over 10 MB)
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

SDK/Toolchains/Meetings/Notes20110408

2011-04-11T13:53:58Z

Kaltsi: /* Date and Time */

=== Date and Time ===
Friday 2011-04-08 @07.00 - 08.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Martti Lumme

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* None

=== Status ===
==== Intel ====
* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** Austin's team will try to figure out the necessary minimal patch for binutils to fix a bug in Fedora 14 builds.

==== ARM ====
*
=== Decisions ===
* Enable armv8el for devel:toolchain too

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation DONE. (diff is over 10 MB)
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

SDK/Toolchains/Meetings/Notes20110408

2011-04-11T13:53:42Z

Kaltsi: Created page with "=== Date and Time === Friday 2011-03-25 @08.00 - 09.00 UTC === Participants === Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Martti Lumme === Agenda === * General n..."

=== Date and Time ===
Friday 2011-03-25 @08.00 - 09.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Martti Lumme

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* None

=== Status ===
==== Intel ====
* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** Austin's team will try to figure out the necessary minimal patch for binutils to fix a bug in Fedora 14 builds.

==== ARM ====
*
=== Decisions ===
* Enable armv8el for devel:toolchain too

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation DONE. (diff is over 10 MB)
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

SDK/Toolchains/ToolchainChange

2011-04-11T10:07:23Z

Kaltsi: /* Change Content */

== Toolchain Change in MeeGo 1.2 ==

ARM Toolchain will be changed in MeeGo release 1.2. This page describes the change and the effects of the change.

=== Background ===

This change effects to ARM cross compiler part of MeeGo toolchain.

The toolchain in current MeeGo 1.1 supports ARM architecture only partially what comes to Floating Point Unit (FPU) support.

gcc compiler provides three options to support floating points in option -mfloat-abi [1]:

* soft - Full software implementation of floating points. Fits the processors without the FPU. All floating point operations are emulated by the compiler
* softfp - FPU unit is in use but the code is compatible to full software code. Floating Point operations are passed to the FPU in integer registers
* hard - Floating Point arguments are passed directly to the FPU registers. No compatibility to soft and softfp.

Full utilization of the FPU gives performance improvement to applications using plenty of floating point operations - like games, location based services and graphics.

In order to take -mfloat-abi=hard option into use in MeeGo 1.2 the toolchain is needed to be updated to gcc-4.5.1 based.

The change proposal ([[SDK/Toolchains/ToolchainChangeProposal]]) was approved in MeeGo TSG on December 1, 2010.

=== Change Content ===

In MeeGo Release 1.2 and onwards the following is about to change:

* The toolchain is based on gcc-4.5.1 with binutils-2.20 (or newer) and glibc-2.10 (or newer)
* '''gcc option -mfloat-abi=hard is the default and mandatory'''
* There are three build configurations in the toolchain - Baseline and two Optimized configurations:
* Baseline configuration maximizes compatibility between various ARMv7-A based chipsets
* Optimized configuration allows optimization for NEON and Thumb2 instructions in the devices where these can be used
* Applications should always target Baseline configuration. The applications that benefit from Optimized configurations can additionally provide optimized binaries. Offering an application without the Baseline configuration should not be done, unless the Baseline configuration binary is unusable for this particular application for a valid reason.
* Baseline configuration (NEON and Thumb2 is not allowed):
* RPM architecture name: "armv7hl"
* ARMv7 architecture (-march=armv7-a)
* VFPv3-D16 is in use (-mfpu=vfpv3-d16)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 1 (NEON is allowed) - Default Optimized configuration for MeeGo Release 1.2:
* RPM architecture name: "armv7nhl"
* ARMv7 architecture (-march=armv7-a)
* NEON allowed (-mfpu=neon)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 2 (Both NEON and Thumb2 are allowed)
* RPM arhcitecture name: "armv7tnhl"
* ARMv7 architecture (-march=armv7-a)
* NEON is used (-mfpu=neon)
* Thumb2 instruction set is used (-mthumb)
* Optimized configuration 1 is the default Optimized configuration for MeeGo Release 1.2. When newer ARM hardware becomes available it is likely that Optimized configuration 2 becomes as the default optimized configuration, but this happens earliest in MeeGo Release 1.3.

* ARM RunFast is enabled in glibc by default
* Scheduler name in build.meego.com is "armv8el"

=== Impact of the Change ===

'''ARM Packages compiled in MeeGo Release 1.2 are not binary compatible with packages that are compiled using gcc-option -mfloat-abi=softfp in MeeGo Release 1.0 or 1.1. So all the packages from Release 1.0 or 1.1 must be re-compiled using the toolchain of MeeGo 1.2.'''

=== Bugzilla ===
All hardfp related issues are tracked in the metabug #11429 [3].

=== References ===
[1] http://wiki.debian.org/ArmHardFloatPort/VfpComparison#DetailsonGCCfloating-pointoptions

[2] http://lists.meego.com/pipermail/meego-dev/2011-January/481145.html

[3] http://bugs.meego.com/showdependencytree.cgi?id=11429&hide_resolved=0

SDK/Toolchains/ToolchainChange

2011-04-11T10:04:43Z

Kaltsi: /* Impact of the Change */

SDK/Toolchains/ToolchainChange

2011-04-11T10:04:14Z

Kaltsi: /* Change Content */

== Toolchain Change in MeeGo 1.2 ==

ARM Toolchain will be changed in MeeGo release 1.2. This page describes the change and the effects of the change.

=== Background ===

This change effects to ARM cross compiler part of MeeGo toolchain.

The toolchain in current MeeGo 1.1 supports ARM architecture only partially what comes to Floating Point Unit (FPU) support.

gcc compiler provides three options to support floating points in option -mfloat-abi [1]:

* soft - Full software implementation of floating points. Fits the processors without the FPU. All floating point operations are emulated by the compiler
* softfp - FPU unit is in use but the code is compatible to full software code. Floating Point operations are passed to the FPU in integer registers
* hard - Floating Point arguments are passed directly to the FPU registers. No compatibility to soft and softfp.

Full utilization of the FPU gives performance improvement to applications using plenty of floating point operations - like games, location based services and graphics.

In order to take -mfloat-abi=hard option into use in MeeGo 1.2 the toolchain is needed to be updated to gcc-4.5.1 based.

The change proposal ([[SDK/Toolchains/ToolchainChangeProposal]]) was approved in MeeGo TSG on December 1, 2010.

=== Change Content ===

In MeeGo Release 1.2 and onwards the following is about to change:

* The toolchain is based on gcc-4.5.1 with binutils-2.20 (or newer) and glibc-2.10 (or newer)
* '''gcc option -mfloat-abi=hard is the default and mandatory'''
* There are three build configurations in the toolchain - Baseline and two Optimized configurations:
* Baseline configuration maximizes compatibility between various ARMv7-A based chipsets
* Optimized configuration allows optimization for NEON and Thumb2 instructions in the devices where these can be used
* Applications should always target Baseline configuration. The applications that benefit from Optimized configurations can additionally provide optimized binaries. Offering an application without the Baseline configuration should not be done, unless the Baseline configuration binary is unusable for this particular application for a valid reason.
* Baseline configuration (NEON and Thumb2 is not allowed):
* RPM architecture name: "armv7hl"
* ARMv7 architecture (-march=armv7-a)
* VFPv3-D16 is in use (-mfpu=vfpv3-d16)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 1 (NEON is allowed) - Default Optimized configuration for MeeGo Release 1.2:
* RPM architecture name: "armv7nhl"
* ARMv7 architecture (-march=armv7-a)
* NEON allowed (-mfpu=neon)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 2 (Both NEON and Thumb2 are allowed)
* RPM arhcitecture name: "armv7tnhl"
* ARMv7 architecture (-march=armv7-a)
* NEON is used (-mfpu=neon)
* Thumb2 instruction set is used (-mthumb)
* Optimized configuration 1 is the default Optimized configuration for MeeGo Release 1.2. When newer ARM hardware becomes available it is likely that Optimized configuration 2 becomes as the default optimized configuration, but this happens earliest in MeeGo Release 1.3.

* ARM RunFast is enabled in glibc by default
* Scheduler name in build.meego.com is "armv8el"

=== Impact of the Change ===

'''ARM Packages compiled in MeeGo Release 1.2 are not binary compatible with those packages that are compiled using gcc-option -mfloat-abi=softfp in MeeGo Release 1.0 or 1.1. So all the packages from Release 1.0 or 1.1 must be re-compiled using the toolchain of MeeGo 1.2.'''

=== Bugzilla ===
All hardfp related issues are tracked in the metabug #11429 [3].

=== References ===
[1] http://wiki.debian.org/ArmHardFloatPort/VfpComparison#DetailsonGCCfloating-pointoptions

[2] http://lists.meego.com/pipermail/meego-dev/2011-January/481145.html

[3] http://bugs.meego.com/showdependencytree.cgi?id=11429&hide_resolved=0

SDK/Toolchains/ToolchainChange

2011-04-11T10:02:57Z

Kaltsi: /* Change Content */

== Toolchain Change in MeeGo 1.2 ==

ARM Toolchain will be changed in MeeGo release 1.2. This page describes the change and the effects of the change.

=== Background ===

This change effects to ARM cross compiler part of MeeGo toolchain.

The toolchain in current MeeGo 1.1 supports ARM architecture only partially what comes to Floating Point Unit (FPU) support.

gcc compiler provides three options to support floating points in option -mfloat-abi [1]:

* soft - Full software implementation of floating points. Fits the processors without the FPU. All floating point operations are emulated by the compiler
* softfp - FPU unit is in use but the code is compatible to full software code. Floating Point operations are passed to the FPU in integer registers
* hard - Floating Point arguments are passed directly to the FPU registers. No compatibility to soft and softfp.

Full utilization of the FPU gives performance improvement to applications using plenty of floating point operations - like games, location based services and graphics.

In order to take -mfloat-abi=hard option into use in MeeGo 1.2 the toolchain is needed to be updated to gcc-4.5.1 based.

The change proposal ([[SDK/Toolchains/ToolchainChangeProposal]]) was approved in MeeGo TSG on December 1, 2010.

=== Change Content ===

In MeeGo Release 1.2 and onwards the following is about to change:

* The toolchain is based on gcc-4.5.1 with binutils-2.20 (or newer) and glibc-2.10 (or newer)
* '''gcc option -mfloat-abi=hard is the default and mandatory'''
* There are three build configurations in the toolchain - Baseline and two Optimized configurations:
* Baseline configuration maximizes compatibility between various ARMv7-A based chipsets
* Optimized configuration allows optimization for NEON and Thumb2 instructions in the devices where these can be used
* Applications should always target Baseline configuration. The applications benefit from Optimized configurations can additionally provide optmized binaries. Offering an application without Baseline configuration should not be done, unless the Baseline configuration binary is unusable for this particular application for a valid reason.
* Baseline configuration (NEON and Thumb2 is not allowed):
* RPM architecture name: "armv7hl"
* ARMv7 architecture (-march=armv7-a)
* VFPv3-D16 is in use (-mfpu=vfpv3-d16)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 1 (NEON is allowed) - Default Optimized configuration for MeeGo Release 1.2:
* RPM architecture name: "armv7nhl"
* ARMv7 architecture (-march=armv7-a)
* NEON allowed (-mfpu=neon)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 2 (Both NEON and Thumb2 are allowed)
* RPM arhcitecture name: "armv7tnhl"
* ARMv7 architecture (-march=armv7-a)
* NEON is used (-mfpu=neon)
* Thumb2 instruction set is used (-mthumb)
* Optimized configuration 1 is the default Optimized configuration for MeeGo Release 1.2. When newer ARM hardware becomes available it is likely that Optimized configuration 2 becomes as the default optimized configuration, but this happens earliest in MeeGo Release 1.3.

* ARM RunFast is enabled in glibc by default
* Scheduler name in build.meego.com is "armv8el"

=== Impact of the Change ===

'''ARM Packages compiled in MeeGo Release 1.2 are not binary compatible with those packages that are compiled using gcc-option -mfloat-abi=softfp in MeeGo Release 1.0 or 1.1. So all the packages from Release 1.0 or 1.1 must be re-compiled using the toolchain of MeeGo 1.2.'''

=== Bugzilla ===
All hardfp related issues are tracked in the metabug #11429 [3].

=== References ===
[1] http://wiki.debian.org/ArmHardFloatPort/VfpComparison#DetailsonGCCfloating-pointoptions

[2] http://lists.meego.com/pipermail/meego-dev/2011-January/481145.html

[3] http://bugs.meego.com/showdependencytree.cgi?id=11429&hide_resolved=0

SDK/Toolchains/ToolchainChange

2011-04-11T10:00:46Z

Kaltsi: /* Change Content */

== Toolchain Change in MeeGo 1.2 ==

ARM Toolchain will be changed in MeeGo release 1.2. This page describes the change and the effects of the change.

=== Background ===

This change effects to ARM cross compiler part of MeeGo toolchain.

The toolchain in current MeeGo 1.1 supports ARM architecture only partially what comes to Floating Point Unit (FPU) support.

gcc compiler provides three options to support floating points in option -mfloat-abi [1]:

* soft - Full software implementation of floating points. Fits the processors without the FPU. All floating point operations are emulated by the compiler
* softfp - FPU unit is in use but the code is compatible to full software code. Floating Point operations are passed to the FPU in integer registers
* hard - Floating Point arguments are passed directly to the FPU registers. No compatibility to soft and softfp.

Full utilization of the FPU gives performance improvement to applications using plenty of floating point operations - like games, location based services and graphics.

In order to take -mfloat-abi=hard option into use in MeeGo 1.2 the toolchain is needed to be updated to gcc-4.5.1 based.

The change proposal ([[SDK/Toolchains/ToolchainChangeProposal]]) was approved in MeeGo TSG on December 1, 2010.

=== Change Content ===

In MeeGo Release 1.2 and onwards the following is about to change:

* The toolchain is based on gcc-4.5.1 with binutils-2.20 and glibc-2.11
* '''gcc option -mfloat-abi=hard is the default and mandatory'''
* There are three build configurations in the toolchain - Baseline and two Optimized configurations:
* Baseline configuration maximizes compatibility between various ARMv7-A based chipsets
* Optimized configuration allows optimization for NEON and Thumb2 instructions in the devices where these can be used
* Applications should always target Baseline configuration. The applications benefit from Optimized configurations can additionally provide optmized binaries. Offering an application without Baseline configuration should not be done, unless the Baseline configuration binary is unusable for this particular application for a valid reason.
* Baseline configuration (NEON and Thumb2 is not allowed):
* RPM architecture name: "armv7hl"
* ARMv7 architecture (-march=armv7-a)
* VFPv3-D16 is in use (-mfpu=vfpv3-d16)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 1 (NEON is allowed) - Default Optimized configuration for MeeGo Release 1.2:
* RPM architecture name: "armv7nhl"
* ARMv7 architecture (-march=armv7-a)
* NEON allowed (-mfpu=neon)
* Thumb2 instruction set not used (-mno-thumb)
* Optimized configuration 2 (Both NEON and Thumb2 are allowed)
* RPM arhcitecture name: "armv7tnhl"
* ARMv7 architecture (-march=armv7-a)
* NEON is used (-mfpu=neon)
* Thumb2 instruction set is used (-mthumb)
* Optimized configuration 1 is the default Optimized configuration for MeeGo Release 1.2. When newer ARM hardware becomes available it is likely that Optimized configuration 2 becomes as the default optimized configuration, but this happens earliest in MeeGo Release 1.3.

* ARM RunFast is enabled in glibc by default
* Scheduler name in build.meego.com is "armv8el"

=== Impact of the Change ===

'''ARM Packages compiled in MeeGo Release 1.2 are not binary compatible with those packages that are compiled using gcc-option -mfloat-abi=softfp in MeeGo Release 1.0 or 1.1. So all the packages from Release 1.0 or 1.1 must be re-compiled using the toolchain of MeeGo 1.2.'''

=== Bugzilla ===
All hardfp related issues are tracked in the metabug #11429 [3].

=== References ===
[1] http://wiki.debian.org/ArmHardFloatPort/VfpComparison#DetailsonGCCfloating-pointoptions

[2] http://lists.meego.com/pipermail/meego-dev/2011-January/481145.html

[3] http://bugs.meego.com/showdependencytree.cgi?id=11429&hide_resolved=0

SDK/Meetings/20110406 Weekly

2011-04-06T16:00:06Z

Kaltsi: /* Toolchains (JuhaK) */

= MeeGo SDK Weekly Meeting 20110406 =

This document contains status update of 20110406.

== Conventions of this document ==

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

== Status ==

=== SDK Program (Veli) ===

* Nokia changes...

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

=== Architecture (Bob) ===

(Meetings held weekly, as needed)

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

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

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

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

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

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

=== Releasing (Fathi) ===

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

=== Windows port (Max) ===

* Preview 6 has been released
** Using 1.2 toolchains and Qt Creator 2.1
** See bugs 15003, 15004 and 14025
* AP: ARM hardfp toolchain should be provided by Al
* AP: Al to create a wiki page about the windows build server

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

* David was not present

=== Toolchains (JuhaK) ===

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

=== Documentation (Taru) ===

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

=== QA (Juha) ===

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

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

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

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

SDK/Toolchains/Meetings/Notes20110325

2011-03-25T09:07:59Z

Kaltsi: /* Participants */

=== Date and Time ===
Friday 2011-03-25 @08.00 - 09.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Junfeng Dong, Xu Zhang, Jarmo Kant

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* None

=== Status ===
==== Intel ====
* gcc 4.5.2 testing has progressed, some little regressions were found, Austin will send test results via e-mail.

==== ARM ====
* Some bugs raised by Juha for gcc-4.5 in upstream have been fixed

=== Decisions ===
* Enable armv8el for devel:toolchain too

* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** upgrade in MeeGo Trunk is too late now
** we'll need to verify it is compatible with MeeGo Trunk

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation

AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

AP: Juha - ssp related glibc ARM build problem must be solved - RESOLVED this week

SDK/Toolchains/Meetings

2011-03-25T09:07:47Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated week 08/2011)

Meeting Minutes:
* Friday, 2011-03-25: [[SDK/Toolchains/Meetings/Notes20110325]]
* Friday, 2011-03-11: [[SDK/Toolchains/Meetings/Notes20110311]]
* Friday, 2011-02-25: [[SDK/Toolchains/Meetings/Notes20110225]]
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains/Meetings/Notes20110325

2011-03-25T08:40:16Z

Kaltsi: /* Action points */

=== Date and Time ===
Friday 2011-03-25 @08.00 - 09.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Junfeng Dong, Xu Zhang

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* None

=== Status ===
==== Intel ====
* gcc 4.5.2 testing has progressed, some little regressions were found, Austin will send test results via e-mail.

==== ARM ====
* Some bugs raised by Juha for gcc-4.5 in upstream have been fixed

=== Decisions ===
* Enable armv8el for devel:toolchain too

* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** upgrade in MeeGo Trunk is too late now
** we'll need to verify it is compatible with MeeGo Trunk

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation

AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful

AP: Juha - ssp related glibc ARM build problem must be solved - RESOLVED this week

SDK/Toolchains/Meetings/Notes20110325

2011-03-25T08:39:50Z

Kaltsi: Created page with "=== Date and Time === Friday 2011-03-25 @08.00 - 09.00 UTC === Participants === Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Junfeng Dong, Xu Zhang === Agenda === *…"

=== Date and Time ===
Friday 2011-03-25 @08.00 - 09.00 UTC

=== Participants ===
Juha Kallioinen, Al Nikolov, Carsten Munk, Austin Zhang, Junfeng Dong, Xu Zhang

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* None

=== Status ===
==== Intel ====
* gcc 4.5.2 testing has progressed, some little regressions were found, Austin will send test results via e-mail.

==== ARM ====
* Some bugs raised by Juha for gcc-4.5 in upstream have been fixed

=== Decisions ===
* Enable armv8el for devel:toolchain too

* binutils upgrade for MeeGo 1.2 SDK is needed because of the Fedora 14 build problems.
** upgrade in MeeGo Trunk is too late now
** we'll need to verify it is compatible with MeeGo Trunk

=== Action points ===
AP: Al - create a diff between binutils 2.20.51.0.2 -> 2.20.51.0.7 for evaluation
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful
AP: Juha - ssp related glibc ARM build problem must be solved - RESOLVED this week

SDK/Toolchains/Meetings/Notes20110311

2011-03-14T19:56:56Z

Kaltsi: /* Participants */

=== Date and Time ===
Friday 2011-03-11 @08.00 - 09.00 UTC

=== Participants ===
Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Riku Voipio, Austin Zhang, Junfeng Dong, Paavo Leinonen

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* Junfeng Dong has joined Intel's toolchain team

=== Status ===
==== Intel ====
* Performance/regression test preparation
* Austin is a bit concerned about merging Linaro patches to FSF gcc 4.5.2/3 in case the merge happens too late. Concerns about regression testing etc. We should set up a continuous regression build test server somewhere.

==== ARM ====
* None

=== Decisions ===

=== Action points ===
AP: Juha - set up a draft wiki page for toolchain performance results, discuss if the format could be useful
AP: Juha - ssp related glibc ARM build problem must be solved

SDK/Toolchains/Meetings

2011-03-14T19:56:06Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated week 08/2011)

Meeting Minutes:
* Friday, 2011-03-11: [[SDK/Toolchains/Meetings/Notes20110311]]
* Friday, 2011-02-25: [[SDK/Toolchains/Meetings/Notes20110225]]
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains/Meetings/Notes20110311

2011-03-14T19:55:28Z

Kaltsi: Created page with "=== Date and Time === Friday 2011-03-11 @08.00 - 09.00 UTC === Participants === Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Riku Voipio, Austin Zhang, Junfeng Dong, Paavo …"

SDK/Toolchains/Meetings/Notes20110225

2011-03-03T14:03:13Z

Kaltsi: /* Action points */

=== Date and Time ===
Friday 2011-02-25 @08.00 - 09.00 UTC

=== Participants ===
Carsten Munk, Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Jarmo Kant, Martti Lumme, Austin Zhang, Paavo Leinonen

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* Nothing new about Nokia/MeeGo plans at this time

=== Status ===
==== Intel ====
* Intel will run performance/regression tests on gcc 4.5.2 starting next week

==== ARM ====
* Leonid is running performance tests every month on new Linaro toolchain releases

=== Decisions ===
* Austin's proposal about toolchain update from previous meeting for MeeGo 1.3 is basically ok, but we should see if gcc 4.5.3 is ready in time.
* It's now too late to update the compiler to gcc 4.5.2 or glibc to 2.12 in MeeGo 1.2
* We should come up with a deadline for toolchain related changes in MeeGo 1.3
* We should use MeeGo bugzilla to track bugs in the MeeGo toolchain

=== Action points ===
AP: Juha - add a link to the linaro bug about the ICE Carsten pasted
* [https://build.meego.com/package/live_build_log?arch=armv7el&package=ilmbase&project=Trunk&repository=standard]
* Bug created about a similar issue [https://bugs.launchpad.net/gcc-linaro/+bug/723185]

AP: Juha - list bugs fixed btwn 4.5.1 - > 4.5.2
* Here's a link to gcc project's buzilla listing the resolved bugs in 4.5.2 [http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.2]

AP: Paavo - arrange a telco with Linaro guys to discuss Linaro toolchain plans
* Telco is arranged for Wednesday 2011-03-02.
* Meeting minutes [[File:Meeting-linaro-tc-20110203.txt]]

File:Meeting-linaro-tc-20110203.txt

2011-03-03T14:02:02Z

Kaltsi: Telco with Linaro guys - discussion about Linaro's toolchain in general and MeeGo 1.3 toolchain plans.

Telco with Linaro guys - discussion about Linaro's toolchain in general and MeeGo 1.3 toolchain plans.

SDK/Toolchains/Meetings

2011-03-02T05:52:22Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated week 08/2011)

Meeting Minutes:
* Friday, 2011-02-25: [[SDK/Toolchains/Meetings/Notes20110225]]
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains/Meetings

2011-03-02T05:28:02Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated)

Meeting Minutes:
* Friday, 2011-02-25: [[SDK/Toolchains/Meetings/Notes20110225]]
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains/Meetings/Notes20110225

2011-03-01T12:59:07Z

Kaltsi: /* Action points */

SDK

2011-02-25T09:30:28Z

Kaltsi: /* Subsystems */

= MeeGo SDK =

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

== Using the SDK ==

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

== Contact ==

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

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

== SDK Development ==

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

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

=== SDK Program Organization ===

==== Management ====

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

==== Domains ====

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

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

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

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

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

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

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

==== Subsystems ====

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

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

* [[SDK/Toolchains]] - [http://meego.com/users/kaltsi Juha Kallioinen] - Toolchain Team Lead
** Al Nikolov - ARM
** Xu U Zhang - Intel

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

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

=== Meetings ===

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

=== Proposals & Studies ===

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

==== Active ====

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

==== Closed ====

* -

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

SDK/Toolchains/Meetings/Notes20110225

2011-02-25T09:27:37Z

Kaltsi: /* Date and Time */

=== Date and Time ===
Friday 2011-02-25 @08.00 - 09.00 UTC

=== Participants ===
Carsten Munk, Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Jarmo Kant, Martti Lumme, Austin Zhang, Paavo Leinonen

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* Nothing new about Nokia/MeeGo plans at this time

=== Status ===
==== Intel ====
* Intel will run performance/regression tests on gcc 4.5.2 starting next week

==== ARM ====
* Leonid is running performance tests every month on new Linaro toolchain releases

=== Decisions ===
* Austin's proposal about toolchain update from previous meeting for MeeGo 1.3 is basically ok, but we should see if gcc 4.5.3 is ready in time.
* It's now too late to update the compiler to gcc 4.5.2 or glibc to 2.12 in MeeGo 1.2
* We should come up with a deadline for toolchain related changes in MeeGo 1.3
* We should use MeeGo bugzilla to track bugs in the MeeGo toolchain

=== Action points ===
AP: Juha - add a link to the linaro bug about the ICE Carsten pasted
* [https://build.meego.com/package/live_build_log?arch=armv7el&package=ilmbase&project=Trunk&repository=standard]
* Bug created about a similar issue [https://bugs.launchpad.net/gcc-linaro/+bug/723185]

AP: Juha - list bugs fixed btwn 4.5.1 - > 4.5.2

AP: Paavo - arrange a telco with Linaro guys to discuss Linaro toolchain plans

SDK/Toolchains/Meetings

2011-02-25T09:27:16Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated)

Meeting Minutes:
* Friday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110225]]
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains/Meetings/Notes20110225

2011-02-25T09:26:15Z

Kaltsi: Created page with "=== Date and Time === Friday 2011-02-25 @10.00 - 11.00 UTC === Participants === Carsten Munk, Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Jarmo Kant, Martti Lumme, Austin Z…"

=== Date and Time ===
Friday 2011-02-25 @10.00 - 11.00 UTC

=== Participants ===
Carsten Munk, Juha Kallioinen, Leonid Moiseichuck, Al Nikolov, Jarmo Kant, Martti Lumme, Austin Zhang, Paavo Leinonen

=== Agenda ===
* General news
* Status
* AOB

=== General News ===
* Nothing new about Nokia/MeeGo plans at this time

=== Status ===
==== Intel ====
* Intel will run performance/regression tests on gcc 4.5.2 starting next week

==== ARM ====
* Leonid is running performance tests every month on new Linaro toolchain releases

=== Decisions ===
* Austin's proposal about toolchain update from previous meeting for MeeGo 1.3 is basically ok, but we should see if gcc 4.5.3 is ready in time.
* It's now too late to update the compiler to gcc 4.5.2 or glibc to 2.12 in MeeGo 1.2
* We should come up with a deadline for toolchain related changes in MeeGo 1.3
* We should use MeeGo bugzilla to track bugs in the MeeGo toolchain

=== Action points ===
AP: Juha - add a link to the linaro bug about the ICE Carsten pasted
* [https://build.meego.com/package/live_build_log?arch=armv7el&package=ilmbase&project=Trunk&repository=standard]
* Bug created about a similar issue [https://bugs.launchpad.net/gcc-linaro/+bug/723185]

AP: Juha - list bugs fixed btwn 4.5.1 - > 4.5.2

AP: Paavo - arrange a telco with Linaro guys to discuss Linaro toolchain plans

SDK/Toolchains/Meetings

2011-02-25T07:36:52Z

Kaltsi: /* MeeGo Toolchain Project Meetings */

== MeeGo Toolchain Project Meetings ==

Regular project meeting every second Friday @08.00 - 09.00 UTC.

Working environment at http://etherpad.piipiip.net/l7OtIB62DP (location updated)

Meeting Minutes:
* Monday, 2011-02-21: [[SDK/Toolchains/Meetings/Notes20110221]]
* Monday, 2011-01-31: [[SDK/Toolchains/Meetings/Notes20110131]]
* Friday, 2011-01-14: [[SDK/Toolchains/Meetings/Notes20110114]]
* Wednesday, 2011-01-05: [[SDK/Toolchains/Meetings/Notes20110105]]
* Friday, 2010-12-17: [[SDK/Toolchains/Meetings/Notes20101217]]
* Friday, 2010-11-19: [[SDK/Toolchains/Meetings/Notes20101119]]
* Monday, 2010-11-08: [[SDK/Toolchains/Meetings/Notes20101108]]
* Friday, 2010-10-22: [[SDK/Toolchains/Meetings/Notes20101022]]

SDK/Toolchains

2010-12-27T13:35:44Z

Kaltsi: /* Team */

== MeeGo Toolchain ==
MeeGo Toolchain Team is responsible of toolchain for MeeGo Platform.

=== Team ===
* Jarmo Kant, Nokia (jarmo.kant@nokia.com), IRC: jake-k
* Juha Kallioinen, Nokia (juha.kallioinen@nokia.com), IRC: kaltsi
* Al Nikolov, Nokia (al.nikolov@nokia.com)
* Martti Lumme, Nokia (martti.lumme@nokia.com), IRC: marlumme
* Alexander Kanevskiy, Nokia (alexander.kanevskiy@nokia.com)
* Leonid Moiseichuk, Nokia (leonid.moiseichuk@nokia.com)
* Austin Zhang, Intel (austin.zhang@intel.com), IRC: austin_zhang
* Jackie Wu, Intel (jackie.wu@intel.com)
* Jan-Simon Möller, Linux Foundation (jsmoeller@linuxfoundation.org), IRC: dl9pf

=== Change Proposals ===
* [[SDK/Toolchains/ToolchainChangeProposal]]

=== Meetings ===

Meeting agendas, minutes, etc. can be found from [[SDK/Toolchains/Meetings]]

=== MeeGo Toolchain Change Process ===
The following diagram figures out the process how the changes to the Toolchain components are done.

[[File:toolchain_change_process.png | 800px]]

It contains a following roles:
* MeeGo Community - self explaining role
* Request Initiator - A stakeholder that wants to change version or add/remove of some component in the Toolchain.
* MeeGo Toolchain WG - Toolchain working group in MeeGo
* Partner - A stakeholder using the Toolchain

Most important deliverable is the Change Request (CR). It is filed by the Request Initiator and contains the following information:
* Changed component
* Version change
* Business reason for the change
* Use Case describing the change and what is achieved with the change
* Test case(s) to validate the change. This should be a script that can be easily run and automated
* Impact analysis where the change affects
* Risks
Change request template: [[File:toolchain_cr_template.txt]]

The procedure step by step:
* Request Initiator wants to change Toolchain and files the CR
* Toolchain WG handles the CR, informs MeeGo community about the CR and pass the CR to the relevant Partners
* Partner possibly handles it in their internal decision making body and checks at least the following:
* changed component is buildable
* executes performance tests
* checks that the packages can be built using the changed Toolchain
* Report of the analysis is handled by the Partner and based on the results Partner gives verdict whether to approve or reject the CR.
* Response is handled in the MeeGo Toolchain WG and the Request Initiator is informed. If the change has been approved the change is scheduled to be taken into use and the MeeGo community is informed about the upcoming change.
* If the change has been rejected, the Request Initiator can escalate the change still (escalating path is TBD).