From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 01/14] Add a new "src" directory in the output directory
Date: Thu, 24 Jan 2013 20:19:18 +0100 [thread overview]
Message-ID: <51018936.8000706@mind.be> (raw)
In-Reply-To: <1663985.KsIK240cT1@sagittae>
On 01/21/13 06:38, J?r?me Pouiller wrote:
>> > +SRC_DIR:=$(BASE_DIR)/src
> IMHO, $(SRC_DIR) should be in $(TOPDIR) to be shared between different
> configurations. In add $(SRC_DIR) have to customizable in case I would like to
> clearly separate two projects.
>
> I think, my workspace would look like this:
> br/srcs-projet1
> br/srcs-projet2
> br/output-project1-configA
> br/output-project1-configB
> br/output-project2-configA
> br/output-project2-configB
>
> Finally SRC_DIR should be handled like DL_DIR.
I agree that that would be a good idea.
However, what if the patches are different for two configurations? They
can be different because:
- there is a configuration option for custom patches, like
BR2_LINUX_KERNEL_PATCH
- there are patches applied depending on configuration options, like
BR2_LINUX_KERNEL_EXT_XENOMAI_ADEOS_PATCH
- there are manual modifications applied depending on some configuration
option, like BZIP2_NOLARGEFILE_FIX_MAKEFILE
- override.mk appends to the FOO_PATCH variable
- BR2_EXTRA_PACKAGE_PATCH_DIRS (not committed yet,
http://patchwork.ozlabs.org/patch/204216/ )
So in practice, I'm afraid it's not feasible.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-01-24 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:25 [Buildroot] [RFC v1] Prototype implementation of per-package out of tree build Thomas Petazzoni
2013-01-20 20:25 ` [Buildroot] [RFC v1 01/14] Add a new "src" directory in the output directory Thomas Petazzoni
2013-01-21 5:38 ` Jérôme Pouiller
2013-01-24 19:19 ` Arnout Vandecappelle [this message]
2013-01-20 20:25 ` [Buildroot] [RFC v1 02/14] package infrastructure: move subdir support to autotools Thomas Petazzoni
2013-01-22 21:11 ` [Buildroot] [RFC v1] Prototype implementation of per-package out of tree build Avery Pennarun
-- strict thread matches above, loose matches on Subject: below --
2013-01-20 23:52 Thomas Petazzoni
2013-01-20 23:52 ` [Buildroot] [RFC v1 01/14] Add a new "src" directory in the output directory Thomas Petazzoni
2013-01-21 13:47 ` Jérôme Pouiller
2013-01-21 17:16 ` Thomas Petazzoni
2013-01-22 10:15 ` Jérôme Pouiller
2013-01-22 16:49 ` Thomas Petazzoni
2013-01-22 17:12 ` Jérôme Pouiller
2013-01-23 15:45 ` Thomas Petazzoni
2013-01-24 10:34 ` Jérôme Pouiller
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=51018936.8000706@mind.be \
--to=arnout@mind.be \
--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.