From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with ipkg
Date: Sun, 23 Sep 2007 22:43:17 +0200 [thread overview]
Message-ID: <20070923204317.GF20058@aon.at> (raw)
In-Reply-To: <20070922222827.GD711@zelow.no>
On Sun, Sep 23, 2007 at 12:28:27AM +0200, Thomas Lundquist wrote:
>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?
next prev parent reply other threads:[~2007-09-23 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 22:28 [Buildroot] buildroot with ipkg Thomas Lundquist
2007-09-23 20:43 ` Bernhard Fischer [this message]
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=20070923204317.GF20058@aon.at \
--to=rep.dot.nop@gmail.com \
--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