Mer/Documentation/SDK

m (Begin update)
Line 1: Line 1:
-
== SDK (armv5te) ==
+
== Mer Development ==
 +
 
 +
Mer development is currently based around the OBS tools.
 +
 
 +
Install <code>osc</code> as described on the [[Mer/Build]] page.
 +
 
 +
TODO: work through: linking home to various Mer build targets; creating a package on OBS home:<username>, building using  tar.gz, diff.gz and .dsc files. chroot using qemu and sharing with local desktop. Uploading files to OBS. Promotion
 +
 
 +
 
 +
== Pre 0.13 SDK (armv5te) ==
First, install Fremantle SDK, and add yourself as a user to scratchbox.
First, install Fremantle SDK, and add yourself as a user to scratchbox.

Revision as of 16:56, 26 May 2009

Mer Development

Mer development is currently based around the OBS tools.

Install osc as described on the Mer/Build page.

TODO: work through: linking home to various Mer build targets; creating a package on OBS home:<username>, building using tar.gz, diff.gz and .dsc files. chroot using qemu and sharing with local desktop. Uploading files to OBS. Promotion


Pre 0.13 SDK (armv5te)

First, install Fremantle SDK, and add yourself as a user to scratchbox.

As user:

ISSUES:

  • You might have to do export PKG_CONFIG_PATH=/usr/share/pkgconfig:/usr/lib/pkgconfig to get some pkg-config stuff going
  • You might have to set cpu right and such to target armv5el (no vfp)
  • You probably need to get EABI cpu transparency target too
  • 'not safe for cross-compilation' warnings (not true, i think)
  • fakeroot apt-get dist-upgrade is good once in a while to keep up to date.