On Mon, 21 May 2012, Werner LEMBERG wrote:
The question is what happens for static linking. For example, in the
FreeType case, I get the following:
> pkg-config --libs --static freetype2
-L/usr/local/lib -lfreetype -lz -lbz2
> pkg-config --libs freetype2
-L/usr/local/lib -lfreetype
If I
> I would therefore check in your configure script whether the *.la
> file you got from the --libtool option exists, and, if not, simply
> link directly with only the library you're using (-lfreetype, for
> instance) and assume everything will work.
OK.
> I would also encourage any library maint
>> Some foo-config scripts like freetype-config have an option
>>
>> --libtool
>>
>> to display the library's .la file. However, it is more and more
>> common that .la files get removed by distributions if installed in
>> /usr/lib, as you are certainly aware.
>
> What is this information used f
Werner LEMBERG writes:
> My question is how to handle this properly. Shall the logic to test for
> the existence of the .la in the foo-config file or in the configuration
> script which actually uses foo-config? And what exactly should be done
> if no .la file is available? I suppose it's best
On Sun, 20 May 2012, Werner LEMBERG wrote:
Some foo-config scripts like freetype-config have an option
--libtool
to display the library's .la file. However, it is more and more
common that .la files get removed by distributions if installed in
/usr/lib, as you are certainly aware.
What is
Some foo-config scripts like freetype-config have an option
--libtool
to display the library's .la file. However, it is more and more
common that .la files get removed by distributions if installed in
/usr/lib, as you are certainly aware.
My question is how to handle this properly. Shall th
