| Line 8: | Line 8: | ||
== Topics Reviewed == | == Topics Reviewed == | ||
| - | === | + | === Content of the default sysroot === |
| - | + | Description: The SDK uses a sysroot for the MeeGo libraries that can be built with on the host system. We need to clarify what is in this default set. | |
| - | + | ||
* Use current sysroot contents. Includes libraries for compliance with some extras | * Use current sysroot contents. Includes libraries for compliance with some extras | ||
| Line 16: | Line 15: | ||
* AP: Fathi -- Create 2 sysroots: small and full (all devel). See how big the "slim" versions are. | * AP: Fathi -- Create 2 sysroots: small and full (all devel). See how big the "slim" versions are. | ||
* AP: Fathi -- resolve ks content / organization | * AP: Fathi -- resolve ks content / organization | ||
| + | * Future: Veli is investigating how to map QEMU image and use libraries directly. | ||
| + | |||
| + | === 3rd Party Library use === | ||
| + | '''Date reviewed:''' Thursday Jan 13 05:30 UTC <br /> | ||
| + | '''Description:''' Developers need a way to use additional, custom libraries that are not part of the default sysroot. One way to do this is to recreate the sysroot, but this is timeconsuming. Another way is to allow developers to specify the location of 3rd party libraries and include them in their project in addition to the sysroot. | ||
| + | |||
| + | * Will use package injection/removal | ||
| + | * take files from RPM or DEB and add to sysroot | ||
| + | * MADDE command 'mad xdpkg' can do this for debian-based sysroots; Will add rpm feature. Works in Windows too. | ||
| + | * Qt Creator 2.1 enables adding a project target to the sysroot itself, enhancing the sysroot with libraries/applications. | ||
| + | * AP: Maurice to investigate changes needed for Qt Creator. | ||
| + | * AP: Tomi to add RPM feature | ||
| + | * AP: Jackie to play with existing feature | ||
| + | * Future: Veli is investigating how to map QEMU image and use libraries directly. If done, users could update the libraries inside QEMU. | ||
=== MeeGo SDK Installer for Linux === | === MeeGo SDK Installer for Linux === | ||
| Line 30: | Line 43: | ||
* Start Qt Creator | * Start Qt Creator | ||
| - | Nokia is working on a "super installer" which will allow extension for 3rd party libraries such as Intel tools. | + | Resolution: |
| + | * Installer will install distribution-specific packages | ||
| + | * Bangalore team working on an interface: Installer detects system. Looks online for map to repo. Pulls from right repo. Uses right tools (apt/yum/zypper) | ||
| + | * Power user can still install manually | ||
| + | * Requires build repository into OBS for every distribution release (fedora14, ubuntu 10.10, etc.) | ||
| + | * Dependencies of host distribution can be used. | ||
| + | * IFW may be extended to use Bangalore package-installing backend | ||
| + | * Timeframe: Further discussion @F2F | ||
| + | * Owner: Bangalore backend. Maurice IFW. | ||
| + | * AP: Kamal to send design and other info to Maurice / Intel (Done!) | ||
| + | * Nokia is working on a "super installer" which will allow extension for 3rd party libraries such as Intel tools. | ||
This page is to collect and track status for major decisions regarding the MeeGo SDK. Please add topics under the "Topics to review" heading.
Meeting times: Thursdays at 05:30 UTC
Minutes: http://piratepad.net/qqICWdiYLl
Contents |
Description: The SDK uses a sysroot for the MeeGo libraries that can be built with on the host system. We need to clarify what is in this default set.
Date reviewed: Thursday Jan 13 05:30 UTC
Description: Developers need a way to use additional, custom libraries that are not part of the default sysroot. One way to do this is to recreate the sysroot, but this is timeconsuming. Another way is to allow developers to specify the location of 3rd party libraries and include them in their project in addition to the sysroot.
Date to review: Thursday Jan 13 05:30 UTC
Description:
The Linux SDK needs to be easy to install. An installer could help with:
Resolution: