Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/Makefile.in: export O= to post-build/image scripts for out-of-tree builds
Date: Mon, 17 Jul 2017 23:32:13 +0200	[thread overview]
Message-ID: <871spe92ci.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <7d2448b0-800c-cb14-657b-907d380787f8@mind.be> (Arnout Vandecappelle's message of "Mon, 17 Jul 2017 22:52:31 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 14-07-17 15:04, Peter Korsgaard wrote:
 >> Sometimes it can be interesting to call back into buildroot from a
 >> post-build/image script (E.G. make printvars or similar). For this to work
 >> correctly with out-of-tree builds we need to pass O= to make, but this is
 >> currently not available in the environment of post-build/image scripts.
 >> 
 >> In concept, O could be derrived from BUILD_DIR (E.G. by stripping /build),
 >> but directly exporting O is cleaner.
 >> 
 >> O= cannot be exported globally as it interferes with various build systems,
 >> so instead add it to EXTRA_ENV.

 >  I'm too late with this comment, but why is BASE_DIR not sufficient? It is
 > already exported, and it is set to:

 > BASE_DIR := $(CANONICAL_O)

Yes, that can also work - Even though it is less obvious that you should
run make O=${BASE_DIR} inside the post build/image scripts, instead of
make O=$O

 >  O has the problem that it's too risky to lead to conflicts IMO.

Even for post build/image scripts? What use cases do you have in mind
where there could be conflicts?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-07-17 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 13:04 [Buildroot] [PATCH] package/Makefile.in: export O= to post-build/image scripts for out-of-tree builds Peter Korsgaard
2017-07-14 21:53 ` Yann E. MORIN
2017-07-15  8:11 ` Thomas Petazzoni
2017-07-17 20:52 ` Arnout Vandecappelle
2017-07-17 21:32   ` Peter Korsgaard [this message]
2017-07-17 21:34     ` Arnout Vandecappelle
2017-07-18 12:47       ` Peter Korsgaard
2017-07-18 13:18         ` 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=871spe92ci.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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