Op Mon, 17 Jul 2006, schreef Jonas Maebe:
> There is no other way to properly support linking to external libraries,
> unless you use something like Mac OS X' frameworks (which does support
> transparent versioning and multi-version support, including name changes of
> individual libraries part of a framework even if they represent the same
> library version if you'd feel inclined to do that).
>
> That doesn't mean Mac OS X doesn't potentially have the same library problems
> though, since most open source based libraries are not distributed as a
> framework.
IMHO crap like *_config are only tricks used by C people used to work
around defficiencies in their toolchains. There simply should be no reason
why you want such complexity. A library has a name, you link to it by
name, basta.
If people start renaming libraries we make us resistant to library name
changes. Otherwise the compiler needs to support a_config for library x
and b_config for package and the end is loose.
Daniël
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
