From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv2 3/7] Makefile, skeleton: move the host skeleton logic to host-skeleton package
Date: Sat, 25 Nov 2017 20:54:23 +0100 [thread overview]
Message-ID: <20171125205423.45d27e1e@windsurf.lan> (raw)
In-Reply-To: <20171125194650.3psruf7s2mhzjtgd@tarshish>
Hello,
On Sat, 25 Nov 2017 21:46:50 +0200, Baruch Siach wrote:
> Hi Thomas,
>
> On Fri, Nov 24, 2017 at 05:46:06PM +0100, Thomas Petazzoni wrote:
> > As part of the per-package SDK work, we want to avoid having logic
> > that installs files to the global HOST_DIR, and instead do it inside
> > packages. One thing that gets installed to the global HOST_DIR is the
> > minimal "skeleton" that we create in host:
> >
> > - the "usr" symbolic link for backward compatibility
> >
> > - the "lib" directory, and its lib64 or lib32 symbolic links
> >
> > This commit moves this logic to a new host-skeleton package, and makes
> > all packages (except itself) depend on it. We also make sure that this
> > host-skeleton package doesn't depend on host-patchelf, because
> > host-patchelf depends on host-skeleton.
>
> AFAICS, host-patchelf becomes a dependency of all packages only in patch #6.
> Maybe this last sentence should move there.
True. This patch originally was *after* the change of the RPATH
strategy, and I decided to move it earlier in t he patch series, hoping
that it could be merged earlier than the bigger/more controversial
changes.
I'll fix that in v3.
Thanks for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-25 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 16:46 [Buildroot] [RFCv2 0/7] Per-package SDK and target directories Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 1/7] pkgconf: use relative path to STAGING_DIR instead of absolute path Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 2/7] toolchain: post-pone evaluation of TOOLCHAIN_EXTERNAL_BIN Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 3/7] Makefile, skeleton: move the host skeleton logic to host-skeleton package Thomas Petazzoni
2017-11-25 19:46 ` Baruch Siach
2017-11-25 19:54 ` Thomas Petazzoni [this message]
2017-11-24 16:46 ` [Buildroot] [RFCv2 4/7] pkg-cmake: install CMake files as part of a package Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 5/7] pkg-generic: add .stamp_installed step Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 6/7] core: change host RPATH handling Thomas Petazzoni
2017-11-24 16:46 ` [Buildroot] [RFCv2 7/7] core: implement per-package SDK and target 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=20171125205423.45d27e1e@windsurf.lan \
--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