Mer/Documentation/SDK
 |
Mer is back : Please visit http://www.merproject.org to learn more about this news. |
[edit] 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
[edit] Pre 0.13 SDK (armv5te)
First, install Fremantle SDK, and add yourself as a user to scratchbox.
As user:
- wget -c http://stskeeps.subnetmask.net/mer/arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb
- sudo dpkg -i arm-linux-cs2008q3-72-libtool2_1.0.11_i386.deb (run as root)
- wget -c http://stskeeps.subnetmask.net/mer/scratchbox-devkit-mer_1.0.11_i386.deb
- sudo dpkg -i scratchbox-devkit-mer_1.0.11_i386.deb
- You can optionally get qemu-arm-eabi and use that here instead. It is very good for your use of the SDK
- sb-conf setup MER-ARMEL --compiler=arm-linux-cs2008q3-72-libtool2 --devkits=debian-etch:cputransp:perl:mer --cputransp=qemu-arm-cvs-m -f
- sb-conf reset -f MER-ARMEL
- sb-conf select MER-ARMEL
- sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz
- sb-conf install MER-ARMEL --etc --devkits --fakeroot
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.
- This page was last modified on 22 September 2010, at 10:50.
- This page has been accessed 7,692 times.