From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] using a variable within a buildroot menuconfig
Date: Tue, 25 Jun 2013 19:39:17 +0200 [thread overview]
Message-ID: <51C9D5C5.4090409@mind.be> (raw)
In-Reply-To: <51C94D88.5080707@gmail.com>
On 25/06/13 09:58, Jan Pohanka wrote:
> Hi all,
>
> 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'm afraid that I don't understand your question. string type
configuration variables can contain any kind of string, including paths
of files. This is used for instance in BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.
Specifically for ffmpeg, however, there is already the
BR2_PACKAGE_FFMPEG_EXTRACONF option. You can just set that to
--extra-cflags '-fPIC -DMY_DEFINE' (note the funky quoting, which I'm not
100% sure will work correctly).
> 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 wonder what you mean with the TI SDK. You probably mean you have to
use _some packages_ that are in the 700MB self-extractor, right? Because
the SDK itself is in fact a replacement for buildroot (or buildroot is a
replacement for the SDK, depending on how you want to look at it :-).
Getting that stuff to work is absolute horror, I can testify. I did
that a year and a half ago for the DM365 multimedia codecs, but I never
found a reasonable solution to extract and build individual packages.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-06-25 17:39 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 [this message]
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
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=51C9D5C5.4090409@mind.be \
--to=arnout@mind.be \
--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.