Hi,
I would be thankful if some body can give me a suggestion as to where
I can change the compiler from gcc to mpicc in cmake. One more
question Is it necessary to also have the compiler g++ installed
incase of using gcc or compiler mpic++ installed in case of using
mpicc ? The problem is I do
The LINK_DIRECTORIES has to be before the ADD_EXECUTABLE.
Another way to do it that should work for both version of cmake
is to use the full path to the library in target_link_libraries.
target_link_libraries(MyProject d:/dcmtk-3.5.3/dcmdata.lib)
The duplicate library stuff has been fixed in cvs
Just to check, I've made the littlest cmakelists.txt file I can that shows
the problem. Here it is in it's entirety:
PROJECT(MyProject)
ADD_EXECUTABLE(MyProject WIN32 file2.cpp )
LINK_DIRECTORIES( "d:/dcmtk-3.5.3" )
TARGET_LINK_LIBRARIES(MyProject dcmdata.lib)
If I build a project for Visual Stu
It already is before the targets that need it are added. Any other ideas?
Jolinda
-Original Message-
From: Brad King [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 6:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [CMake] Problem with link directories
jolinda w
I'm using CMake 2.2.3, swig 1.3.28 on Suse Linux 9.3.
I want to set a couple of different options for a swig interface file
I'm compiling:
# This is all on a single line if my email program munges it.
SET_SOURCE_FILES_PROPERTIES(manta.i PROPERTIES SWIG_FLAGS "-Wall
-DSCI_NOPERSISTENT")
Wel
Hi
I was able to successfully run the CTest, while posting the
test results to the public dashboard.
Now I want to post it to the Dart server running in my
machine. My Dart server is up and running; and can view my dashboard at http://localhost:8081/TestProject/Dashboard/
I unde
At 04:02 AM 3/7/2006, Prakash Punnoor wrote:
>rm CMakeCache.txt
>cmake .
>
>-- Check for working C compiler: gcc
>-- Check for working C compiler: gcc -- works
>-- Check size of void*
>-- Check size of void* - done
>no uname<--
>-- Configuring done
>-- Generating done
>
Hi Vingesh,
I will fix this bug in CTest for the next release. That said, for now,
could you just make sure to run CTest in the directory where your tests
are? What I mean is something like this. If your BuildDirectory is
pointing to /foo/bar, then make sure you first do:
cd /foo/bar
befor
Hi
I hope there is a misunderstanding; it doesn't work in the right directory
too.
I am not even able to test run the CTest using
ctest -D ExperimentalStart -D ExperimentalTest -D ExperimentalSubmit
The problem is "Testing" folder gets created in the current directory
itself, irrespective of t
Vignesh M.P.N. would like to recall the message, "[CMake] CTest newbie".
<>___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
-Original Message-
From: Andy Cedilnik [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 3:31 PM
To: Vignesh M.P.N.
Subject: Re: [CMake] CTest newbie
Hi,
For now just make sure you run ctest in the right directory.
Andy
Vignesh M.P.N. wrote:
>Hi
>
>I have posted the b
We are talking static libs here right ?
Instead of manually modifying Makefile, could you instead modify the
file:
Just for clarification: No, we're talking about shared libraries! Static
libraries in conjunction with threads don't work on HPs.
With your hint I can alter the order -lXext
jolinda wrote:
Hi,
I have a Visual Studio 7.0 project that was building fine using CMake-1.8
that won't build with version 2.2. I have a simple CMakeLists.txt file that
includes things like:
LINK_DIRECTORIES( ${DCMTK_PATH}/dcmdata/libsrc
${DCMTK_PATH}/dcmimage/libsrc )
When u
Hi Burkhard,
Burkhard Neinhues wrote:
Hi,
building VTK on HPUX PARISC machines has never worked so far without
adjusting Makefiles manually.
However, now with version 5.0, the PARISC linker often fails to locate
dependent libraries.
This is NOT a problem with
1) libraries not being presen
14 matches
Mail list logo