Hi Peter,
On 20/02/2005, at 11:38 PM, Peter O'Gorman wrote:
|> Not at all a stupid question – I was going to ask the same thing (in
|> relation to the fontconfig2-dev packages). I understand that it forces
|> libraries/executables to link against a specific version of a library
|> (i.e. in the case of fontconfig2-dev) - is it possible to replicate
|> this behaviour using dynamic libraries? What are the pros/cons/issues?
When making static libraries for this kind of situation, it is probably a
good idea to nmedit them to make the symbols private external. This will
stop many multiple defitions errors/warnings. If a shared library is built
with the static one as part of the input, it would normally reexport all the
global symbols from the static lib, making the static lib's symbols private
external will stop that from happening.
OK, that's really good to know - I guess what I'd also like to know is when is this static library situation appropriate? To be honest, I'd rather build a full fontconfig2 2.2.9x package (dynamic libraries and all). Is there any reason I shouldn't?
-Tony
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
