Meego Wiki
Views

SDK/MeeGo 1.1 Application SDK Project Plan

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Mission)
(Removed one level from the headings)
Line 1: Line 1:
-
== MeeGo 1.1 Application SDK Project Plan !!! DRAFT !!! ==
+
''' !!! THIS IS STILL A DRAFT !!! '''
This document describes the MeeGo 1.1 Application SDK contents and how we get there. It should include but not limit to:
This document describes the MeeGo 1.1 Application SDK contents and how we get there. It should include but not limit to:
Line 7: Line 7:
* Resources allocated with clear R&R
* Resources allocated with clear R&R
-
=== Mission ===
+
== Mission ==
* Delivering MeeGo SDK for developers to develop MeeGo Applicaitons at best chance running across platforms and segments(netbook, handset, tablet and TV..).
* Delivering MeeGo SDK for developers to develop MeeGo Applicaitons at best chance running across platforms and segments(netbook, handset, tablet and TV..).
Line 17: Line 17:
The application SDK should run on multiple different host environments (Linux, Win, Mac). In general all the parts of the Application SDK should run similarly on all the hosts! Still it is possible that we will have features that will only work on some of the hosts or with only some of the targets. This aspect should be considered in the SDK architecture.
The application SDK should run on multiple different host environments (Linux, Win, Mac). In general all the parts of the Application SDK should run similarly on all the hosts! Still it is possible that we will have features that will only work on some of the hosts or with only some of the targets. This aspect should be considered in the SDK architecture.
-
=== Key Drivers ===
+
== Key Drivers ==
* MeeGo Application SDK which allows developers to use any host and develop to any target with a similar manner.
* MeeGo Application SDK which allows developers to use any host and develop to any target with a similar manner.
Line 28: Line 28:
-
=== Project Group ===
+
== Project Group ==
This chapter lists the people involved an their responsibilities.
This chapter lists the people involved an their responsibilities.
Line 35: Line 35:
-
=== Schedule ===
+
== Schedule ==
-
==== Milestones ====
+
=== Milestones ===
{| class="wikitable" border=1
{| class="wikitable" border=1
Line 54: Line 54:
|}
|}
-
==== Meetings ====
+
=== Meetings ===
-
=== Architecture of MeeGo SDK ===
+
== Architecture of MeeGo SDK ==
-
===Integration, Distribution and Installation of MeeGo SDK===
+
== Integration, Distribution and Installation of MeeGo SDK ==
How MeeGo SDK components to be integrated and distributed
How MeeGo SDK components to be integrated and distributed
Line 64: Line 64:
** QT Creator
** QT Creator
** QEMU
** QEMU
-
** Xephry
+
** Xephyr
** Mad-developer
** Mad-developer
Line 81: Line 81:
-
=== Quality Assurance ===
+
== Quality Assurance ==
*QA should cover:
*QA should cover:
Line 92: Line 92:
** Other tools, like packaging tool, performance tunning tools.
** Other tools, like packaging tool, performance tunning tools.
-
=== Key Components of MeeGo SDK ===
+
== Key Components of MeeGo SDK ==
The components of MeeGo Application SDK are listed in this section. Each component should have a responsible, package maintainer and some status information as we go along.
The components of MeeGo Application SDK are listed in this section. Each component should have a responsible, package maintainer and some status information as we go along.
-
====  Qt Creator ====
+
===  Qt Creator ===
Qt Creator is the chosen IDE for MeeGo Application SDK.  
Qt Creator is the chosen IDE for MeeGo Application SDK.  
Line 108: Line 108:
** Adding MADDE targets seems somewhat complicated
** Adding MADDE targets seems somewhat complicated
-
=====Compiling plugins=====
+
====Compiling plugins====
The compiling plugins are used for compiling and packaging the software with different tools (MADDE / OBS). The end result should be installable application RPM.
The compiling plugins are used for compiling and packaging the software with different tools (MADDE / OBS). The end result should be installable application RPM.
-
======MADDE plugin======
+
=====MADDE plugin=====
This plugin uses MADDE for compiling and packaging the software.
This plugin uses MADDE for compiling and packaging the software.
Line 121: Line 121:
** Just a dream
** Just a dream
-
====== OBS plugin ======
+
===== OBS plugin =====
This plugin uses OBS for compiling and packaging the software.
This plugin uses OBS for compiling and packaging the software.
Line 130: Line 130:
** Just a dream
** Just a dream
-
===== Run plugins =====
+
==== Run plugins ====
The run plugins are used for installing, running and debugging the software. In general the plugin could use e.g. MADDE to provide this feature.
The run plugins are used for installing, running and debugging the software. In general the plugin could use e.g. MADDE to provide this feature.
-
====== Qemu plugin ======
+
===== Qemu plugin =====
This plugin provides the possibility to use Qemu for "Run plugin" features. This plugin uses MADDE.
This plugin provides the possibility to use Qemu for "Run plugin" features. This plugin uses MADDE.
Line 143: Line 143:
** Just a dream
** Just a dream
-
====== Device run plugin ======
+
===== Device run plugin =====
This plugin provides the possibility to use real devices for "Run plugin" features. This plugin uses MADDE.
This plugin provides the possibility to use real devices for "Run plugin" features. This plugin uses MADDE.
Line 152: Line 152:
** Just a dream
** Just a dream
-
====== Xephyr plugin ======
+
===== Xephyr plugin =====
This plugin provides the possibility to use Xephyr (and chroot) for "Run plugin" features.
This plugin provides the possibility to use Xephyr (and chroot) for "Run plugin" features.
Line 161: Line 161:
** Just a dream
** Just a dream
-
===== Debugging plugins =====
+
==== Debugging plugins ====
These plugins are used for debugging in Qt Creator. These could use MADDE for running the debuggers etc. and different kind of methods for visualization.
These plugins are used for debugging in Qt Creator. These could use MADDE for running the debuggers etc. and different kind of methods for visualization.
-
====== Valgrind ======
+
===== Valgrind =====
TODO
TODO
Line 174: Line 174:
** Just a dream
** Just a dream
-
====== Oprofile ======
+
===== Oprofile =====
TODO
TODO
Line 184: Line 184:
-
====  MADDE ====
+
===  MADDE ===
MADDE is multiplatform toolset for compiling, running, debugging and testing.
MADDE is multiplatform toolset for compiling, running, debugging and testing.
Line 197: Line 197:
** Not part of the OBS builds yet
** Not part of the OBS builds yet
-
==== Compiling ====
+
=== Compiling ===
Compiling is done with combination of a cross-compiler and a sysroot which
Compiling is done with combination of a cross-compiler and a sysroot which
includes target headers and libraries. Compilers come with MADDE.
includes target headers and libraries. Compilers come with MADDE.
-
===== Hosts and Targets =====
+
==== Hosts and Targets ====
Status of the supported hosts and targets:
Status of the supported hosts and targets:
Line 227: Line 227:
|}
|}
-
====== Sysroots ======
+
===== Sysroots =====
Sysroot is a collection of target headers and libraries which are used by the compilers to compile the software.
Sysroot is a collection of target headers and libraries which are used by the compilers to compile the software.
Line 251: Line 251:
|}
|}
-
====== Cross-Compilers ======
+
===== Cross-Compilers =====
Cross-compiler status per host and responsibles:
Cross-compiler status per host and responsibles:
Line 294: Line 294:
|}
|}
-
==== Running ====
+
=== Running ===
With MADDE the application developer can create RPM package on any host
With MADDE the application developer can create RPM package on any host
Line 300: Line 300:
emulation.
emulation.
-
===== RPM support =====
+
==== RPM support ====
RPM packager is created with ...
RPM packager is created with ...
Line 325: Line 325:
|}
|}
-
===== Targets (devices / Emulation) =====
+
==== Targets (devices / Emulation) ====
-
====== Aava ======
+
===== Aava =====
-
====== N900 ======
+
===== CDK =====
 +
===== N900 =====
-
====== Qemu ======
+
 
 +
===== Qemu =====
The status and the responsible of the Qemu on different host platforms.
The status and the responsible of the Qemu on different host platforms.
Line 375: Line 377:
|}
|}
-
======= Qemu Images =======
+
====== Qemu Images ======
The Qemu images are images used with the QEMU full system emulation. The images are as similar as possible to the actual device images.
The Qemu images are images used with the QEMU full system emulation. The images are as similar as possible to the actual device images.
Line 398: Line 400:
-
==== Testing & Debugging tools ====
+
=== Testing & Debugging tools ===
What do we have?
What do we have?
-
=== Documentation of MeeGo SDK ===
+
== Documentation of MeeGo SDK ==
The Documentation of MeeGo SDK tells how to install/set up MeeGo SDK on any host machine, how to get started to use SDK to create first MeeGo applicaiton, including creating project, editing, compiling and building and remotely deploying and debuging applicaton.  
The Documentation of MeeGo SDK tells how to install/set up MeeGo SDK on any host machine, how to get started to use SDK to create first MeeGo applicaiton, including creating project, editing, compiling and building and remotely deploying and debuging applicaton.  
Supported APIs are also important part of SDK docmentation.
Supported APIs are also important part of SDK docmentation.

Revision as of 08:57, 17 June 2010

 !!! THIS IS STILL A DRAFT !!!

This document describes the MeeGo 1.1 Application SDK contents and how we get there. It should include but not limit to:

  • Key requirements of MeeGo SDK release matching MeeGo 1.1 release in Oct
  • Get aligned on MeeGo SDK milestones
  • List major tasks/deliverables of SDK
  • Resources allocated with clear R&R

Contents

Mission

  • Delivering MeeGo SDK for developers to develop MeeGo Applicaitons at best chance running across platforms and segments(netbook, handset, tablet and TV..).
  • Shape MeeGo APIs and compliance with MeeGo SDK.
  • Build MeeGo ecosystem with MeeGo SDK.

MeeGo 1.1 Application SDK is going to be the first MeeGo Application SDK release created in collaboration between MeeGo partners (Nokia & Intel at this point). The Application SDK is mainly targetted for Application developers who are interested in creating new applications for MeeGo platform.

The application SDK should run on multiple different host environments (Linux, Win, Mac). In general all the parts of the Application SDK should run similarly on all the hosts! Still it is possible that we will have features that will only work on some of the hosts or with only some of the targets. This aspect should be considered in the SDK architecture.

Key Drivers

  • MeeGo Application SDK which allows developers to use any host and develop to any target with a similar manner.
    • The host OSs include Windows, Linux (Ubuntu and Fedora??) and Mac OS.
    • The targets include CDK,Aava and N900 or simulators/emulators.
    • Support both 64bits and 32 bits host machines
    • Have a possibility for allowing features that only work on specific hosts or for specific targets
  • SDK development process agreed and active


Project Group

This chapter lists the people involved an their responsibilities.

  • Veli Kaksonen : Nokia MeeGo SDK project manager


Schedule

Milestones

id Date Short description
M1 20100630 Project start (Targets set, resources allocated...)
M2 2010???? Beta release...

Meetings

Architecture of MeeGo SDK

Integration, Distribution and Installation of MeeGo SDK

How MeeGo SDK components to be integrated and distributed

  • Some components should be put into OBS and maintained there as RPMs, like
    • QT Creator
    • QEMU
    • Xephyr
    • Mad-developer
  • Or just be packaged as tarball and maintained in gitorious, like
    • Madde
  • Some components should be created based on the MeeGo build by using tools/scripts, like
    • Simulator images
    • QEMU/emulator images
    • Sysroots
    • Toolchains
  • MeeGo Application SDK will be built in sync with the MeeGo weekly builds. ...
  • Installer of SDK should be developed to package everything of MeeGo SDK into one package (bin)
  • End users just need to download the SDK Installers (for Windows, Linux and Mac), and then execute it to install MeeGo SDK on hosts.


Quality Assurance

  • QA should cover:
    • SDK documentations, like how to install and set up SDK, how to Get Started, how to build, debug;
    • SDK components: QT Creator, Madde, sysroots, Toolchains;
    • Simulator/Emulator
    • Simulator images and Emulator images
    • Simulated devices
    • Demo applications/APIs
    • Other tools, like packaging tool, performance tunning tools.

Key Components of MeeGo SDK

The components of MeeGo Application SDK are listed in this section. Each component should have a responsible, package maintainer and some status information as we go along.

Qt Creator

Qt Creator is the chosen IDE for MeeGo Application SDK.

  • Key Requirements for MeeGo1.1:
    • Support mutiple targets, like N900, CDK and Aava;
    • Support remote deploying and debugging.
  • Responsible: Maurice Kalinowski
  • Package Maintainer: Fathi Boudra
  • Status:
    • Not part of the OBS builds yet
    • Adding MADDE targets seems somewhat complicated

Compiling plugins

The compiling plugins are used for compiling and packaging the software with different tools (MADDE / OBS). The end result should be installable application RPM.

MADDE plugin

This plugin uses MADDE for compiling and packaging the software.

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream
OBS plugin

This plugin uses OBS for compiling and packaging the software.

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream

Run plugins

The run plugins are used for installing, running and debugging the software. In general the plugin could use e.g. MADDE to provide this feature.

Qemu plugin

This plugin provides the possibility to use Qemu for "Run plugin" features. This plugin uses MADDE.

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream
Device run plugin

This plugin provides the possibility to use real devices for "Run plugin" features. This plugin uses MADDE.

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream
Xephyr plugin

This plugin provides the possibility to use Xephyr (and chroot) for "Run plugin" features.

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream

Debugging plugins

These plugins are used for debugging in Qt Creator. These could use MADDE for running the debuggers etc. and different kind of methods for visualization.

Valgrind

TODO

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream
Oprofile

TODO

  • Responsible: unknown
  • Package Maintainer: unknown
  • Status:
    • Just a dream


MADDE

MADDE is multiplatform toolset for compiling, running, debugging and testing. It provides same API for underlying tools on all the host platforms. MADDE can be used from commandline or from IDE. Primary IDE is Qt Creator but others, like eclipse, can be supported too (although not in this project).

  • Responsible: Jari Ihatsu
  • Package Maintainer: Fathi Boudra
  • Status:
    • We have a build of MADDE that includes MeeGo ARM target
    • Not part of the OBS builds yet

Compiling

Compiling is done with combination of a cross-compiler and a sysroot which includes target headers and libraries. Compilers come with MADDE.

Hosts and Targets

Status of the supported hosts and targets:

MeeGo chroot Ubuntu 32bit Ubuntu 64bit Fedora 32bit Fedora 64bit Windows 7 Mac OS X
ARMv5 - (cs2007q3)  ?
ARMv7 - (cs2007q3)  ?
Intel (gcc-...) ok
Sysroots

Sysroot is a collection of target headers and libraries which are used by the compilers to compile the software.

Sysroot responsibles and statuses:

sysroot Responsible Status
ARMv5  Fathi Boudra Work in progress
ARMv7 Fathi Boudra Work in progress
Intel  ?  ?
Cross-Compilers

Cross-compiler status per host and responsibles:

ARM-cs2007q3 ARM-MeeGo 4.? Intel-MeeGo 4.?
MeeGo chroot (not planned)  (not planned) (ok)  ?
Ubuntu 32bit (ok) Martti Lumme (work in progress)
Ubuntu 64bit  (ok)  
Fedora 32bit  (ok)  
Fedora 64bit  (ok)  
Windows 7  (ok)  
Mac OS X  (ok)  

Running

With MADDE the application developer can create RPM package on any host environment, transfer and run the software on the device or in the emulation.

RPM support

RPM packager is created with ...

The status of the RPM support on different host platforms.

Host RPM creation Transfer Run
Ubuntu 32bit
Ubuntu 64bit
Fedora 32bit
Fedora 64bit
Windows 7
Mac OS X

Targets (devices / Emulation)

Aava
CDK
N900
Qemu

The status and the responsible of the Qemu on different host platforms.

ARMv5 (N900) ARMv7 (N900) Intel (Aava?)
Ubuntu 32bit Riku Voipio (ok) Riku Voipio (ok)  ?
Ubuntu 64bit Riku Voipio (ok) Riku Voipio (ok)  ?
Fedora 32bit Riku Voipio (ok) Riku Voipio (ok)  ?
Fedora 64bit Riku Voipio (ok) Riku Voipio (ok)  ?
Windows 7 Riku Voipio (ok) Riku Voipio (ok)  ?
Mac OS X  ?  ?  ?
Qemu Images

The Qemu images are images used with the QEMU full system emulation. The images are as similar as possible to the actual device images.

Target Responsible Status
ARMv5 (Qemu N900) Fathi Boudra Work in progress
ARMv7 (Qemu N900) Fathi Boudra Work in progress
Intel (Aava?)  ?  ?


Testing & Debugging tools

What do we have?

Documentation of MeeGo SDK

The Documentation of MeeGo SDK tells how to install/set up MeeGo SDK on any host machine, how to get started to use SDK to create first MeeGo applicaiton, including creating project, editing, compiling and building and remotely deploying and debuging applicaton.

Supported APIs are also important part of SDK docmentation.

Retrieved from "http://wiki.meego.com/SDK/MeeGo_1.1_Application_SDK_Project_Plan"
Personal tools