From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/libtool: Reduce target package to libltdl only
Date: Mon, 26 Nov 2018 11:18:22 +0100 [thread overview]
Message-ID: <20181126111822.053c42a5@windsurf> (raw)
In-Reply-To: <b4e54580-453f-e184-4c82-531ed56cca8b@mind.be>
Hello,
On Mon, 26 Nov 2018 11:12:42 +0100, Arnout Vandecappelle wrote:
> On second thought, maybe we should just remove the automatic inheritance for
> _SUBDIR entirely.
>
> There are 15 host packages that set _SUBDIR.
>
> Of these, 6 are host-only (e.g. gcc) so the automatic inheritance is pointless.
>
> Of the remaining 9:
> - 2 override only HOST_XXX_SUBDIR (asterisk, cxxtest).
> - 1 has a different SUBDIR for host and target (gettext).
> - 1 overrides HOST_XXX_SUBDIR back to its default (gdb).
> - 1 defines both with the same value (icu).
> - 4 actually use the inheritance (capnproto, libnspr, tcl, vim).
>
> So it hardly seems worth to have the automatic inheritance, if only 1/3 of its
> occurences are actually useful.
Dropping the automatic inheritance of _SUBDIR is fine with me.
However, while we are talking about _SUBDIR, what about making progress
on the discussion we had related to
https://patchwork.ozlabs.org/project/buildroot/list/?series=70199 ? :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-26 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 16:54 [Buildroot] [PATCH v2] package/libtool: Reduce target package to libltdl only Alexander Sverdlin
2018-11-24 18:47 ` Yann E. MORIN
2018-11-24 19:06 ` Alexander Sverdlin
2018-11-24 21:03 ` Alexander Sverdlin
2018-11-24 19:24 ` Alexander Sverdlin
2018-11-26 9:28 ` Arnout Vandecappelle
2018-11-26 9:38 ` Alexander Sverdlin
2018-11-26 10:12 ` Arnout Vandecappelle
2018-11-26 10:18 ` Thomas Petazzoni [this message]
2018-12-03 7:25 ` Peter Korsgaard
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=20181126111822.053c42a5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox