From: john <john.osullivan@cloudiumsystems.com>
To: buildroot@busybox.net
Subject: [Buildroot] Environment Variables and CMAKE
Date: Wed, 22 May 2013 17:21:55 +0100 [thread overview]
Message-ID: <1369239715.2814.31.camel@john-ubu> (raw)
Hi,
I have a cmake based project which I am trying to incorporate into
buildroot-2012.05
As part of the configuration of the code I need to pass it an
environment variable $(CLIENT_VER) which I generate at the time of
building in the source directory (which I check out of SVN).
I have tried various approaches without success.
This is my mk file
#I first tried this approach by generating the cmake configuration
#command with a script and then executing that script
#but the problem here was I would need to know the location of the
#buildroot generated version of cmake and the toolchain file
#I could figure these out in the script but I felt there must be a
#simpler approach
#define CLIENT_BARROW_CONFIGURE_CMDS
# (cd $(CLIENT_BARROW_SRCDIR) && source set_environment.sh \
# && ./cmake_run \
# )
#endef
#then I tried this
define CLIENT_BARROW_SET_ENVIRONMENT
(source $(CLIENT_BARROW_SRCDIR)set_environment.sh \
&& echo "Running Pre Configure Hook " \
)
endef
CLIENT_BARROW_PRE_CONFIGURE_HOOKS = CLIENT_BARROW_SET_ENVIRONMENT
CLIENT_BARROW_VERSION = HEAD
CLIENT_BARROW_SITE = svn://cloudiumserver3/topaz/trunk/client_barrow
CLIENT_BARROW_INSTALL_STAGING = YES
CLIENT_BARROW_CONF_OPT = -DWITH_XV=OFF -DCLIENT_VER_STR=$(CLIENT_VER)
$(eval $(call CMAKETARGETS))
My basic question is this:
Is there someway to pickup an environment variable in the process that
processes the .mk file?
next reply other threads:[~2013-05-22 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 16:21 john [this message]
2013-05-24 16:51 ` [Buildroot] Environment Variables and CMAKE Arnout Vandecappelle
2013-05-26 12:16 ` Samuel Martin
2013-05-27 9:49 ` john
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=1369239715.2814.31.camel@john-ubu \
--to=john.osullivan@cloudiumsystems.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