On Sun, 28 Jul 2013, Peter Stuge wrote:
libssh2 can be linked against openssl or gcrypt however, so my build
environment needs to know which one in order to trigger the proper
initialisation code and avoid unneeded dependencies.
The correct way to do this is through pkg-config. This is precisely the
problem that pkg-config solves.
Is it? How would you build your makefile / build scripts with pkg-config to
figure this out?
If libssh2 doesn't have a .pc file yet it needs to get one!
It has one.
But I could also imagine a run-time API so that an application can figure this
out on its own...
--
/ daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
