Meego Wiki
Views

SDK/1.2/Installer

From MeeGo wiki
< SDK(Difference between revisions)
Jump to: navigation, search
(Created page with "This page describes the design and components of the MeeGo SDK installer. The installer is currently === Background === The MeeGo SDK Installer is based on IFW (Nokia's recent...")
 
Line 5: Line 5:
=== Components ===
=== Components ===
-
TBD.
+
TBD. Simple design needed
=== Behavior ===
=== Behavior ===
Line 28: Line 28:
=== SDK Targets ===
=== SDK Targets ===
How to update targets:
How to update targets:
-
1. Target maintainer provides a madde config file (preferably a single file) that defines the target, and any new components (normal sysroot and runtime) used  by the target.
+
<ol>
-
2. Target maintainer provides some useful information of the target:
+
<li>Target maintainer provides a madde config file (preferably a single file) that defines the target, and any new components (normal sysroot and runtime) used  by the target.
-
a) Download size
+
<li>Target maintainer provides some useful information of the target:
-
b) Installed size
+
<li>Download size
-
3. Installer maintainer adds the config file into madde_configs directory  
+
<li>Installed size
-
4. Installer maintainer runs ./creat_repo.bat to generate the repository and push it to the repository server
+
<li>Installer maintainer adds the config file into madde_configs directory  
-
5. End user launches MeeGo SDK Maintenance Tool and select the new target to install
+
<li>Installer maintainer runs ./creat_repo.bat to generate the repository and push it to the repository server
 +
<li>End user launches MeeGo SDK Maintenance Tool and select the new target to install
 +
</ol>
-
How to package an App:
 
-
MeeGo SDK’s packaging functionality is integrated with MeeGo SDK QtCreator. You can get an RPM package by doing the following steps:
 
-
1. Install MeeGo SDK
 
-
2. Launch MeeGo SDK QtCreator
 
-
3. Open an existing project or new a project
 
-
4. Click “Run” or “Debug” button.
 
-
If everything goes well, an RPM package will be generated in <project dir>/../<project>-build-meego/rrpmbuild. The package is a very basic RPM package, whose main purpose is to help QtCreator to deploy files to QEMU or devices. If you want to refine the package, please modify <project dir>/<project>.spec according to your needs.
+
=== Adding additional tools to the SDK installer ===
 +
It is possible to augment the installer so that additional development tools can be installed.
 +
TBD:  Design. Types of development tools. Open source. Restrictions
 +
Steps to accomplish:
 +
* People to talk to
 +
  * QA process
 +
  * Components:  GUI, config values, packages, files, libraries, Qt Creator modifications

Latest revision as of 18:02, 3 May 2011

This page describes the design and components of the MeeGo SDK installer. The installer is currently

Contents

Background

The MeeGo SDK Installer is based on IFW (Nokia's recently open-sourced Installer Framework).

Components

TBD. Simple design needed

Behavior

Windows:

Steps to install:
Components installed:
 Registry keys:
 Files:
 Libraries:
 Executables:
 File locations:

Linux:

Steps to install:
Components installed:
 Packages:
 Libraries:
 Executables:
 Config keys:
 File locations:

SDK Targets

How to update targets:

  1. Target maintainer provides a madde config file (preferably a single file) that defines the target, and any new components (normal sysroot and runtime) used by the target.
  2. Target maintainer provides some useful information of the target:
  3. Download size
  4. Installed size
  5. Installer maintainer adds the config file into madde_configs directory
  6. Installer maintainer runs ./creat_repo.bat to generate the repository and push it to the repository server
  7. End user launches MeeGo SDK Maintenance Tool and select the new target to install


Adding additional tools to the SDK installer

It is possible to augment the installer so that additional development tools can be installed. TBD: Design. Types of development tools. Open source. Restrictions Steps to accomplish:

* People to talk to
* QA process
* Components:  GUI, config values, packages, files, libraries, Qt Creator modifications
Personal tools