From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Samuel Martin <s.martin49@gmail.com>,
Sen Hastings <sen@phobosdpl.com>,
buildroot <buildroot@buildroot.org>,
Norbert Lange <nolange79@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH v4 2/2] package/pkg-meson: use meson to build/install packages
Date: Tue, 26 Jul 2022 09:07:55 +0200 [thread overview]
Message-ID: <20220726090755.2ec1a4a8@windsurf> (raw)
In-Reply-To: <CADvTj4ob3JZmsB=jdW3kM4mTQ30jsDXWTOEG5FUG1b=vwfRB8g@mail.gmail.com>
On Tue, 26 Jul 2022 00:38:11 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> > I *think* this is wrong, at least in the classical autotools sense of
> > prefix vs. DESTDIR.
>
> This isn't really different from how we handle target/staging prefix+install.
It is completely different. Do you know the difference between prefix
and DESTDIR?
prefix is the path where the software will be located when executed.
DESTDIR is here to divert the installation.
For host packages, we use prefix=$(HOST_DIR) and no DESTDIR because the
software will be located in $(HOST_DIR) when executed.
For target packages, we use prefix=/usr and DESTDIR=$(TARGET_DIR) /
$(STAGING_DIR) because the software will be located in /usr when
executed on the target, but temporarily during the installation we need
the files to go in $(TARGET_DIR) or $(STAGING_DIR).
See also https://www.gnu.org/prep/standards/html_node/DESTDIR.html.
> > And you should drop --destdir $$(HOST_DIR) here.
>
> I recall this didn't work due to pkg-config file generation being prefix based
> which was resulting in pkg-config files being incompatible with per-package
> directories.
And this needs to be investigated since as explained above --prefix /
and --destdir $(HOST_DIR) is most likely incorrect for host packages.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 4:44 [Buildroot] [PATCH v4 1/2] support/misc/toolchainfile.cmake.in: don't set PKG_CONFIG_SYSROOT_DIR James Hilliard
2022-07-26 4:44 ` [Buildroot] [PATCH v4 2/2] package/pkg-meson: use meson to build/install packages James Hilliard
2022-07-26 6:25 ` Thomas Petazzoni via buildroot
2022-07-26 6:38 ` James Hilliard
2022-07-26 7:07 ` Thomas Petazzoni via buildroot [this message]
2022-07-26 17:26 ` James Hilliard
2022-07-26 17:34 ` Thomas Petazzoni via buildroot
2022-07-27 7:18 ` James Hilliard
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=20220726090755.2ec1a4a8@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=james.hilliard1@gmail.com \
--cc=nolange79@gmail.com \
--cc=s.martin49@gmail.com \
--cc=sen@phobosdpl.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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