Authors,

I have a problem with Crypt::SSLeay getting the path right to custom include directories to pick up the OpenSSL libraries and headers.

On most free/libre Unix environments, one finds the includes rooted under /usr or /usr/local at

  .../include/openssl/*.h

On Windows, one finds both include/ and lib/ underneath openssl/

  c:/openssl
  c:/openssl/include
  c:/openssl/lib

Solaris, or at least the sunfreetools site tends to do something different (e.g.):

  /opt/include
  /opt/openssl
  /opt/lib

That is, from the install directory, the lib and inc dirs are siblings. I've refactored Makefile.PL heavily over the past year making things work better, but I haven't been able to get this sorted out to arrive at a situation where it works for everybody. I have a number of tickets in the queue saying "Just do this, and then it will work me". Except that it will stop working for everyone else.

An additional wrinkle is that Makefile.PL generates a .h file that is included by XS, and the subdirectory paths have to be (or not) embedded in the #include directives.

Someone must have dealt with this before. Perhaps not with OpenSSL, but some other library where the include and lib directories are subdirs, or siblings, or subdirectories hanging off the standard lib and inc directories (for some definition of standard).

Can someone point me to a module that already does this, or point me to a recipe that works in all cases?

Thanks,
David

Reply via email to