This is the mail archive of the
mailing list for the Cygwin project.
Re: [RFC] disable static libraries?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 15 Mar 2012 23:55:38 -0400
- Subject: Re: [RFC] disable static libraries?
- References: <4F62B3E5.email@example.com>
- Reply-to: cygwin-apps at cygwin dot com
On Thu, Mar 15, 2012 at 10:30:45PM -0500, Yaakov (Cygwin/X) wrote:
>libtool, while very commonly used, is the only major build system which
>creates both shared and static versions of every library by default.
>With the notable exceptions of libiconv and gettext, which are used in
>winsup/utils, most of the time the only purpose static libraries serve
>is to lengthen build times and enlarge -devel packages.
>So my question is, do you think about adding --disable-static to the
>default configure flags in cygport, or is this better left to individual
>maintainers to (be encouraged to?) do this themselves?
I think it sounds like it's a good idea to make it the default.