The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Platform SDK
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 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.
Using the platform SDK
Installation / setup
The platform SDK is provided as a rootfs tarball that contains essential tools for Mer platform development along with a helper script to enter the rootfs.
Please note that the platform SDK requires that you're using a Linux distribution (one in a virtual machine works as well).
To setup the SDK: - Create directory for the SDK rootfs and download the latest stable SDK rootfs tarball
mkdir $HOME/mer-sdk && cd $HOME/mer-sdk curl -O url_to_be_defined
- extract the tarball as root or with sudo
sudo tar xzvf mer-platform-sdk-latest-stable.tar.gz
Entering chroot
TODO
SDK contents
The platform SDK's rootfs has... TODO
Compiling with the SDK
TODO
Building an image
TODO
Development Documentation
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 or access to an OBS.
- Offline compilation must be possible
- Clearly document the difference between platform SDK and application SDK.
- Document the SDK tools for easier porting to new Linux distributions (if all SDK tools, and nothing else, comes from a single OBS project, that might be enough 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
Goals for the first version (Proposal)
The target is to provide a Linux distribution agnostic SDK in form of rootfs image to enable people working on Mer to compile, package and hack on Mer offline and without OBS access.
The initial version should contain the following
- Mer rootfs
- working zypper, etc
- script to setup mounts
- Mounts host root and users home from host
- Cross compilers
- scratchbox2
- x86
- arm
- mips
- packaging tools
- spectacle, etc.
- image creation tools
- mic
- Documentation
- howtos, etc.
Work so far
- COBS project : home:stskeeps:tools
- basic kickstart: http://releases.merproject.org/~carsten/mer-core-i586-sdk.ks
- rootfs : http://releases.merproject.org/~carsten/mer-core-i586-sdk-test.tar.gz
- script to mount the rootfs : https://gitorious.org/random-timoph/scripts/blobs/master/mer/enter-chroot.sh
QA
TBD
SDK team meeting minutes
- 13.1.2012 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-01-13-18.02.html
- 28.1.2012 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-01-28-10.04.log.html
