From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] Delete all .la files?
Date: Mon, 28 Dec 2015 14:16:49 +0100 [thread overview]
Message-ID: <n5rco1$fn0$1@ger.gmane.org> (raw)
In-Reply-To: <CAJTo0LayEjj9moB9xgup=vB+C9Sn2-WX+s97UWRt9tg=HYFnag@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 23-12-15 om 22:41 schreef Burton, Ross:
> Hi,
>
> So I've just done an oe-core world build with my latest .la-killer class
> enabled (
> https://github.com/rossburton/meta-ross/blob/master/classes/wipe-la.bbclass)
>
>
and the results are pretty good. Basically this class hooks onto
> do_install and simply deletes every *.la file it can find in ${D}, with
> an opt-out if required. .la files can cause rebuild problems if
> directories move around and are mostly pointless on Linux anyway, so they
> can just be deleted.
>
> One recipe (opensp-native) needs to opt out of the .la deletion as
> openjade-native for <redacted> reasons explicitly expects .la files to
> be installed. Some other desktop distros already strip out .la files so
> I wouldn't be surprised if there's a patch floating around to solve
> this.
>
> One recipe fails to build (gcc-sanitizers) as it expects to have built
> its own libstdc++ so the recipe just deletes the source and drops in
> symlinks to the libraries in the sysroot. Works, but is nasty. I could
> either opt gcc out of la removal, or improve the fixup to make it
> actually link to the installed libraries. Or, merge the sanitisers into
> the main gcc recipe, as I can't recall why they're separate anyway.
>
> Apart from that, my world build was successful.
>
> So in the new year I plan on submitting a renamed version of this class
> to oe-core and adding it to INHERIT_DISTRO. Any comments?
Go ahead, .la files need to go away in the OE world. I wish your class had
an option to kill them with fire, but alas.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFWgTZAMkyGM64RGpERAph9AJ0Tdmw9r3WW5OrQv6FTUGdh6zOiIwCcCyuu
9CHG+z9GGf7hW4GkdaRchZU=
=l+7i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-28 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 21:41 [RFC] Delete all .la files? Burton, Ross
2015-12-23 21:41 ` Burton, Ross
2015-12-23 22:49 ` Phil Blundell
2015-12-24 9:09 ` [OE-core] " Burton, Ross
2015-12-24 9:09 ` Burton, Ross
2015-12-29 11:21 ` Phil Blundell
2016-01-02 21:01 ` [OE-core] " Burton, Ross
2016-01-02 21:01 ` Burton, Ross
2015-12-28 13:16 ` Koen Kooi [this message]
2016-01-04 8:48 ` Clemens Lang
2016-01-04 16:50 ` [OE-core] " Burton, Ross
2016-01-04 16:50 ` Burton, Ross
2016-01-04 17:28 ` Burton, Ross
2016-01-04 17:28 ` Burton, Ross
2016-01-04 18:01 ` Christopher Larson
2016-01-04 18:01 ` [oe] " Christopher Larson
2016-01-04 19:01 ` Phil Blundell
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='n5rco1$fn0$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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.