You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Mario Emmenlauer (JIRA)" <ji...@apache.org> on 2017/12/07 20:35:00 UTC
[jira] [Created] (THRIFT-4412) thrift cmake does not use absolute
library path, linking system libraries
Mario Emmenlauer created THRIFT-4412:
----------------------------------------
Summary: thrift cmake does not use absolute library path, linking system libraries
Key: THRIFT-4412
URL: https://issues.apache.org/jira/browse/THRIFT-4412
Project: Thrift
Issue Type: Bug
Components: Build Process
Affects Versions: 0.10.0, 0.11.0, 1.0
Reporter: Mario Emmenlauer
I build thrift using cmake on Linux. It works generally very good on many platforms (I've tested Linux, Windows and MacOSX extensively). But one issue is plaguing me. I have my own custom boost libraries, libevent and others. I set CMAKE_PREFIX_PATH to their install directory. This generally also works well, and cmake finds the libraries. However in the final Makefile, the linker command uses `-lxxx` for library `xxx` instead of the usual cmake absolute path `/a/b/c/libxxx.so`. This is a problem because `ld` suddenly prefers the system libraries over my custom builds. This in turn breaks the build for me.
I do not have this problem with any other cmake builds. And I tried various workarounds to force cmake to use the absolute path, but failed. Did somebody maybe add this on purpose?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)