| 1 |
On Wednesday 03 August 2005 15:11, Danny van Dyk wrote: |
| 2 |
> Mike Frysinger schrieb: |
| 3 |
> | On Wednesday 03 August 2005 07:16 am, Martin Schlemmer wrote: |
| 4 |
> |>On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote: |
| 5 |
> |>>On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: |
| 6 |
> |> |
| 7 |
> |>Last time I checked, only --without-pic or --disable-static disable |
| 8 |
> |>compiling twice. |
| 9 |
> | |
| 10 |
> | my tests show that with libtool 1.5.18 --without-pic doesnt change |
| 11 |
> | anything ... obviously --disable-static changes things same as |
| 12 |
> | --disable-shared would :P |
| 13 |
> | |
| 14 |
> | maybe i just did it wrong ... i used imlib2-1.2.0 as a reference |
| 15 |
> | -mike |
| 16 |
> |
| 17 |
> According to libtool's source, it only compiles things twice if it |
| 18 |
> shall build 'old-libs' ($build_old_libs=yes) _and_ shared libraries. If |
| 19 |
> it builds 'libtool-libs' ($build_libtool_libs=yes) it uses the same |
| 20 |
> object files for both the static and the shared library. |
| 21 |
> |
| 22 |
> But I might be comletely wrong... libtool's internals are sometimes so |
| 23 |
> confusing :-/ |
| 24 |
|
| 25 |
It shouldn't, and I believe it doesn't. Static libraries should be built |
| 26 |
without -pic, and shared with. Of course static libraries with pic do |
| 27 |
work, but it is a suboptimal solution. (Unless you want to include said |
| 28 |
static library into a shared library). Just see a static library as |
| 29 |
nothing more or less than a system archive of object files that |
| 30 |
applications can include. |
| 31 |
|
| 32 |
Paul |
| 33 |
|
| 34 |
-- |
| 35 |
Paul de Vrieze |
| 36 |
Gentoo Developer |
| 37 |
Mail: pauldv@g.o |
| 38 |
Homepage: http://www.devrieze.net |
Archives