In order to package your application and include it in the root filesystem image, you must write a BitBake recipe for it.<\/p>\n
When starting from scratch, it is easiest to learn by example from existing recipes.<\/p>\n
For software that uses autotools (.\/configure; make; make install), writing recipes can be very simple:<\/p>\n
DESCRIPTION = \"Hello World Recipe using autotools\"\r\nHOMEPAGE = \"http:\/\/www.multitech.net\/\"\r\nSECTION = \"console\/utils\"\r\nPRIORITY = \"optional\"\r\nLICENSE = \"GPL\"\r\nPR = \"r0\"\r\n\r\nSRC_URI = \"git:\/\/git.multitech.net\/helloworld-autotools.git;protocol=git;tag=1.0.0\"\r\nS = \"${WORKDIR}\/git\"\r\n\r\ninherit autotools<\/pre>\nSRC_URI<\/code> specifies the location to download the source from. It can take the form of any standard URL using http:\/\/, ftp:\/\/, etc. It can also fetch from SCM systems, such as git in the example above.<\/p>\nPR<\/code> is the package revision variable. Any time a recipe is updated that should require the package to be rebuilt, this variable should be incremented.<\/p>\ninherit autotools<\/code> brings in support for the package to be built using autotools, and thus no other instructions on how to compile and install the software are needed unless something needs to be customized.<\/p>\nS<\/code> is the source directory variable. This specifies where the source code will exist after it is fetched from SRC_URI and unpacked. The default value is ${WORKDIR}\/${PN}-${PV}<\/code>, where PN<\/code> is the package name and PV<\/code> is the package version. Both PN<\/code> and PV<\/code> are set by default using the filename of the recipe, where the filename has the format PN_PV.bb<\/code>.<\/p>\nExample HelloWorld recipe using a single source file<\/h5>\n
This example shows a simple case of building a helloworld.c file directly using the default compiler (gcc). Since it isn’t using autotools or make, we have to tell BitBake how to build it explicitly.<\/p>\n
DESCRIPTION = \"HelloWorld\"\r\nSECTION = \"examples\"\r\nLICENSE = \"GPL\"\r\n\r\nSRC_URI = \"file:\/\/helloworld.c\"\r\n\r\nS = \"${WORKDIR}\"\r\n\r\ndo_compile() {\r\n\t${CC} ${CFLAGS} ${LDFLAGS} helloworld.c -o helloworld\r\n}\r\n\r\ndo_install() {\r\n\tinstall -d ${D}${bindir}\r\n\tinstall -m 0755 helloworld ${D}${bindir}\r\n}<\/pre>\nIn this case, SRC_URI<\/code> specifies a file that must exist locally with the recipe. Since there is no code to download and unpack, we set S<\/code> to WORKDIR<\/code> since that is where helloworld.c will be copied to before it is built.<\/p>\nWORKDIR<\/code> is located at ${OETREE}\/build\/tmp\/work\/armv5te-corecdp-linux-gnueabi\/<package name and version><\/code> for most packages. If the package is machine-specific (rather than generic for the armv5te architecture), it may be located in the mtcdp-corecdp-linux-gnueabi or mt100eocg-corecdp-linux-gnueabi subdirectory depending on your hardware (this applies to kernel packages, images, etc).<\/p>\ndo_compile<\/code> defines how to compile the source. In this case, we just call gcc directly. If it isn’t defined, do_compile<\/code> runs make<\/code> in the source directory by default.<\/p>\ndo_install<\/code> defines how to install the application. This example runs install<\/code> to create a bin directory where the application will be copied to and then copies the application there with permissions set to 755.<\/p>\nD<\/code> is the destination directory where the application is installed to before it is packaged.<\/p>\n${bindir}<\/code> is the directory where most binary applications are installed, typically \/usr\/bin<\/code>.<\/p>\nFor more examples, see the Multi-Tech recipes in ${OETREE}\/openembedded\/recipes\/multitech<\/a> and the many OpenEmbedded recipes in ${OETREE}\/openembedded\/recipes<\/a>.<\/p>\nFor a more in-depth explanation of BitBake recipes, syntax, and variables, see the Writing a New Recipe\u00a0<\/a>at www.yactoproject.org<\/a>.<\/p>\n