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: Tue, 18 Jul 2017 14:47:25 +0200	[thread overview]
Message-ID: <87wp757vz6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <dca9fa93-e6f8-10d9-f166-02f981b4f0a3@mind.be> (Arnout Vandecappelle's message of "Mon, 17 Jul 2017 23:34:01 +0200")

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

Hi,

 >> 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

 >  OK, but having both exported seems a bit silly...

Correct. I would argue that O is somewhat nicer than BASE_DIR, as the
user is already using O= (and if they don't use O=, then they also don't
need to pass it in post-build/post-image scripts), but we have exported
and documented BASE_DIR for some time now, so we cannot really get rid
of it.

 >> >  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?

 >  True, in EXTRA_ENV the risk is minimal - especially since Kbuild and
 > derivatives (like Buildroot) ignore an O passed through the environment.

Indeed.

I don't feel strongly pro/con, what do others say?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-07-18 12:47 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
2017-07-17 21:34     ` Arnout Vandecappelle
2017-07-18 12:47       ` Peter Korsgaard [this message]
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=87wp757vz6.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