From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Makefile: don't recreate staging symlink if it exists
Date: Tue, 18 Feb 2020 19:44:18 +0100 [thread overview]
Message-ID: <20200218194418.5f38002b@windsurf> (raw)
In-Reply-To: <CAAXf6LWzJA5tnAXs3KMPip77men=bjgRYKf_KOUizrjP4WHkPg@mail.gmail.com>
On Tue, 18 Feb 2020 18:59:49 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> > The question that comes to mind is: why are you building something
> > against the Buildroot toolchain/sysroot, before the Buildroot build has
> > completed ?
>
> No, the initial Buildroot build _is_ completed first. Then the
> application build starts according to the scenario described.
> In our case, the extra Buildroot 'make' is done to let Buildroot
> create the images, passing a custom TARGET_DIR which is an extended
> copy of the original output/target. This step happens multiple times
> for different boards, out of the same Buildroot (the boards differ a
> bit in our own software plus perhaps some other customization done in
> the rootfs). From the perspective of the application build, the fact
> that Buildroot 'make' is called shouldn't matter because all the files
> it needs will not be touched. Buildroot itself is also retained as-is,
> except it is asked to produce images.
Ah, ok. Convoluted use case, but OK. Anyway, the change makes sense, so
we'll apply. Thanks for the additional explanation!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-18 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:00 [Buildroot] [PATCH 1/2] Makefile: use HOST_DIR_SYMLINK instead of hardcoding Thomas De Schampheleire
2020-02-18 15:01 ` [Buildroot] [PATCH 2/2] Makefile: don't recreate staging symlink if it exists Thomas De Schampheleire
2020-02-18 15:40 ` Thomas Petazzoni
2020-02-18 17:59 ` Thomas De Schampheleire
2020-02-18 18:44 ` Thomas Petazzoni [this message]
2020-02-19 19:15 ` [Buildroot] [PATCH 1/2] Makefile: use HOST_DIR_SYMLINK instead of hardcoding 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=20200218194418.5f38002b@windsurf \
--to=thomas.petazzoni@bootlin.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.