Re: Testing for C library status at perl binding build time?

Replies are listed 'Best First'.
Re^2: Testing for C library status at perl binding build time? by dkg (Acolyte) on Dec 17, 2009 at 19:01 UTC
We're already using Devel::CheckLib, but it only checks for the existence of the library. I don't see a way to make it check the return value of a given function call when compiled against that library. Have i missed something from the Devel::CheckLib documentation?	[reply]
Re^3: Testing for C library status at perl binding build time? by Corion (Patriarch) on Dec 17, 2009 at 19:06 UTC
The current stable version (0.06) doesn't support this, but it seems that the current developer version, 0.699_001, supports supplying your own function body to be compiled and/or run. And as you're supposed to bundle Devel::CheckLib with your module anyway, using the developer version is just as good as using the stable version.	[reply]
Re^4: Testing for C library status at perl binding build time? by dkg (Acolyte) on Dec 17, 2009 at 23:25 UTC
yes, perfect! thanks for pointing out that change in Devel::CheckLib. I think we'll use 0.699; it tests and works fine for me to distinguish the different versions of libgcrypt across different installations.	[reply]