From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with ipkg
Date: Wed, 19 Sep 2007 23:50:43 +0200 [thread overview]
Message-ID: <20070919215043.GX20058@aon.at> (raw)
In-Reply-To: <20070919205603.GA16408@zelow.no>
On Wed, Sep 19, 2007 at 10:56:03PM +0200, Thomas Lundquist wrote:
>On Wed, Sep 19, 2007 at 09:27:40PM +0200, Bernhard Fischer wrote:
>> >Index: package/config/mconf.c
>> >===================================================================
>> >--- package/config/mconf.c (revision 18947)
>> >+++ package/config/mconf.c (working copy)
>> >@@ -165,7 +165,8 @@
>> > "Arrow keys navigate the menu. "
>> > "<Enter> selects submenus --->. "
>> > "Highlighted letters are hotkeys. "
>> >- "Pressing <Y> selectes a feature, while <N> will exclude a feature. "
>> >+ "Pressing <Y> selectes a feature, while <N> will exclude a feature, "
>> >+ "<M> will build a separate package. "
>> > "Press <Esc><Esc> to exit, <?> for Help, </> for Search. "
>> > "Legend: [*] feature is selected [ ] feature is excluded",
>> > radiolist_instructions[] =
>>
>> I'm not sure if that is a good idea. You'd generally want to build all
>> packages as ipkg, i'd say.
>
>I want the users to be able to choose. This is a very simple way for
>them to do so. I know I probably should find that bloody "m" and change
>it to a "p" and might do it.
m vs p doesn't make much difference.
>> >+ifeq ($(strip $(BR2_PACKAGE_DROPBEAR)),m)
>> >+DROPBEAR_DESTDIR=$(TARGET_PACKAGES_DIR)/dropbear
>> >+else
>> >+DROPBEAR_DESTDIR=$(TARGET_DIR)
>> >+endif
>>
>> wow. This would be very intrusive.
>
>but very simple.
Don't forget about package/Makefile.autowhatever.in.
This needs adjustment too.
(and whoever hard-coded x11 specific stuff in there should be beaten)
>> We should be able to use one central
>> TARGET_PACKAGES_DIR that may or may not be empty that we stick into the
>> individual FOO_DIR's via TARGET_DIR
>
>Not sure I follofw you completely but you mean make sure that TARGET_DIR
>changes for every make file dependant on the package/base option set in
>.config?
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.
>Be my guest but I've already volunteered to do the changes to the .mk
>files to make my method work.
Yes, but somebody has to maintain it and explain it :)
>
>BTW; I been away from buildroot for way too long. I just can't find out
>where or how TARGET_DIR is defined. Anyone able to enoughten me? grep is
>usually a very good toy but it didn't make me any brighter this time.
$ 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
>> Still, creating ipkg would be a nice thing to have.
>
>And here is a patch that whould do this (and .deb, and .rpm or whatever
>people want or need.) together with someone wanting to add it and do the
>monkey work.
yeah. I'll reread the dropbear example tomorrow. Perhaps somebody else
has other comments.
Cheers,
next prev parent reply other threads:[~2007-09-19 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 12:09 [Buildroot] buildroot with ipkg 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-09-22 22:28 Thomas Lundquist
2007-09-23 20:43 ` Bernhard Fischer
2007-11-14 10:12 ` 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=20070919215043.GX20058@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