thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Emmenlauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (THRIFT-4412) thrift cmake does not use absolute library path, linking system libraries
Date Tue, 12 Dec 2017 14:27:00 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mario Emmenlauer resolved THRIFT-4412.
--------------------------------------
    Resolution: Won't Fix

[~jking3] I thik you are right and this issue is too broad for thrift. Its possibly just a
cmake issue that requires special handling. I'll investigate with cmake, and if I find a workaround
I'll propose it here.

> 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: Question
>          Components: Build Process
>    Affects Versions: 0.10.0, 0.11.0
>            Reporter: Mario Emmenlauer
>            Assignee: James E. King, III
>            Priority: Minor
>
> 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)

Mime
View raw message