From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with ipkg
Date: Sun, 23 Sep 2007 00:28:27 +0200 [thread overview]
Message-ID: <20070922222827.GD711@zelow.no> (raw)
On Wed, Sep 19, 2007 at 11:50:43PM +0200, Bernhard Fischer wrote:
>
> 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.
> 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 cetera
>
> may 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.
> $ 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.
next reply other threads:[~2007-09-22 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 22:28 Thomas Lundquist [this message]
2007-09-23 20:43 ` [Buildroot] buildroot with ipkg Bernhard Fischer
2007-11-14 10:12 ` Thomas Lundquist
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 12:09 pasteur
2007-09-17 19:44 ` Julien Boibessot
2007-09-17 20:14 ` Erik Andersen
2007-09-17 21:17 ` Julien Boibessot
2007-09-19 6:42 ` Thomas Lundquist
2007-09-19 12:17 ` Thomas Lundquist
2007-09-19 19:27 ` Bernhard Fischer
2007-09-19 20:56 ` Thomas Lundquist
2007-09-19 21:50 ` Bernhard Fischer
2007-09-20 21:16 ` Julien Boibessot
2007-09-20 21:37 ` Thomas Lundquist
2007-09-22 21:28 ` julien.boibessot at free.fr
2007-09-22 21:43 ` Bernhard Fischer
2007-09-22 22:19 ` Thomas Lundquist
2007-09-20 9:06 ` Elizabeth Oldham
2007-09-20 10:52 ` Thomas Lundquist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070922222827.GD711@zelow.no \
--to=lists@zelow.no \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox