|
Hello all,
I've just upgraded one of my PC's to Hardy Heron (excellent, BTW), and I'm using this opportunity to reinstall and reorganize Buildroot. When I first installed Buildroot, I basically stuck with the defaults, changing only what I needed to in order to get everything to compile. Over time, it became increasingly difficult to keep my project organized. I started to gather changes to the Buildroot files, the linux kernel, the root filesystem, and U-boot, in addition to all of the custom programs and drivers I've written. My solution was to keep separate directories for each of these subsystems which contained only the changed and added files, and I would copy them into the Buildroot directory when I rebuilt everything. This has gotten rather cumbersome and difficult to manage, so I'm sure there's a better way.
Now that I have the chance to start over, I thought I'd solicit some input from others on the best way to keep everything nice and neat. So how does everyone else do it? How do you keep your custom kernel, root filesystem, toolchain, drivers, and applications organized so that it's easy to update, compile, and backup? Ideally, I hope to get enough input here to put an article up on the linux4sam.com wiki.
Cheers,
Alex
|