BeagleBox: BUI reset


I've spent the past week or so trying to integrate my BUI releases into the Buildroot build for beaglebox.  My original intent was to use a metabuild of all of the packages I'd forked from matchbox so I'd only have one package to build in buildroot.  The metabuild would build based on locally saved copies of each package instead of external packages. The metabuild works fine when run by itself, but the config/build/install process under Buildroot is better served if each package has a separate release from the others.

Looking at how Matchbox is integrated into Buildroot I can see how they use a top level menu selection to enable other features.  But the features (re: packages) are individual configurations that download, configure, build and install each package separate from one another.  This makes sense since there are library packages that the others depend on and it's easier to simply make use of the existing autoconf features to reference the build tree for each package.  Also, selecting the top level matchbox entry forces build of a library and the window manager while the keyboard, panel and desktop are optional components.  In bui, there are no optional components so my configuration will be slightly different.  But at least the Matchbox setup offers an example of how to do this.

So I'm going to break out the packages of BUI into their own cvs projects and create separate releases for each.  The metabuild may go away – I haven't decided yet.  It's convenient for me in testing under qemu at the moment.  But if it does stay around it will have to convert to downloading and compiling packages instead of grabbing them locally – essentially the same format as the BeagleBox metabuild.  And if it's going to be like that, I may as well just integrate it into BeagleBox for testing purposes outside of Buildroot.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.