Is it possibly to detect which OpenSSL is used for a port?

[list_freebsd at bluerosetech.com]

On 2015-03-20 14:49, Naram Qashat wrote:
> I've looked at bsd.openssl.mk and from what it says, those WITH_OPENSSL_*
> knobs are use-set, not port-set. So that doesn't help me.

I'm not sure what you read, but lines 5 through 10 of 
ports/Mk/bsd.openssl.mk are:

# Use of 'USE_OPENSSL=yes' includes this Makefile after bsd.ports.pre.mk
#
# the user/port can now set this options in the makefiles.
#
# WITH_OPENSSL_BASE=yes - Use the version in the base system.
# WITH_OPENSSL_PORT=yes - Use the OpenSSL port, even if base is up to date

I can confirm that setting or testing those variables is how you modify 
the OpenSSL linking behaviour of a port.  There's currently 51 ports 
that do so.  Off hand, an example is www/nginx-devel.  It can't use 
OpenSSL 0.9.8 if you enable SPDY, so it sets WITH_OPENSSL_PORT=yes if 
OSVERSION < 1000028.

>> On 2015-03-20 11:02, Naram Qashat wrote:
>>> This isn't quite what I'm looking for. I want to be able to tell within
>>> a
>>> port's Makefile if the user wanted the base or ports OpenSSL to be used.
>>> I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
>>> check for OpenSSL. This would work if the only form of OpenSSL was in
>>> ports, but the base OpenSSL doesn't have a pkg-config file to use, so I
>>> need to know which is going to be used so I can determine when this
>>> pkg-config check can be removed.
>>
>> `grep WITH_OPENSSL_ Makefile`
>>
>> If the port expresses an opinion about which OpenSSL to use, it has to
>> use WITH_OPENSSL_PORT or WITH_OPENSSL_BASE.
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>