On Thu, 6 Dec 2012, Gary Thomas wrote:
I think your problem stems from confusion about how recipes work. The build system centers around packaged sources, typically tarballs. These are then unpacked into the build "tmp" directory where the build will actually take place. Trying to use your extant directory will not work (or at least not work the way things are designed)
Ok, thanks for that Gary, I wasn't sure as there was an example I saw online that showed a file HelloWorld.c file being included in a recipe.
Can you try my rewritten version (attached)? First, you'll need to execute this step to build the tarball: % tar -zcf /home/aland/src/FLS.tar.gz -C /home/aland/src FLS Let me know what happens
This seems to have worked and installed successfully, and I'm building the image for the beaglebone now.
Is it at all possible to modify and/or change files to be included in the rootfs, or does everything need to be a recipe and/or package?
As an example, let's say I wanted to modify a config file in /etc/, and while we don't have one with our app, let's use /etc/fls.conf as an example. Can I edit and put that somewhere on the system so that it would be picked up and installed in the rootfs when the image is built?
-- Regards, Alan _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
