Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Salvatore Albano <info@daccii.it>
To: buildroot@busybox.net
Subject: [Buildroot] linux: why is vmlinux only available for mips?
Date: Fri, 15 Jul 2011 11:46:00 +0200	[thread overview]
Message-ID: <4E200C58.4050401@daccii.it> (raw)
In-Reply-To: <CAAXf6LXwcpiXfJF26ABizR5y3KuJ2OCVHSyyhQePzxCeG-H6bg@mail.gmail.com>

Il 15/07/2011 11:34, Thomas De Schampheleire ha scritto:
> This works fine in the context of buildroot. However, I need to access
> these files from a non-buildroot context (external makefiles/scripts)
> and so the variable BR2_LINUX_KERNEL_VERSION is not known.
>
> Thomas

If you're using *sh scripts, you can just do something like
. /PATH/TO/BUILDROOT/.config

to access buildroot config variables so you can use that variable

If you're using make file i don't know, but there is a way to do it too, 
sure :)

In the end, if you're using anithing else you can try to parse using 
regular expressions (needs delimiters and/or backslashes around quotes)
BR2_LINUX_KERNEL_VERSION="?([a-zA-Z0-9\.\-]+)"?

or cat, grep and cut
cat .config | grep BR2_LINUX_KERNEL_VERSION | cut -d"\"" -f2


Best Regards,
Daniele

-- 
____________________________________________________________
                                         |
Daniele Salvatore Albano                | web site:
  IT Consultant                          | http://www.itechcon.it
  Webapps Design and Development         |
  Software Engineer and Developer        | e-mail:
  Linux Servers SetUp And Administration | info at itechcon.it
  Embedded Network Solutions             | d.albano at itechcon.it

Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in 
questo messaggio sono riservate ed a uso esclusivo del destinatario. 
Qualora il messaggio in parola Le fosse pervenuto per errore, La 
invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, 
dandocene gentilmente comunicazione. Grazie.
Pursuant to Legislative Decree No. 196/2003, you are hereby informed 
that this message contains confidential information intended only for 
the use of the addressee. If you are not the addressee, and have 
received this message by mistake, please delete it and immediately 
notify us. You may not copy or disseminate this message to anyone. Thank 
you.

  parent reply	other threads:[~2011-07-15  9:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  6:20 [Buildroot] linux: why is vmlinux only available for mips? Thomas De Schampheleire
2011-07-15  6:34 ` Thomas De Schampheleire
2011-07-15  9:22   ` Yann E. MORIN
2011-07-15  9:34     ` Thomas De Schampheleire
2011-07-15  9:38       ` Peter Korsgaard
2011-07-15 11:53         ` Thomas De Schampheleire
2011-07-15  9:46       ` Daniele Salvatore Albano [this message]
2011-07-15 11:55         ` Thomas De Schampheleire
2011-07-15 12:30   ` Thomas Petazzoni
2011-07-15 13:10     ` Yann E. MORIN
2011-07-20 13:38     ` Thomas De Schampheleire
2011-07-20 16:10       ` Quotient Remainder
2011-07-20 19:23         ` Thomas Petazzoni
2011-07-24 11:36         ` Thomas De Schampheleire
2011-07-26 10:38           ` Thomas De Schampheleire
2011-07-20 16:17       ` Thomas Petazzoni
2011-07-24 11:46         ` Thomas De Schampheleire
2011-07-25  7:05           ` Thomas Petazzoni
2011-07-25  8:34             ` Thomas De Schampheleire

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=4E200C58.4050401@daccii.it \
    --to=info@daccii.it \
    --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