Closed nim65s closed 1 year ago
I was especially not inspired for those macro names, so if someone comes with better ones, don't hesitate.
What do you mean by relative inverse? This is no meaningful at first glance.
if the relative path from CMAKE_INSTALL_PREFIX
to ${PYWRAP}_INSTALL_DIR
is lib/python3.10/site-packages/eigenpy
, its "inverse" is ../../../..
. Or "revert", I don't know.
Or we can just remove this and state this is from ${PYWRAP}_INSTALL_DIR
to CMAKE_INSTALL_PREFIX
, it would make more sense, thanks
Or we can just remove this and state this is from
${PYWRAP}_INSTALL_DIR
toCMAKE_INSTALL_PREFIX
, it would make more sense, thanks
I don't get the shortcut. Could you explain a bit more?
I just removed the "inv" part and inverted the formulation.
with
REL_INV_INSTALL_PATH(FILE VARIABLE)
to compute the relative inverse install path ofFILE
and store it intoVARIABLE
eg:
and
LIB_REL_RPATH(TARGET_INSTALL_DIR VARIABLE)
to compute the relative path from thisTARGET_INSTALL_DIR
toCMAKE_INSTALL_LIBDIR
."eg:
fix. https://github.com/stack-of-tasks/eigenpy/issues/353 ref. https://github.com/jrl-umi3218/jrl-cmakemodules/pull/587