[Gumstix-users] New buildroot directory structure

[Craig H. <cr...@gu...>]

I just finished a mammoth effort to get all the gumstix stuff ported  
to the new buildroot directory structure (for some definition of  
"new").  I've got it all working now in http://svn.gumstix.com/ 
gumstix-buildroot/branches/projects/br2 and intend to merge onto the  
trunk ASAP.  I've tested the main bits of functionality by building a  
u-boot and root_fs and both seem to work (note that root_fs_arm_nofpu  
is now named rootfs.arm_nofpu.jffs2).

Other than that, everything's heavily moved around, and the buildroot  
itself now has a nice "make menuconfig" option for turning packages  
on and off and stuff.  Each package lives in its own separate  
directory, including .mk file, Config.in file for the config system,  
and patches (if any).  The top level structure now looks like:

.
|-- docs        [documentation]
|-- package     [.mk, Config.in and patches for all the packages  
which can be installed]
|-- target      [.mk, Config.in and patches for things specific to a  
particular target platform; linux is included in here for some reason]
|-- toolchain   [.mk, Config.in and patches for the cross-compiler  
tools (binutils, gcc, uClibc, etc)
|-- build_arm_nofpu   [stuff gets built in this directory, as before]
|    |-- staging_dir  [stuff is "installed" here for use on the build  
host]
|    `-- root         [stuff is "installed" here and will then become  
the root_fs for the target system]
`-- toolchain_build_arm_nofpu   [stuff gets built in this directory,  
as before]

If you're familiar with the old buildroot, this should be pretty easy  
to figure out, with the possible exception of the fine semantics of  
what goes in target vs package vs toolchain -- it seems somewhat  
arbitrary in places.

anyhoo, if some of the more adventurous among you would be willing to  
try out the new SVN branch and see if it is in fact working right  
(including any pet packages you might want to try out), please do so  
and let me know.

If nobody much complains that things are horribly broken in the next  
couple of days, I'll merge onto the trunk and update all the various  
wiki pages which talk about how the buildroot works.

Thanks,

C