From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] package/environment-setup: add configure alias
Date: Mon, 20 Apr 2020 23:52:27 +0200 [thread overview]
Message-ID: <20200420215228.16175-3-angelo@amarulasolutions.com> (raw)
In-Reply-To: <20200420215228.16175-1-angelo@amarulasolutions.com>
In order to simplify the usage of a buildroot toolchain within
the buildroot shell, a "configure" alias is provided to call
./configure with the correct flags.
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
docs/manual/using-buildroot-toolchain.txt | 4 ++--
package/environment-setup/environment-setup | 1 +
package/environment-setup/environment-setup.mk | 2 ++
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/docs/manual/using-buildroot-toolchain.txt b/docs/manual/using-buildroot-toolchain.txt
index 7b2de4bdfa..187ffd472b 100644
--- a/docs/manual/using-buildroot-toolchain.txt
+++ b/docs/manual/using-buildroot-toolchain.txt
@@ -31,8 +31,8 @@ For your convenience, by selecting the package BR2_PACKAGE_ENVIRONMENT_SETUP,
you can have a +setup-environment+ script installed in +output/host/+.
This script can be sourced with +. your/sdk/path/environment-setup+ to launch
the buildroot shell. Inside this shell, you will find an environment already
-set up with the correct PATH and the complete list of +target configure
-options+.
+set up with the correct PATH, the complete list of +target configure
+options+ and some useful commands.
Alternatively, if you just want to prepare the SDK without generating
the tarball (e.g. because you will just be moving the +host+ directory,
diff --git a/package/environment-setup/environment-setup b/package/environment-setup/environment-setup
index 8819e9f60a..20a6ffb3af 100644
--- a/package/environment-setup/environment-setup
+++ b/package/environment-setup/environment-setup
@@ -11,6 +11,7 @@ Some tips:
* PATH is now pointing to the HOST_DIR path
* Target configure options are already exported
* To configure do "./configure $CONFIGURE_FLAGS"
+* Alternatively use the alias "configure"
EOF
SDK_PATH=$(dirname "${BASH_SOURCE[0]}")
diff --git a/package/environment-setup/environment-setup.mk b/package/environment-setup/environment-setup.mk
index fc74594459..bd74dcb2f4 100644
--- a/package/environment-setup/environment-setup.mk
+++ b/package/environment-setup/environment-setup.mk
@@ -21,6 +21,8 @@ define ENVIRONMENT_SETUP_INSTALL_TARGET_CMDS
--sysconfdir=/etc \
--localstatedir=/var \
--program-prefix=\"\n" >> $(ENVIRONMENT_SETUP_FILE)
+ printf "alias configure=\"./configure \$${CONFIGURE_FLAGS}\"\n" \
+ >> $(ENVIRONMENT_SETUP_FILE)
$(SED) $(ENVIRONMENT_SETUP_HOST_DIR_SED_EXP) $(ENVIRONMENT_SETUP_FILE)
printf "PS1=\"\[\e[32m\]buildroot-$(BR2_VERSION)\[\e[m\]:\[\e[34m\]\w\[\e[m\]\$$ \"\n" \
>> $(ENVIRONMENT_SETUP_FILE)
--
2.17.1
next prev parent reply other threads:[~2020-04-20 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 21:52 [Buildroot] [PATCH v3 0/3] Adding the buildroot shell Angelo Compagnucci
2020-04-20 21:52 ` [Buildroot] [PATCH v3 1/3] package/environment-setup: new package Angelo Compagnucci
2020-04-20 21:52 ` Angelo Compagnucci [this message]
2020-04-20 21:52 ` [Buildroot] [PATCH v3 3/3] package/environment-setup: add cmake alias Angelo Compagnucci
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=20200420215228.16175-3-angelo@amarulasolutions.com \
--to=angelo.compagnucci@gmail.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 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.