From: Brian G. <gerkey@AI.SRI.COM> - 2006-03-18 00:54:07
|
hi, I'd like to make some changes to files that go into the rootfs, such as /etc/network/interface and /etc/modules. My technique so far has been to edit the files in target/generic/target_skeleton, cp them to build_arm_nofpu/root, rm rootfs.arm_nofpu.jffs2, then make. The resulting .jffs2 has my changes. This is obviously pretty roundabout. It looks like the tree in build_arm_nofpu/root is built by unpacking target/generic/ skel.tar.gz, but I don't see a step anywhere for (re)building that tarball (which is itself checked into SVN). How can I trigger a rebuild of that tarball to include my changes? I'd like to also be able to add files to that tarball. thanks, brian. -- Brian P. Gerkey ge...@ai... SRI AI Center http://leek.ai.sri.com/~gerkey |
From: Dave H. <dhy...@gm...> - 2006-03-18 01:49:18
|
Hi Brian, > I'd like to make some changes to files that go into the rootfs, such > as /etc/network/interface and /etc/modules. My technique so far has > been to edit the files in target/generic/target_skeleton, cp them to > build_arm_nofpu/root, rm rootfs.arm_nofpu.jffs2, then make. The > resulting .jffs2 has my changes. Actually, what I'd like to see is the ability to have a custom makefile, that we can provide in some directory. If the custom makefile doesn't exist, then it won't call it, and if it does exist, it would be called at various stages throughout the build process. So, some likely spots to have custom rules, are just after unpacking skel, just after copying linux.confg but before running oldconfig, just after copying in busybox config but before building, etc. This would allow people to apply their own custom patches, or whatever, without having to redo everything whenever a new build comes out. For your particular case, you could just make a custom package, and build it after building the buildroot. Make your custom package modify the appropriate files, and probably delete the .jffs2 file so that it gets regenerated. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@gu...> - 2006-03-18 19:00:15
|
On Mar 17, 2006, at 4:54 PM, Brian Gerkey wrote: > hi, > > I'd like to make some changes to files that go into the rootfs, > such as /etc/network/interface and /etc/modules. My technique so > far has been to edit the files in target/generic/target_skeleton, > cp them to build_arm_nofpu/root, rm rootfs.arm_nofpu.jffs2, then > make. The resulting .jffs2 has my changes. > > This is obviously pretty roundabout. It looks like the tree in > build_arm_nofpu/root is built by unpacking target/generic/ > skel.tar.gz, but I don't see a step anywhere for (re)building that > tarball (which is itself checked into SVN). How can I trigger a > rebuild of that tarball to include my changes? I'd like to also be > able to add files to that tarball. The build process actually unballs that tarball, and then afterwards copies the files from the target_skeleton directory over the top of the tarball contents. I think the idea is that the tarball would contain any special files and such, plus maybe directories; I'm not entirely sure what all is in the tarball. The target_skeleton is where I normally make changes of the type you're describing. The makefile which copies the contents of that directory though don't have any sensible way of determining though if the build_arm_nofpu/ root is out of date relative to the target_skeleton directory -- so after the initial copy over, it won't notice any modifications you've made, and won't over-copy stuff in the target directory. You can always force it to re-copy everything by just nuking build_arm_nofpu/ root then doing a "make" again -- this is what I normally do. C |
From: Craig H. <cr...@gu...> - 2006-03-18 19:01:10
|
On Mar 17, 2006, at 5:49 PM, Dave Hylands wrote: > Hi Brian, > >> I'd like to make some changes to files that go into the rootfs, such >> as /etc/network/interface and /etc/modules. My technique so far has >> been to edit the files in target/generic/target_skeleton, cp them to >> build_arm_nofpu/root, rm rootfs.arm_nofpu.jffs2, then make. The >> resulting .jffs2 has my changes. > > Actually, what I'd like to see is the ability to have a custom > makefile, that we can provide in some directory. If the custom > makefile doesn't exist, then it won't call it, and if it does exist, > it would be called at various stages throughout the build process. > > So, some likely spots to have custom rules, are just after unpacking > skel, just after copying linux.confg but before running oldconfig, > just after copying in busybox config but before building, etc. Patches happily accepted :) C |
From: Dave H. <dhy...@gm...> - 2006-03-19 04:50:31
|
Hi Craig, > > So, some likely spots to have custom rules, are just after unpacking > > skel, just after copying linux.confg but before running oldconfig, > > just after copying in busybox config but before building, etc. > > Patches happily accepted :) Somehow I expected that :) -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |