Target install does nothing with static oqsprovider.a library

[maroueneboubakri]

Hello,

The provider could be used as standalone library to be statically linked with a binary. Therefore, it makes sense that cmake --install or cmake --build . --target install installs the static library into lib folder. While nothing happens when those are invoked.

-- Install configuration: ""

Kindly consider this use case.

Br
Maro

[maroueneboubakri]

Also kindly keep consider naming liboqsprovider.a for static library to ease linking against it with gcc -loqsprovider instead of providing path to to oqsprovider.a.

[ghost]

Hi @maroueneboubakri, thank you for raising that issue.

Actually, you should be able to get your oqsprovider.a installed under your ${CMAKE_INSTALL_PREFIX} by using Debug or Release build type:

oqs-provider/oqsprov/CMakeLists.txt

Lines 89 to 92 in bfaf298

	install(TARGETS oqsprovider
	CONFIGURATIONS Debug Release
	LIBRARY DESTINATION "${OPENSSL_MODULES_PATH}"
	RUNTIME DESTINATION "${OPENSSL_MODULES_PATH}")

With an empty ${CMAKE_BUILD_TYPE} it installs nothing though.

I fixed this odd behavior, and I renamed oqsprovider.a to liboqsprovider.a (only if you build it statically) in #441.

I also added a CI test for it.