Mir
|
There are a few ways to compile Mir for an ARM device. You should only need to choose one of these approaches...
If you have an ARM device you should be able to compile and install directly on the device. Although this will usually be significantly slower than using a desktop. On the armhf or arm64 target device just follow these steps:
$ mk-build-deps --install --tool "apt-get -y" --build-dep debian/control $ cmake .. -DMIR_PLATFORM=android $ make $ make install
The addional cmake option -DMIR_ENABLE_TESTS=off can be used to avoid building the test suite to save time.
Using a current Ubuntu (15.04 or later) installation it's very simple to build binaries for armhf devices. Just follow these steps:
$ sudo apt-get install g++-arm-linux-gnueabihf debootstrap $ cd mir_source_dir $ ./cross-compile-chroot.sh $ ls -l build-android-arm/* # binaries to copy to your device as you wish
To speed up the process for future runs of cross-compile-chroot.sh, some files are saved in ~/.cache/. To flush the cache and download new armhf packages just add the -u option to cross-compile-chroot.sh.
"sbuild" is recommended to compile Mir packages with armhf. Information on setting up sbuild can be found here:
If you do not wish to run the Mir test suite during package generation, set DEB_BUILD_OPTIONS=nocheck to your environment
This uses qemu to compile the package. Substitute <version_string> for the .dsc file name generated by the debuild command.
$ cd mir_source_dir $ debuild -S -uc -us $ cd .. $ sbuild -d vivid --arch armhf mir_<version_string>.dsc
This uses a cross-compile toolchain to compile the package, and generally should be faster than the emulated sbuild package generation.
Substitute <version_string> for the .dsc file name generated by the debuild command.
$ cd mir_source_dir $ debuild -S -uc -us $ cd .. $ sbuild -d vivid --host armhf --build amd64 mir_<version_string>.dsc
Copyright © 2012-2015 Canonical Ltd.
Generated on Thu Oct 8 16:20:16 UTC 2015