Testing #67
closed
Split subprojects from bui project, push to new modules in CVS tree
100%
Description
The current metabuild orientation of bui is not conducive to use with Buildroot-based metabuilds. Therefore, each of the subprojects needs to be broken out into its own CVS projects and have their own release cycles.
Makes sense. That's how Matchbox did it and now you can see a very practical reason why it should still be that way.
Related issues
Updated by Hammel about 14 years ago
All o the subprojects have been pulled from the bui metabuild and placed into their own CVS trees and a release made for each (0.1.0 for each).
Next step is to make the bui build pull each of them down and build them to verify they still build okay.
Then verify they build in a cross-compiler environment using beaglebox's xcc to make sure they can be compiled that way. May need to fix up bui metabuild to pass in --host/--build/--target options to configure for each subproject. This is in prep for integrating them into the beaglebox build as a single buildroot package.
Updated by Hammel almost 14 years ago
All of the individual projects have been tested within the Buildroot rootfs build for BeagleBox. However, they have not been fully integrated into the bui metabuild yet.
Updated by Hammel almost 14 years ago
The metabuild now builds all the separated out projects by retrieving the release packages for each.