Andreas Naumann wrote:
> cmake instrospects your compiler and asks for system directories.
Just stumbled across this documentation tidbit:
>>>
CMAKE__IMPLICIT_LINK_DIRECTORIES
--
Implicit linker search path detected for language .
Compilers typically
Eric Noulard wrote:
> AFAIK the explanation you gave. CMake does not seem to play with -l or -L
> options.
As Rolf said above, apparently it does.
> the FindPNG.cmake shipped with CMake does not do that either.
Indeed, it sets PNG_LIBRARY to the path of libpng, and PNG_LIBRARIES to the 2
requi
2017-07-12 21:14 GMT+02:00 René J. V. Bertin :
> Rolf Eike Beer wrote:
>
> >> It seems that clang handles that variable in a somewhat different manner
> >> than GCC does. Even in a very simple call on the commandline (including
> the
> >> -v option) I see it adds -L/opt/local/lib AFTER the user-su
Rolf Eike Beer wrote:
>> It seems that clang handles that variable in a somewhat different manner
>> than GCC does. Even in a very simple call on the commandline (including the
>> -v option) I see it adds -L/opt/local/lib AFTER the user-supplied
>> libraries, where GCC puts it before the 1st -l op
If they were not propagated, it wouldn't compile at all, so they're
definitely there somewhere.
Can you show your CMakeLists.txt files?
/Florent
On 12/07/2017 19:59, Christian Mazakas wrote:
To give a brief overview of what I'm trying to do, right now I'm
working on a project with tests. I wa
I am proud to announce the sixth CMake 3.9 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.9
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.9/release/3.9.html
Some of the more significant ch
To give a brief overview of what I'm trying to do, right now I'm working on
a project with tests. I want to abstract my implementation into a library
that I can then link to when building both a testing binary and an
application binary.
The issue is, my library is currently header-only. So I figur
Am Mittwoch, 12. Juli 2017, 18:31:56 schrieb René J. V. Bertin:
> Andreas Naumann wrote:
> > cmake instrospects your compiler and asks for system directories. Only
> > these system directories will be removed and the corresponding libraries
> > will be linked by -l<...>. So, you should check your c
FWIW, I do question this rewriting feature, because it clearly can go wrong.
I'd argue that programmers (or build script/cmake modules/...) usually have
good
reason when they give the absolute path to a library: making darn sure it's
indeed that one that gets linked.
While I agree that replaci
Andreas Naumann wrote:
> cmake instrospects your compiler and asks for system directories. Only
> these system directories will be removed and the corresponding libraries
> will be linked by -l<...>. So, you should check your compiler and the
> environment. I had several problems years ago with th
Dear Rene,
cmake instrospects your compiler and asks for system directories. Only
these system directories will be removed and the corresponding libraries
will be linked by -l<...>. So, you should check your compiler and the
environment. I had several problems years ago with the environment
v
Hi,
I have a target_link_libraries command that uses ${PNG_LIBRARIES} and thus
*should* add something like `/path/to/libpng.so /path/to/libz.so` to the linker
command. Instead, I am getting a linker command line that has `-lpng -lz`,
which fails for me because the `/path/to` in question isn't o
12 matches
Mail list logo
