From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9866] New: BASE_DIR usage
Date: Tue, 16 May 2017 13:31:57 +0000 [thread overview]
Message-ID: <bug-9866-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9866
Bug ID: 9866
Summary: BASE_DIR usage
Product: buildroot
Version: 2017.02
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
I'm trying to use the printvars target from a post image shell script and I
would like this script to support both default output directory ie
buildroot/output as well as O= option.
Thus I'm calling the printvars target as follow :
make -C ${BASE_DIR} printvars
However this code will only work if O= option is used, since in this case the
BASE_DIR directory will contain the main Makefile.
Is there any variable that will contain the directory which contains the main
Makefile file ?
Wouldn't it be more coherent if the BASE_DIR would point to directories with
similar content without depending on O= option ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-05-16 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 13:31 bugzilla at busybox.net [this message]
2017-05-16 16:03 ` [Buildroot] [Bug 9866] BASE_DIR usage bugzilla at busybox.net
2017-05-16 17:36 ` bugzilla at busybox.net
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox