Difference between revisions of "Buildroot Packages"
m (New page: In this page you will learn how to add a new package or a new application to the Armadeus buildroot == Preliminary work == *1] Take a look at the buildroot mailing list to check whether ...) |
m |
||
Line 30: | Line 30: | ||
If this command works, test your package on an Armadeus plateform. If it's ok you can jump to the next chapter and proceed with the integration into buildroot. | If this command works, test your package on an Armadeus plateform. If it's ok you can jump to the next chapter and proceed with the integration into buildroot. | ||
Otherwise it is perhaps necessary to do some modifications of the sources/Makefile. | Otherwise it is perhaps necessary to do some modifications of the sources/Makefile. | ||
+ | Start by creating a new folder containing the package to modify: | ||
+ | $ cd buildroot/build_arm | ||
+ | $ cp -Rf toto toto.org | ||
+ | Now perform the modifications in the ''toto'' directory until you get a running package. Once done, one or several patches will be probably required against the original sources: | ||
+ | $ diff -rup toto.org/fichier toto/fichier > ../package/toto/toto.0.patch | ||
+ | |||
+ | These patches will be applied by the toto.mk file. Save your work and check it: | ||
+ | $ mv toto toto.ok | ||
+ | $ cd ../.. | ||
+ | $ make -C buildroot/ toto | ||
− | + | if it is ok, remove the directories buildroot/build_arm/toto.org and buildroot/build_arm/toto.ok which are now useless | |
+ | |||
+ | |||
+ | == Integration of the package into Buildroot == | ||
+ | |||
+ | |||
+ | Once the package or the application successfully tested, add a reference to package/toto/Config.in. | ||
+ | $ cp buildroot/package/Config.in buildroot/package/Config.org | ||
+ | then perform the modifications in the Config.in and start buildroot menuconfig | ||
+ | $ make menuconfig | ||
+ | Select your package in the menu "package", save the configuration et retry the installation: | ||
+ | $ make toto-dirclean | ||
+ | $ make | ||
+ | |||
+ | As soon as all is ok, you need to create the configuration patch for buildroot:( file buildroot/package/Config.in) with the same method as before | ||
+ | |||
+ | $ diff -rup buildroot/package/Config.org buildroot/package/Config.in > patches/numero_buildroot_nompaquet.diff | ||
+ | |||
+ | == Add the new package to the Armadeus distro == | ||
+ | |||
+ | All the files located in buildroot/package/toto and the patches (buildroot configuration) as well have to be added to SVN | ||
+ | |||
+ | $ svn add -N fichiers | ||
+ | $ svn commit -m [BUILDROOT PACKAGE] Adding an usefull toto package files --non-interactive | ||
+ | |||
+ | |||
+ | And now check with a fresh developpement tree... |
Revision as of 20:14, 19 May 2008
In this page you will learn how to add a new package or a new application to the Armadeus buildroot
Contents
Preliminary work
- 1] Take a look at the buildroot mailing list to check whether the work has not already been done
- 2] Send an email on the Armadeus mailing list (SourceForge) to verify that nobody is working on this package or to get help
- Check that the package is not available here: http://www.daimi.au.dk/~spider/gumstix/gumstix-buildroot/package/
- or here: http://downloads.openwrt.org/whiterussian/packages/ then https://dev.openwrt.org/browser/branches/whiterussian/openwrt/package
- 3] Create a directory in buildroot/package. For our exemple we will install the package named "toto"
$ mkdir buildroot/package/toto
- 4] In this folder, create a new Makefile "toto.mk" and a new config file "Config.in". If you need some tips on how to write these files, take a look here: package/sdl/
- 5] Modify Config.in according to the description of the "Toto" package:
- 6] Modify toto.mk
This Makefile contains several steps:
- software download
- untar the archive
- apply patches to the sources if necessary
- configure the sources
- build
- install in the rootfs
This makefile has to contain one target toto-clean to clean up the sources after a build and an other one toto-dirclean to remove the folder from the overall compilation process
Compilation test of the package
Try this:
$ make -C buildroot/ toto
If this command works, test your package on an Armadeus plateform. If it's ok you can jump to the next chapter and proceed with the integration into buildroot. Otherwise it is perhaps necessary to do some modifications of the sources/Makefile. Start by creating a new folder containing the package to modify:
$ cd buildroot/build_arm $ cp -Rf toto toto.org
Now perform the modifications in the toto directory until you get a running package. Once done, one or several patches will be probably required against the original sources:
$ diff -rup toto.org/fichier toto/fichier > ../package/toto/toto.0.patch
These patches will be applied by the toto.mk file. Save your work and check it:
$ mv toto toto.ok $ cd ../.. $ make -C buildroot/ toto
if it is ok, remove the directories buildroot/build_arm/toto.org and buildroot/build_arm/toto.ok which are now useless
Integration of the package into Buildroot
Once the package or the application successfully tested, add a reference to package/toto/Config.in.
$ cp buildroot/package/Config.in buildroot/package/Config.org
then perform the modifications in the Config.in and start buildroot menuconfig
$ make menuconfig
Select your package in the menu "package", save the configuration et retry the installation:
$ make toto-dirclean $ make
As soon as all is ok, you need to create the configuration patch for buildroot:( file buildroot/package/Config.in) with the same method as before
$ diff -rup buildroot/package/Config.org buildroot/package/Config.in > patches/numero_buildroot_nompaquet.diff
Add the new package to the Armadeus distro
All the files located in buildroot/package/toto and the patches (buildroot configuration) as well have to be added to SVN
$ svn add -N fichiers $ svn commit -m [BUILDROOT PACKAGE] Adding an usefull toto package files --non-interactive
And now check with a fresh developpement tree...