Zachary Pincus wrote:
Thanks everyone for your suggestions about how to deal with rpaths (aka
install names for OS X dylibs) and installed shared libraries.
Option A is to disable the rpaths and make sure that (1) the libraries
are installed in a "standard" location, or (2) [DY] LD_LIBRARY_P
Thanks everyone for your suggestions about how to deal with rpaths
(aka install names for OS X dylibs) and installed shared libraries.
Option A is to disable the rpaths and make sure that (1) the
libraries are installed in a "standard" location, or (2) [DY]
LD_LIBRARY_PATH is set to the inst
Tanner Lovelace wrote:
On 2/23/06, Brad King <[EMAIL PROTECTED]> wrote:
You can set CMAKE_SKIP_RPATH in the advanced cache options to disable
the rpaths that point at the build tree (this works with any CMake
version). Then the installed libraries will not have any rpath.
Programs can be execu
On 2/23/06, Brad King <[EMAIL PROTECTED]> wrote:
> You can set CMAKE_SKIP_RPATH in the advanced cache options to disable
> the rpaths that point at the build tree (this works with any CMake
> version). Then the installed libraries will not have any rpath.
> Programs can be executed by adding their
Brad King wrote:
Zachary Pincus wrote:
It seems like this issue will arise with any CMake-driven project,
and not just ITK. So, in its current state, can CMake be used to
create shared libs that work properly when installed? I know that
CMake just got custom rpath support (thanks Brad!), so
Zachary Pincus wrote:
Hi folks,
For the first time ever, I actually installed ITK (built with shard
libs) as opposed to using it from the build directory.
After installing ITK, I moved the build directory and tried to build
and run a project that uses ITK. The project built fine, because t
Hi folks,
For the first time ever, I actually installed ITK (built with shard
libs) as opposed to using it from the build directory.
After installing ITK, I moved the build directory and tried to build
and run a project that uses ITK. The project built fine, because the
linker saw the ins
[EMAIL PROTECTED] wrote:
I have a couple of quick questions about the CMAKE_DEBUG_POSTFIX variable.
1. Is there any documentation on it?
Not currently, it was an experimental feature until recently.
2. What version(s) of CMake supports it?
It partially works in CMake 2.2 (and maybe 2.0).
Walter E Brown wrote:
> >Why does TRY_COMPILE not only compile but also try to link the code?
Actually
> >compilng only would be enough to run most tests and would also be a bit
> >faster if you avoid linking.
>Sometimes that is the only way to make sure something actually
compiles and work
I have retried my swig build with a version of cmake downloaded
yesterday
>cmake --version
>cmake version 2.3-20060222
Problem still exists - the solaris lib is generated as MyJNI.so rather
than libMyJNI.so.
On a side-note the bootstrap script fails due to ./Tests/CMakeTests dir
not existing
Root
I'm writing to express an opinion on the following exchange, extracted
from the CMake Digest, Vol 22, Issue 39:
> >Why does TRY_COMPILE not only compile but also try to link the code?
Actually
> >compilng only would be enough to run most tests and would also be a bit
> >faster if you avoid li
Am Donnerstag Februar 23 2006 16:40 schrieb William A. Hoffman:
> At 10:43 AM 2/23/2006, Prakash Punnoor wrote:
> >Now another question: nasm cannot link code, so what should I write into
> >CMAKE_ASM_LINK_EXECUTABLE? It should use the default c/c++/whatever
> > linker.
>
> It should run the link c
Hi Filipe,
I have not tested it on Visual Studio 8 and I know that there are some
STL issues. I'll look into that.
Andy
Filipe Sousa wrote:
Filipe Sousa wrote:
Filipe Sousa wrote:
Oops!
I just forgot to set CPACK_ vars in CMakeLists.txt. Now is working :)
Works on Linux, but not on
At 10:43 AM 2/23/2006, Prakash Punnoor wrote:
>Now another question: nasm cannot link code, so what should I write into
>CMAKE_ASM_LINK_EXECUTABLE? It should use the default c/c++/whatever linker.
It should run the link command directly.
>Why does TRY_COMPILE not only compile but also try to l
riable not set, cmake may be not
be built correctly.
Missing variable is:
CMAKE_ASM_LINK_EXECUTABLE
CMake Error: Internal CMake error, TryCompile generation of cmake failed
But, if I copy my 4 files for nasm integration from my project module dir into
CMAKE_ROOT (and adjusting the path in the CO
I have a couple of quick questions about
the CMAKE_DEBUG_POSTFIX variable.
1. Is there any documentation on it?
2. What version(s) of CMake supports
it?
3. Can it be used on the Windows platform
to dynamically name build products (libs in particular) to distinguish
between Debug and Release conf
At 03:08 AM 2/23/2006, Martin Baumann wrote:
>Hi,
>
>I have installed CMake on a Onyx2 system. When I run cmake I get the error:
>
>CMake Error: CMake was unable to find a build program corresponding to "Unix
>Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a
>different b
Hi,
I have installed CMake on a Onyx2 system. When I run cmake I get the error:
CMake Error: CMake was unable to find a build program corresponding to "Unix
Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a
different build tool.
CMake Error: Error required internal CMak
18 matches
Mail list logo
