amos blackman schrieb: > On Wed, Jul 24, 2002 at 09:51:20PM +0200, Götz Babin-Ebell wrote: > >>Amos Blackman schrieb: >> >>>i was just wondering if there was a simple way to generate all the >>>makefiles and supporting scripts such that they create differently named >>>libraries (eg. libcrypto-096d and libssl-096d), so that i can have an old >>>version and a new version coexist peacefully in my project's build tree. >> >>The usual way to have different versions of a library in the system is to >>store them in different install directories > > this doesn't work for me, because i need both to be a part of the same build;
Are you really shure you need that ?
> certain binaries link against the older version, others link against the
> newer, at runtime both need to be available. thus they need unique names.
Static or dynamic linking ?
With static linking you can do a
${CC} -o module1 module1.c -I openssl-096d/include -Lopenssl-096d/lib\
-lssl -lcrypto
${CC} -o module2 module1.c -I openssl-096c/include -Lopenssl-096c/lib\
-lssl -lcrypto
With dynamic linking you can use a wrapper script:
#!/bin/sh
LD_LIBRARY_PATH=openssl-096d/lib:$LD_LIBRARY_PATH
module1 ...
and
#!/bin/sh
LD_LIBRARY_PATH=openssl-096c/lib:$LD_LIBRARY_PATH
module2 ...
> i'll take you're response to mean that there isn't a more generic solution
> than my script, though, which i can live with. i was just wondering.
Your problem is usually solved the way I describe here...
Bye
Goetz
--
Goetz Babin-Ebell, TC TrustCenter AG, http://www.trustcenter.de
Sonninstr. 24-28, 20097 Hamburg, Germany
Tel.: +49-(0)40 80 80 26 -0, Fax: +49-(0)40 80 80 26 -126
smime.p7s
Description: S/MIME Cryptographic Signature
