From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion, move TARGET_DIR
Date: Mon, 6 Nov 2006 21:57:51 +0200 [thread overview]
Message-ID: <DQ6KSKMJS5g8.cLWMbj8T@mailout.dof.se> (raw)
>
> If you have, lets say, several ARM targets, it makes sense to have several "root"
> which you can rebuild without recompiling each package.
and both buld_<ARCH> and target_<ARCH> ends up as the same thing.
but if I understand you, you'd like target_<TARGET_NAME> or
target_<ARCH>_<TARGET_NAME> so we can build for more than one target?
=> Actually I'd like
target_<ARCH>/<TARGET_NAME>
and under that I'd
like to put all things
related to that target
including "root",
the generated file system(s)
the build for u-boot and
linux so I can have
several configurations.
Actually every package
which have their own
configuration file should
be in a target specific
directory, so maybe even
busybox.
build_<ARCH> should be used when you can use the same package for several targets.
/Ulf
> Also it would make sense to be able to generate binary rpm's for each package.
Landley mentioned dependencies but it shouldn't be that hard if we drop
that headache.
Thomas.
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
next reply other threads:[~2006-11-06 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 19:57 Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-05 12:05 [Buildroot] Suggestion, move TARGET_DIR Thomas Lundquist
2006-11-06 7:22 ` Ulf Samuelsson
2006-11-06 9:50 ` 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=DQ6KSKMJS5g8.cLWMbj8T@mailout.dof.se \
--to=ulfs@dof.se \
--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