All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] using a variable within a buildroot menuconfig
Date: Tue, 25 Jun 2013 21:41:05 +0200	[thread overview]
Message-ID: <20130625214105.0419b326@skate> (raw)
In-Reply-To: <51C94D88.5080707@gmail.com>

Dear Jan Pohanka,

On Tue, 25 Jun 2013 09:58:00 +0200, Jan Pohanka wrote:

> I have another /weird/ question.
> 
> I would like to know if it is possible to create an item in 
> configuration which will for example contain some (absolute) path on my 
> filesystem. Then I would like to use this variable for example in 
> --extra-cflags configure option for applications like ffmpeg etc.
> 
> I know that it is not very nice way, but I need to integrate buildroot 
> with Texas Instruments SDK, which is not very GNU build tools friendy.

I'm not sure to really understand what you want to do here. You can
always create string options:

config BR2_SOME_PATH
	string
	default "/path/to/somewhere/"

and then in some .mk file, you can use:

	$(BR2_SOME_PATH)

to refer to still variable, or:

	$(call qstrip,$(BR2_SOME_PATH))

if you want to get rid of the quotes around the variable value.

Does this answer your questions?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-06-25 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  7:58 [Buildroot] using a variable within a buildroot menuconfig Jan Pohanka
2013-06-25 17:39 ` Arnout Vandecappelle
2013-06-27 12:25   ` Peter Korsgaard
2013-06-29 13:42     ` Danomi Manchego
2013-06-29 13:44       ` Peter Korsgaard
2013-06-25 19:41 ` Thomas Petazzoni [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=20130625214105.0419b326@skate \
    --to=thomas.petazzoni@free-electrons.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.