Closed nim65s closed 2 years ago
For CMake < 3.12, we use upgraded version of FindBoost.cmake:
https://github.com/jrl-umi3218/jrl-cmakemodules/blob/f4e4be6a6f6577d86c9e2b09ae3a9bf1a545437e/boost.cmake#L40-L46
But then, when we export the Boost targets, they don't exists on dependent projects that don't have a similar workaround and try to link to our packages and still use CMake < 3.12.
ref https://github.com/stack-of-tasks/eigenpy/pull/307
For CMake < 3.12, we use upgraded version of FindBoost.cmake:
https://github.com/jrl-umi3218/jrl-cmakemodules/blob/f4e4be6a6f6577d86c9e2b09ae3a9bf1a545437e/boost.cmake#L40-L46
But then, when we export the Boost targets, they don't exists on dependent projects that don't have a similar workaround and try to link to our packages and still use CMake < 3.12.
ref https://github.com/stack-of-tasks/eigenpy/pull/307