Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@wanadoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] export ARCH and CROSS_COMPILE for the post build script
Date: Thu, 18 Oct 2012 17:31:20 +0200	[thread overview]
Message-ID: <508020C8.8000700@wanadoo.fr> (raw)
In-Reply-To: <20121018153822.58509c94@skate>

Le 18/10/2012 15:38, Thomas Petazzoni a ?crit :
> Dear Thierry Bultel,
>
> On Thu, 18 Oct 2012 08:17:31 +0200, Thierry Bultel wrote:
>
>> Could we make the export of PATH and CROSS_COMPILE to the post-build
>> script ?
>> This would be really useful for building an external user application
>> in one shot (and I need it in my case).
>>
>> eg something like this in the top Makefile:
>>
>> ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")
>>       @$(call MESSAGE,"Executing post-build script")
>> *ARCH=$(ARCH) CROSS_COMPILE=$(TARGET_CROSS)*
>> $(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
>> endif
>>
>> Of course this could be implemented as an option.
>>
>> What do you think about it ?
> Why don't you create a Buildroot package to build your external
> application? It sounds much more logical.

That was my very first idea.
But I wanted to keep the Buildroot tree unchanged.

And at the time I took the decision, I did not find out how
to make such a package be built after all the others.
So "post build" sounded appropriate.

> Thomas

  reply	other threads:[~2012-10-18 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  6:17 [Buildroot] export ARCH and CROSS_COMPILE for the post build script Thierry Bultel
2012-10-18 13:38 ` Thomas Petazzoni
2012-10-18 15:31   ` Thierry Bultel [this message]
2012-10-18 17:12     ` Thomas Petazzoni
2012-10-18 19:21       ` Thierry Bultel

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=508020C8.8000700@wanadoo.fr \
    --to=thierry.bultel@wanadoo.fr \
    --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