On 04/11/2011 11:10 PM, David Aiken wrote:
> That didn't work for me.. I've got it simplified down to:
> SET(CMAKE_SKIP_RPATH TRUE)
> and in the CMakeCache.txt I see:
> CMAKE_SKIP_RPATH:BOOL=NO
That's not surprising as your SET() command doesn't write to the cache.
It's the CMAKE_SKIP_RPATH variab
On 04/11/2011 10:42 PM, Tomasz Grobelny wrote:
> On Monday 11 April 2011 21:55:48 Alexander Neundorf wrote:
>> On Monday 11 April 2011, Tomasz Grobelny wrote:
>>> On Mon, 11 Apr 2011 09:01:09 -0700, Tyler wrote:
On Mon, Apr 11, 2011 at 8:54 AM, Tomasz Grobelny
wrote:
> Ok, but
That didn't work for me.. I've got it simplified down to:
SET(CMAKE_SKIP_RPATH TRUE)
and in the CMakeCache.txt I see:
CMAKE_SKIP_RPATH:BOOL=NO
and further down:
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
I'm using the codeblocks unix makefile target. The rpath is present in both the
build and install s
On Monday, April 11, 2011 01:49:21 pm John R. Cary wrote:
> Scenario:
>
> A library libA.dylib is found somewhere in the building of
> executable B. Doing the typical link, otool -L shows that B
> references:
>
>libA.dylib
>
> or possibly
>
>/A/prefix/lib/libA.dylib.
>
> I want B to r
On Monday 11 April 2011 21:55:48 Alexander Neundorf wrote:
> On Monday 11 April 2011, Tomasz Grobelny wrote:
> > On Mon, 11 Apr 2011 09:01:09 -0700, Tyler wrote:
> > > On Mon, Apr 11, 2011 at 8:54 AM, Tomasz Grobelny
> > >
> > > wrote:
> > >> Ok, but is there a way to achieve the same effect so
Scenario:
A library libA.dylib is found somewhere in the building of
executable B. Doing the typical link, otool -L shows that B
references:
libA.dylib
or possibly
/A/prefix/lib/libA.dylib.
I want B to run from either the build directory or the
installation directory, which I want to be
> You should set CMAKE_PREFIX_PATH instead of relying on pkgconfig. Then you
> can
> be sure that cmake will figure out the stuff in a way that it works (i.e.
> libraries with full paths).
>
That worked like a charm. I'm glad there turned out to be a simple
solution.
> > link_directories( ${
On Monday 11 April 2011, cheshirekow wrote:
> I'm pretty new to cmake and I'm trying to port an (early) project with
> gtkmm-3.0. The project builds fine with my makefiles, so I know I don't
> have errors in the code. I'm running ubuntu lucid so I don't want to
> install gtkmm-3.0 (and it's dozen d
On Monday 11 April 2011, David Aiken wrote:
> Hi all..
>
> I'm using cmake 2.8.4 on Centos 5.2. I build a libUtility.so and a
> libSecurity.so which depends on it. The utility library is located in
> "../../lib/libUtility.so" during the build. If I do an ldd on
> libSecurity.so I can see this relat
On Monday 11 April 2011, Tomasz Grobelny wrote:
> On Mon, 11 Apr 2011 09:01:09 -0700, Tyler wrote:
> > On Mon, Apr 11, 2011 at 8:54 AM, Tomasz Grobelny
> >
> > wrote:
> >> Ok, but is there a way to achieve the same effect so that the user can
> >> type just "make install" and not know anything ab
I'm pretty new to cmake and I'm trying to port an (early) project with
gtkmm-3.0. The project builds fine with my makefiles, so I know I don't
have errors in the code. I'm running ubuntu lucid so I don't want to
install gtkmm-3.0 (and it's dozen dependencies) in the system locations
(/usr, /usr/loc
2011/4/11 David Aiken :
> Hi all..
>
>
>
> I’m using cmake 2.8.4 on Centos 5.2. I build a libUtility.so and a
> libSecurity.so which depends on it. The utility library is located in
> “../../lib/libUtility.so” during the build. If I do an ldd on libSecurity.so
> I can see this relative path for lib
Hi all..
I'm using cmake 2.8.4 on Centos 5.2. I build a libUtility.so and a
libSecurity.so which depends on it. The utility library is located in
"../../lib/libUtility.so" during the build. If I do an ldd on libSecurity.so I
can see this relative path for libUtility.so in both the build and ins
On Mon, 11 Apr 2011 09:01:09 -0700, Tyler wrote:
> On Mon, Apr 11, 2011 at 8:54 AM, Tomasz Grobelny
> wrote:
>> Ok, but is there a way to achieve the same effect so that the user can
>> type just "make install" and not know anything about DESTDIR
environment
>> variable (provided he knows about M
On Mon, Apr 11, 2011 at 8:54 AM, Tomasz Grobelny
wrote:
> Ok, but is there a way to achieve the same effect so that the user can
> type just "make install" and not know anything about DESTDIR environment
> variable (provided he knows about MYDESTDIR)? Maybe it is possible to put
> this "DESTDIR=$M
On Mon, 11 Apr 2011 16:07:36 +0200, Michael Wild
wrote:
> On 04/11/2011 03:16 PM, Tomasz Grobelny wrote:
>> I need behaviour that is available with DESTDIR (that is changing
>> location
>> of installation root after configuration and build is done) but with
>> different name of environment variabl
On the CMake dashboard itself, we are running valgrind dashboards, too.
One with ctest 2.8.1.20100608-g32b96.
Then I set up identical dashboards, but using ctest 2.8.3 and ctest 2.8.4
after you reported this last month.
They've been reporting just fine with all versions of ctest.
Perhaps you co
Anyone have a clue how we can get CDash to display the valgrind report
properly. Last month I noted that with cmake 2.8.4 we could not get the
valgrind reports displayed properly, the report shows the raw compressed (or
otherwise encrypted data). We have the same problem using CMake 2.8.3, 2.8.2
On 04/11/2011 03:16 PM, Tomasz Grobelny wrote:
> I need behaviour that is available with DESTDIR (that is changing location
> of installation root after configuration and build is done) but with
> different name of environment variable (eg. MYDESTDIR). Is it possible with
> cmake?
export MYDESTDI
Hello,
I'm a beginner and I apologize in case I'm asking a question that
has already been answered. I would like to find mpi in my
CMakeLists.txt and enable the user to set the mpi inlude and lib
directories by setting say variables MY_MPI_INCLUDE_DIR and
MY_MPI_LIB_DIR in cmake gui.
U
Hi,
I ran into some strange behaviour when using the CMAKE_DEBUG_POSTFIX
variable with the VS2010 generator. The solution generates fine and all the
libraries of the project are built like they should in debug configuration
with the "_d" postfix I specified. The problem is now that when linking on
I need behaviour that is available with DESTDIR (that is changing location
of installation root after configuration and build is done) but with
different name of environment variable (eg. MYDESTDIR). Is it possible with
cmake?
--
Regards,
Tomasz Grobelny
___
22 matches
Mail list logo
