From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9866] BASE_DIR usage
Date: Tue, 16 May 2017 17:36:38 +0000 [thread overview]
Message-ID: <bug-9866-163-N0HZ6ReKmw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9866-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9866
--- Comment #2 from Jean-pierre Cartal <jpcartal@free.fr> ---
Sorry, my explanation was not clear enough.
Let's try again ;-)
I have several build environments, some are using out-of-tree builds using the
-O option, others are using the default output location.
Now let's say I want to get the value of BR2_ARCH variable in the post image
shell script using the printvars target, I need to find the location of the
Makefile I should use.
My idea was to use the already available BASE_DIR variable as follow :
make -C ${BASE_DIR} printvars
This is working fine for out-of-tree environments, since the
${BASE_DIR}/Makefile file will point to the makefile wrapper.
However for default build environment, ${BASE_DIR} will point to the output
directory where there is no Makefile available.
For the time being I added a test in my script as follow :
#Out-of-tree build case
if [ ${BASE_DIR}/Makefile ] ; then
make -C ${BASE_DIR} printvars
# default build environment case.
else
make -C ${BASE_DIR}/../ printvars
fi;
So I had several questions :
1) Am I using the correct method to get the current build Makefile location ?
2) Wouldn't it be more consistent for ${BASE_DIR} to always point to a location
with the same content/structure for default and out-of-tree builds or maybe to
have another variable that would give access to current build Makefile location
?
Thanks for your help.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-05-16 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 13:31 [Buildroot] [Bug 9866] New: BASE_DIR usage bugzilla at busybox.net
2017-05-16 16:03 ` [Buildroot] [Bug 9866] " bugzilla at busybox.net
2017-05-16 17:36 ` bugzilla at busybox.net [this message]
2017-05-16 17:42 ` bugzilla at busybox.net
2017-05-16 19:02 ` bugzilla at busybox.net
2017-05-16 19:11 ` bugzilla at busybox.net
2017-05-16 19:42 ` bugzilla at busybox.net
2017-05-16 20:24 ` bugzilla at busybox.net
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=bug-9866-163-N0HZ6ReKmw@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.