Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR variable that points the built kernel
Date: Wed, 10 Jun 2015 10:36:06 +0200	[thread overview]
Message-ID: <20150610103606.31b56e0b@free-electrons.com> (raw)
In-Reply-To: <CAFRxoJ=O5=UvmRJPu3+qn2zVu6dniym7qTAdvWSWMf9Dpozk0Q@mail.gmail.com>

Dear Marco Pastorelli,

On Wed, 10 Jun 2015 10:29:16 +0200, Marco Pastorelli wrote:

> You're right, is there a way to use make variables inside the post-build
> script? Or this is a wrong approach?

Some of the make variables are passed in the environment of post build
script, but clearly not all of them. Especially the <pkg>_DIR variable
for each packages is not passed.

You're probably trying to do something that should be done in a
different way. You should have a package installing whatever you need
from $(LINUX_DIR) to $(TARGET_DIR) rather than doing it from a
post-build script.

However, your provide so little details about what you're trying to do
that it's quite impossible to give a good advice.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-06-10  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 11:41 [Buildroot] BR variable that points the built kernel Marco Pastorelli
2015-06-09 12:03 ` Thomas Petazzoni
2015-06-09 13:58   ` Marco Pastorelli
2015-06-09 14:03     ` Thomas Petazzoni
2015-06-10  8:29       ` Marco Pastorelli
2015-06-10  8:36         ` Thomas Petazzoni [this message]
2015-06-10 10:06           ` Marco Pastorelli
2015-06-10 17:15             ` Yann E. MORIN
2015-06-12  6:28               ` Marco Pastorelli

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=20150610103606.31b56e0b@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox