[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: zlib autoconf question
From: |
Eli Zaretskii |
Subject: |
Re: zlib autoconf question |
Date: |
Mon, 12 Aug 2013 18:19:16 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: Ulrich Mueller <address@hidden>, address@hidden, address@hidden
> Date: Mon, 12 Aug 2013 09:58:51 -0400
>
> > The real solution to such problems is to probe for the availability of
> > the shared library at run time.
>
> Or even better, to rely on an FFI (so not only you check availability
> at run-time, but you don't even need to have the library at
> compile-time).
That's similar to what the Windows port does with all the optional
libraries: the headers are required during the compilation, but the
libraries are not. They are loaded when needed, with the equivalents
of dlopen and dlsym.
- Re: zlib autoconf question, (continued)
- Re: zlib autoconf question, Ulrich Mueller, 2013/08/08
- Re: zlib autoconf question, Eli Zaretskii, 2013/08/11
- Re: zlib autoconf question, Stefan Monnier, 2013/08/12
- Re: zlib autoconf question, Stefan Monnier, 2013/08/12
- Re: zlib autoconf question,
Eli Zaretskii <=
- Re: zlib autoconf question, Stefan Monnier, 2013/08/12
- Re: zlib autoconf question, Lars Magne Ingebrigtsen, 2013/08/12
- Re: zlib autoconf question, Richard Stallman, 2013/08/12
- Re: zlib autoconf question, Lars Magne Ingebrigtsen, 2013/08/12
- Re: zlib autoconf question, Paul Eggert, 2013/08/12
- Re: zlib autoconf question, Dmitry Antipov, 2013/08/12
Re: zlib autoconf question, Jérémie Courrèges-Anglas, 2013/08/08