[question] OpenSSL: casing issues in CMake module

[jgsogo]

Hi! I've just realized that the OpenSSL has some casing issues. According to the CMake module:

OpenSSL::SSL
OpenSSL::Crypto

but,

OPENSSL_FOUND
OPENSSL_INCLUDE_DIR
OPENSSL_CRYPTO_LIBRARY
OPENSSL_SSL_LIBRARY
OPENSSL_LIBRARIES
OPENSSL_VERSION

So, not even the cpp_info.names["cmake_***"] or the cpp_info.name will be able to deal with it, right? Am I missing something?

Thanks!

[madebr]

I asked something similar at conan-io/conan#5717 (comment)

[jgsogo]

Do you think we should go for the build_modules approach (add it to OpenSSL), or shall I modify the consumer to match the casing (I found this issue package tgbot)?

[SSE4]

I don't think it's possible to generate multiple CMake targets without the components feature

[jgsogo]

Right, my problem is related to the upper/lower case of the variables. tgbot consumes OPENSSL_LIBRARIES, but we have OpenSSL_LIBRARIES.

[SSE4]

very inconsistent, as usual, e.g.
https://cmake.org/cmake/help/v3.16/module/FindBZip2.html
vs
https://cmake.org/cmake/help/v3.16/module/FindBoost.html
and the most contradictory:
https://cmake.org/cmake/help/v3.16/module/FindLibXml2.html
notice LibXml2_FOUND vs LIBXML2_INCLUDE_DIR
without very flexible customization in generator, it's hard to satisfy every case
seems like it's very random, there is no logic, no standard, no specification...

[jgsogo]

Probably we should follow the comment linked by @madebr and we shouldn't try to recreate the CMake mess. It would be better to patch the build scripts of the consumers when there is some inconsistency, don't you think so?

[SSE4]

I agree, it's impossible to provide drop-in-replacement for something that is not well-defined, unfortunately.

[madebr]

I've gone the manual way and started to add these variables in some of my pull requests:

• bullet3: Add bullet3/2.89 recipe #440
• libpng: libpng: use PNG as name #434

Isn't this the same question as #419?

[jgsogo]

Yes, I think #419 is exactly the same (more general and better explained). I'm closing this one then