Whether you are writing an application from scratch or porting some existing code, there are a number of basic steps that should be followed.<\/p>\n
Determine which external libraries are required.<\/p>\n
If no external libraries are required, the GCC toolchain can be used to compile stand-alone C\/C++ applications. See C\/C++ Toolchain<\/a>. If your application does require an external library, try building it using bitbake if a recipe exists. This will install the library into the staging\/sysroot directory: Compiling and linking C\/C++ applications against external libraries is best accomplished by writing a BitBake recipe for your application and building it within the OpenEmbedded environment. Now that you have your application building, you will want to move it to the hardware platform and test it.<\/p>\n${OETREE}\/<\/code>build\/tmp\/sysroots\/mtcdt<\/code>. Headers and library files will be installed in the usr\/include<\/code> and usr\/lib<\/code> directories in the previously mentioned mtcdt sysroot area.<\/p>\nCFLAGS<\/code>, LDFLAGS<\/code> and other variables will all be appropriately set for cross-compiling and linking against other libraries previously built by BitBake. Refer to the Yocto BitBake documentation<\/a> and to Yocto Common Tasks documentation<\/a> for writing custom recipes.<\/p>\nRunning<\/h4>\n
\n
scp<\/code> the resulting package (and dependencies) to the device and install it using opkg<\/code>. Look for your package in ${OETREE}\/build\/tmp\/deploy\/ipk\/<\/code>.<\/li>\n<\/ul>\nReleasing<\/h4>\n