From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New kernel source mode [Proposal]
Date: Tue, 15 Jan 2013 09:22:31 +0100 [thread overview]
Message-ID: <20130115092231.35fa854a@skate> (raw)
In-Reply-To: <772dc0cb-8f56-4bd5-8862-8c95ad4457a5@zimbra2.corp.accelance.fr>
Dear Jeremy Rosen,
On Tue, 15 Jan 2013 09:18:14 +0100 (CET), Jeremy Rosen wrote:
> > So, for each package, the source code is extracted in
> > output/sources/<pkg>-<version>/, and the build takes places in
> > output/build/<pkg>-<version>/ for target packages, and
> > output/build/host-<pkg>-<version>/ for host packages.
> >
>
> just a small detail but...
>
> could you consider building in output/build/target instead of directly int
> output/build/ for the target ?
Hum, why? Building in output/build/<pkgname>-<pkgversion>/ is already
what we do today.
> 1) the host/ part won't be hidden in the middle of all sorts of directories that are package specific
Hum? I didn't suggest a host/ part. My proposal, in terms of build
directories, do not change anything compared to what we have today:
output/build/host-foo-1.0/ for the host version of package foo
output/build/foo-1.0/ for the target version of package foo
That's what we do today.
> 2) it would avoid confusion in the case we somday include a utility named "host"
It would be:
output/build/host-host-4.2/
output/build/host-4.2/
But that's the same thing today. I am not sure there is an upstream
project called simply "host", so at this point, I don't see the need to
change the naming of those directories.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-15 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 1:12 [Buildroot] New kernel source mode [Proposal] Przemyslaw Wrzos
2013-01-15 7:51 ` Stephan Hoffmann
2013-01-17 6:25 ` Przemyslaw Wrzos
2013-01-17 6:27 ` Przemyslaw Wrzos
2013-01-18 1:10 ` Przemyslaw Wrzos
2013-01-18 8:14 ` Stephan Hoffmann
2013-01-21 0:23 ` Przemyslaw Wrzos
2013-01-15 7:55 ` Thomas Petazzoni
2013-01-15 8:18 ` Jeremy Rosen
2013-01-15 8:22 ` Thomas Petazzoni [this message]
2013-01-15 9:13 ` Jeremy Rosen
2013-01-15 9:24 ` Thomas Petazzoni
2013-01-15 9:27 ` Jeremy Rosen
2013-01-19 16:13 ` Arnout Vandecappelle
2013-01-17 6:59 ` Przemyslaw Wrzos
2013-01-15 18:23 ` Steve Calfee
2013-01-15 20:40 ` Peter Korsgaard
2013-01-19 16:16 ` Arnout Vandecappelle
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=20130115092231.35fa854a@skate \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.