You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! I'm currently on a Mac machine and am building protobuf through ExternalProject_Add. My main project modifies the CMAKE_INSTALL_LIBDIR, so ideally I would love that propagated to the protoc executable instead of it being a hardcoded @loader_path/../lib. My question is, what is the purpose of this cmake code? Why is it hardcoded for mac machines?
In my application, I had to patch the protobuf repository to revert it back to use @loader_path/../${CMAKE_INSTALL_LIBDIR} instead of the hardcoded lib. The issue I was having was that I had another external repository use the protoc executable, however, since the libs did not exist in this location @loader_path/../lib, it was causing library load issues.
The text was updated successfully, but these errors were encountered:
Hey! I'm currently on a Mac machine and am building protobuf through ExternalProject_Add. My main project modifies the
CMAKE_INSTALL_LIBDIR
, so ideally I would love that propagated to theprotoc
executable instead of it being a hardcoded@loader_path/../lib
. My question is, what is the purpose of this cmake code? Why is it hardcoded for mac machines?https://github.com/protocolbuffers/protobuf/blob/main/cmake/install.cmake#L77
In my application, I had to patch the protobuf repository to revert it back to use
@loader_path/../${CMAKE_INSTALL_LIBDIR}
instead of the hardcoded lib. The issue I was having was that I had another external repository use the protoc executable, however, since the libs did not exist in this location@loader_path/../lib
, it was causing library load issues.The text was updated successfully, but these errors were encountered: