Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@thrift.apache.org
Date: Thu, 7 Dec 2017 20:36:00 +0000 (UTC)
From: "Mario Emmenlauer (JIRA)" <jira@apache.org>
To: dev@thrift.apache.org
Message-ID: <JIRA.13123546.1512678867000.411896.1512678960180@Atlassian.JIRA>
In-Reply-To: <JIRA.13123546.1512678867000@Atlassian.JIRA>
References: <JIRA.13123546.1512678867000@Atlassian.JIRA> <JIRA.13123546.1512678867999@jira-lw-us.apache.org>
Subject: [jira] [Updated] (THRIFT-4412) thrift cmake does not use absolute
 library path, linking system libraries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Dec 2017 22:49:32 -0000


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

Mario Emmenlauer updated THRIFT-4412:
-------------------------------------
    Description: 
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?


  was:
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?


> 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)