From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion, move TARGET_DIR
Date: Sun, 5 Nov 2006 13:05:46 +0100 [thread overview]
Message-ID: <20061105120546.GB14530@zelow.no> (raw)
Hello again.
I have always felt that TARGET_DIR was kinda misplaced. build_<ARCH> is
for the source and staging (well, maybe not even staging).
so, what about making target_<ARCH> instead?
I am working on autonomous packages (choose between making a pcakage a
part of the root file system or an autonomous tarball) and I am using
TARGET_PKG_DIR for that. right now it's build_<ARCH>/packages.
but target_<ARCH>/root and target_<ARCH>/packages seems more right to
me.
but foloowing this logic would make us have to sed thorugh the whole
tree to change TARGET_DIR to TARGET_ROOT_DIR but that ain't exactly
difficult to do. (I can make a patch for it).
anyone with anything to say which likes it and will help getting the
patches in?
Thomas.
next reply other threads:[~2006-11-05 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 12:05 Thomas Lundquist [this message]
2006-11-06 7:22 ` [Buildroot] Suggestion, move TARGET_DIR Ulf Samuelsson
2006-11-06 9:50 ` Thomas Lundquist
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 19:57 Ulf Samuelsson
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=20061105120546.GB14530@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