Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/rauc: fix host build with systemd
Date: Fri, 13 Nov 2020 14:33:02 +0100	[thread overview]
Message-ID: <20201113143302.4c3d87d6@windsurf.home> (raw)
In-Reply-To: <3e457876-5396-1982-2cbb-8ef04cf1e064@grinn-global.com>

Hello,

On Fri, 13 Nov 2020 14:28:01 +0100
Bartosz Bilas <b.bilas@grinn-global.com> wrote:

> ouch, I meant about HOST_DIR but I typed STAGING_DIR for some reason... 
> Shouldn't we pass the --prefix=/usr to configure and DESTDIR=$(HOST_DIR) 
> to make in that case?

No. --prefix= is where the software will be executed from, so from host
binaries it must be --prefix=$(HOST_DIR), and DESTDIR not used.

It is when you're cross-compiling that there is a difference between
where the software will be executed from (--prefix) and where you
install it after the build (DESTDIR). That's why when cross-compiling
you have --prefix=/usr, and DESTDIR=$(TARGET_DIR) or
DESTDIR=$(STAGING_DIR). This means "at runtime the software will be in
/usr, but for the installation please put it in TARGET_DIR/usr".

Does that make sense ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-11-13 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 12:26 [Buildroot] [PATCH] package/rauc: fix host build with systemd Bartosz Bilas
2020-11-13 13:08 ` Thomas Petazzoni
2020-11-13 13:28   ` Bartosz Bilas
2020-11-13 13:33     ` Thomas Petazzoni [this message]
2020-11-13 13:44       ` Bartosz Bilas

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=20201113143302.4c3d87d6@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox