From: Warren Young <wyml@etr-usa.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] Removing .la files from x86
Date: Wed, 03 Aug 2016 04:16:00 -0000 [thread overview]
Message-ID: <79640297-2DB1-4BC2-AAF7-600D8FAEB02D@etr-usa.com> (raw)
In-Reply-To: <c2b9aec9-fb94-7766-8e31-f5cce7ce9000@cygwin.com>
On Aug 2, 2016, at 9:09 PM, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
>
> Any objections?
This script would need to consult the same package database cygcheck uses to find out if an installed Cygwin package owns each *.la file it proposes to remove. It should not remove any other *.la file just because it happens to be in /usr/lib.
It should not remove anything in other common libdirs like /usr/local/lib. If I’ve installed something from source and its make install rule installs the *.la file, that’s an issue for the upstream provider.
Doesn’t libtool provide some of the magic library dependency chasing that exists on Linux but almost nowhere else?
That is, if library B depends on library C, and library A depends on B, on Linux you generally only need to explicitly link to library A, and the linker will chase down B and C for you. This doesn’t usually happen on other systems, so you may have to explicitly link to library B, and sometimes to library C as well.
A common practical example is that libpng depends on zlib, but it is sufficient on Linux to link only with -lpng, whereas porting such software to non-Linux systems generally requires appending -lz.
Would we still have that behavior on Windows without the .la files? If not, it’s possible that some build systems would break.
next prev parent reply other threads:[~2016-08-03 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 3:11 Yaakov Selkowitz
2016-08-03 4:16 ` Warren Young [this message]
2016-08-03 8:00 ` Corinna Vinschen
2016-08-03 9:19 ` Marco Atzeri
2016-08-03 15:58 ` Yaakov Selkowitz
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=79640297-2DB1-4BC2-AAF7-600D8FAEB02D@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).