On 05/29/2014 12:32 PM, Vadim Zhukov wrote:
> I was not aware of such issue before that question. :) Yes, paths are
> written in NEEDED entries if requested, that's what CMake does for
> "external" libraries (outside project). Internal libraries are linked
> by name, though, allowing to relocate th
On 05/28/2014 05:19 PM, J Decker wrote:
>> CMake would much rather use full paths rather than -L/-l because of
>> ambiguity problems.
>
> I can get around abguity by ordering the order of -L entries..
CMake versions prior to 2.6 always did that. We had no end of trouble
with the wrong library f
> CMake would much rather use full paths rather than -L/-l because of
> ambiguity problems.
>
>
> While I can see that; I can get around abguity by ordering the order of -L
entries... like if one was buliding an upgrade to an already installed
library, one would want the current version to link aga
On 28.05.2014 22:27, Rolf Eike Beer wrote:
Nils Gladitz wrote:
Given that the topic might have one valid use case after all?
It would be useful as it would allow to drop more OpenBSD downstream patches.
It has been pointed out that this might not be the best approach given
the potential ambigu
Nils Gladitz wrote:
> On 28.05.2014 20:15, Brad King wrote:
> > On 05/28/2014 12:17 PM, Nils Gladitz wrote:
> >> In case you drop "-Wl,-soname" entirely ... how do you work around the
> >> issue of the linker using paths rather than names in NEEDED entries?
> >> Or does the issue not exist on OpenB
