The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Platform SDK
(New page: = Mer platform SDK = TBD == SDK team meeting minutes == * 13.1.2012 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-01-13-18.02.html) |
|||
| Line 1: | Line 1: | ||
= Mer platform SDK = | = Mer platform SDK = | ||
| − | + | To avoid any confusion, there are two types of SDKs: Application SDKs and Platform SDKs. Application SDK's are the ones that deal with Qt applications and libraries, HTML5, etc, while Platform SDK's are for developing the platform, compiling native code and other things revolving around the platform a developer/hacker needs. | |
| + | |||
| + | The platform SDK aims to offer a installable disk image that can be run on virtual machines (typically) or actual hardware, which contains tools like Scratchbox2, MIC (image creator), spectacle, osc, qemu, etc preinstalled, to make it easier for a developer to work with Mer. | ||
| + | |||
| + | Please note that the platform SDK is a work on progress. The work for making the sdk was kicked off January 13 2012. If you are willing to contribute to the effort, please do so. | ||
| + | |||
| + | == Requirements == | ||
| + | The following requirements were agreed on the initial platform sdk brainstorming meeting (things may change) | ||
| + | * platform sdk needs to be able to function without an obs account and access to a obs | ||
| + | * Offline compilation must be possible | ||
| + | * emphasis on documentation | ||
| + | * seperation of user /home and 'sdk' | ||
| + | * need short path from: code, build, deploy, boo | ||
| + | * minimal http server to SDK for built rpm repo serving | ||
| + | |||
| + | == Available tasks == | ||
| + | * Make Mer:PlatformSDK OBS project for what goes into the 'image' | ||
| + | * package spectacle, mic, qemu, osc, .. what else? for Mer and dependancies | ||
== SDK team meeting minutes == | == SDK team meeting minutes == | ||
* 13.1.2012 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-01-13-18.02.html | * 13.1.2012 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-01-13-18.02.html | ||
| + | |||
| + | == Usefull links and further reading == | ||
| + | * http://tuomas.kulve.fi/blog/2011/07/09/meego-1-2-armv7-chroot-beta/ | ||
| + | * https://source.tizen.org/platform_sbs_install.html | ||
| + | * http://maemo-sdk.garage.maemo.org/user-guide.html | ||
Revision as of 19:53, 13 January 2012
Contents |
Mer platform SDK
To avoid any confusion, there are two types of SDKs: Application SDKs and Platform SDKs. Application SDK's are the ones that deal with Qt applications and libraries, HTML5, etc, while Platform SDK's are for developing the platform, compiling native code and other things revolving around the platform a developer/hacker needs.
The platform SDK aims to offer a installable disk image that can be run on virtual machines (typically) or actual hardware, which contains tools like Scratchbox2, MIC (image creator), spectacle, osc, qemu, etc preinstalled, to make it easier for a developer to work with Mer.
Please note that the platform SDK is a work on progress. The work for making the sdk was kicked off January 13 2012. If you are willing to contribute to the effort, please do so.
Requirements
The following requirements were agreed on the initial platform sdk brainstorming meeting (things may change)
- platform sdk needs to be able to function without an obs account and access to a obs
- Offline compilation must be possible
- emphasis on documentation
- seperation of user /home and 'sdk'
- need short path from: code, build, deploy, boo
- minimal http server to SDK for built rpm repo serving
Available tasks
- Make Mer:PlatformSDK OBS project for what goes into the 'image'
- package spectacle, mic, qemu, osc, .. what else? for Mer and dependancies
