On Wednesday 07 December 2011, Renato Utsch wrote:
> >I think it's $ORIGIN, not @ORIGIN.
> >
> >Alex
>
> This works with WIN files too?
Do you mean under Windows ?
No, there is no RPATH or installname_dir there.
IIRC, under Windows, it first checks in the same directory as the executable,
and t
>I think it's $ORIGIN, not @ORIGIN.
>
>Alex
This works with WIN files too?
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
On Tuesday 25 October 2011, Alexander Neundorf wrote:
...
> If you want to create a zip file, you should use "make package" to do that.
> During that step also "make install" will be executed.
> In that step the install RPATH will be patched into the ELF files.
> By default this will be empty (so t
On Tuesday 25 October 2011, Renato Utsch wrote:
> Hello!
>
> I am learning to use CMake and I found it very easy to use, very and very
> good. But I don't understand why it uses full paths instead of relative
> paths when linking shared/dynamic libraries. I am currently making a
> program that is
Hello!
I am learning to use CMake and I found it very easy to use, very and very
good. But I don't understand why it uses full paths instead of relative
paths when linking shared/dynamic libraries. I am currently making a program
that is only compiled to a folder, but not installed to the system (
