buildroot with ipkg
Quoted 2 lines · Bernhard Fischer
Don't forget about package/Makefile.autowhatever.in.
Done. also "modularized" the x11r7 tree. Pretty simple but it fails somewhere not realetd to my changes, so untested.
Quoted 6 lines
Yes. Not sure if that'd work, but perhaps something like
$(PROJECT_BUILD_DIR)/%/$(FOO_BINARY): $(TARGET_DIR)/$(FOO_BINARY) \ $(TARGET_PACKAGES_DIR)/$(FOO_BINARY): $(FOO_DIR)/.unpacked $(MAKE) -C $(FOO_DIR) et ceteramay do the trick. We'd have to see if something like that makes sense.
I have to admit that it did not for me. Probably just too much magic in it. It does look like you are both adding it to the target and the packages directory? I can't really see a test there.
Quoted 2 lines
$ svngrep -r ^TARGET_DIR:= /mnt/cvs/busybox/upstream/buildroot/ 2> /dev/null /mnt/cvs/busybox/upstream/buildroot/project/Makefile.in:TARGET_DIR:=$(PROJECT_BUILD_DIR)/root
Ok, red face then (forgot :=, looked for TARGET= )
New patch attached, this time against the latest trunk. It does build dropbear properly but the ipkg suport is not done, just .udeb / .deb and tarballs.
I'd also would like to do dependencies and package descriptions based on the packages Config.in but then the script has to know where every targets Config.in resides which isn't obvious unfortunately.
Patch was too big for the list so you can find it here:
http://www.zelow.no/floppyfw/download/Development/Patches/buildroot/packages.diff
Thomas.
Quoted 3 lines · Thomas Lundquist
I'd also would like to do dependencies and package descriptions based on the packages Config.in but then the script has to know where every targets Config.in resides which isn't obvious unfortunately.
Earlier today, i thought a little bit about that, too. This would certainly be a nice thing to have. We would create a make-includeable file, let's say .auto.deps, that is included after BASE_TARGETS are set, but before including any other stuff.
.auto.deps could look something like:
libpcap: $(BASE_TARGETS) zlib
tcpdump: $(BASE_TARGETS) libpcap
See r19978 and the log for it for further details and questions that arose.. (apart from my typo "thoughs welcome" which lack a "t" somewhere)
thoughts?
On Sun, Sep 23, 2007 at 10:43:17PM +0200, Bernhard Fischer wrote:
About time I commit something package related but I feel we have to agree.
Quoted 8 lines
Earlier today, i thought a little bit about that, too. This would certainly be a nice thing to have. We would create a make-includeable file, let's say .auto.deps, that is included after
BASE_TARGETSare set, but before including any other stuff..auto.deps could look something like:
libpcap: $(BASE_TARGETS) zlib
tcpdump: $(BASE_TARGETS) libpcap
This would then have to replace the SELECT and DEPENDS in Config.in. having it in two places is dangerous.
make *config could do the include or merging.
Quoted 3 lines
See r19978 and the log for it for further details and questions that arose.. (apart from my typo "thoughs welcome" which lack a "t" somewhere)
Have to admit I lost you there. Not sure what you meant.
For those wanting to read the comment:
http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi?rev=19978&view=rev
Anyway; any reason I should NOT add my packages patchset? I know it's not perfect but it's definately a start. the monkeywork of changeing all the FOO_DIR thingies in every .mk file is a valid reason not to but I'm willing to do it and I don't have a better solution for it.
Thomas.