hi, > support for the buildroot. If you unpack the package using > 'make package/foo-prepare QUILT=1', it will apply all patches > of that package using quilt and disable the automatic rebuild. > You can use the regular quilt commands like push, pop, edit, > etc. as described in http://www.suse.de/~agruen/quilt.pdf > This has the advantage of allowing you to edit multiple > patches for one package without forcing you to use multiple > directories for that. > When you're done editing, 'make package/foo-update' will copy > the final patches back into the buildroot. > I prefer that solution over splitting source directory and > build directory, because it works for all packages without > any extra code for handling the autoconf stuff. When editing > files they have to be explicitly added using quilt add/edit, > so binary junk is always ignored.
Thomas already forwarded your quilt patch ;-) But I didn't spent time right now to take a look. The major problem in conjunction with Clearcase is that currently the source directory is removed during an rebuild. Because we would like to work directly on our packages out of ClearCase I see no need to use quilt in this case. It would make the stuff more complicated. But the option to disable the automatic rebuild would help (... quilt light). > > There is a second reason. I've patched also the buildroot > environment > > to build in "parallel" multiple hardware platforms (based > on the same > > target arch). Means you have unpacked/patched the sources > once but the > > build output and the root file systems exist in parallel. > This enables > > you to boot several different hardware boards through NFS > not leaving > > the build environment. Just by switching the .config you switch > > between the different board development. > Sounds interesting, maybe we could make this an optional > extension. It definitely shouldn't be enabled by default for > all packages, because when I tested it quite some time ago, I > found that quite a few packages didn't handle this properly. For sure. You are right. To suppport this option only for packages which define PKG_BUILD_DIR and PKG_SOURCE_DIR would be an option. It's definitly a big step forward if you don't have to recompile the whole Linux kernel (2.6) just to test certain configurations (target profiles). br/R _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
