From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/3] package/environment-setup: add cmake alias
Date: Mon, 20 Apr 2020 23:52:28 +0200 [thread overview]
Message-ID: <20200420215228.16175-4-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 "cmake" alias is provided to call cmake
with the correct toolchain file and options.
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
package/environment-setup/environment-setup | 1 +
package/environment-setup/environment-setup.mk | 3 +++
2 files changed, 4 insertions(+)
diff --git a/package/environment-setup/environment-setup b/package/environment-setup/environment-setup
index 20a6ffb3af..66bb461e05 100644
--- a/package/environment-setup/environment-setup
+++ b/package/environment-setup/environment-setup
@@ -12,6 +12,7 @@ Some tips:
* Target configure options are already exported
* To configure do "./configure $CONFIGURE_FLAGS"
* Alternatively use the alias "configure"
+* A "cmake" alias is available
EOF
SDK_PATH=$(dirname "${BASH_SOURCE[0]}")
diff --git a/package/environment-setup/environment-setup.mk b/package/environment-setup/environment-setup.mk
index bd74dcb2f4..0f3c954b65 100644
--- a/package/environment-setup/environment-setup.mk
+++ b/package/environment-setup/environment-setup.mk
@@ -23,6 +23,9 @@ define ENVIRONMENT_SETUP_INSTALL_TARGET_CMDS
--program-prefix=\"\n" >> $(ENVIRONMENT_SETUP_FILE)
printf "alias configure=\"./configure \$${CONFIGURE_FLAGS}\"\n" \
>> $(ENVIRONMENT_SETUP_FILE)
+ printf "alias cmake=\"cmake \
+ -DCMAKE_TOOLCHAIN_FILE=$(HOST_DIR)/share/buildroot/toolchainfile.cmake \
+ -DCMAKE_INSTALL_PREFIX=/usr\"\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
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 ` [Buildroot] [PATCH v3 2/3] package/environment-setup: add configure alias Angelo Compagnucci
2020-04-20 21:52 ` Angelo Compagnucci [this message]
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-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox