thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James E. King, III (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (THRIFT-4412) thrift cmake does not use absolute library path, linking system libraries
Date Fri, 08 Dec 2017 13:55:00 GMT

    [ https://issues.apache.org/jira/browse/THRIFT-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283532#comment-16283532
] 

James E. King, III commented on THRIFT-4412:
--------------------------------------------

CMAKE_PREFIX_PATH only controls the cmake find_ routines.  I don't think it is supposed to
be used to add a link library directory to the linker's search path.  There may be a cmake
option you can set for the FindBoost module that will force it to use full paths instead.
 I'm not convinced this is a thrift project issue (yet).

> 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