Dear Cmake users,
I'm facing to a problem I can't resolve.
I'm developping on a windows XP SP3 box with Visual Studio 2005.
I have a project using itk which compile fine.
For some reason, I try to use cmake to generate the same project and I
got linker error (conflict between msvcrtd.lib and
On Fri, May 21, 2010 at 8:01 AM, Daanen Vincent daa...@koelis.com wrote:
Dear Cmake users,
I'm facing to a problem I can't resolve.
I'm developping on a windows XP SP3 box with Visual Studio 2005.
I have a project using itk which compile fine.
For some reason, I try to use cmake to
Am 20.05.2010 um 13:33 schrieb Michael Hertling:
On 05/20/2010 01:04 PM, Christoph Rüdiger wrote:
[...]
I've a directory src containing the complete source code of the
program and
another directory called test containing the source code for the
unit tests.
In the top level directory is a
On Fri, May 21, 2010 at 10:17 AM, Daanen Vincent daa...@koelis.com wrote:
Hello,
Can you post the exact error.
I would say that these errors are the well-known linker errors about libcmt
and msvcrt
msvcrtd.lib(ti_inst.obj) : error LNK2005: private: __thiscall
type_info::type_info(class
Does the problem happen in both Debug and Release builds?
Visual C++ has a well known problem of mixing debug and release libraries
together. My suspicion is that you have some dependant libraries that are
only built in Debug or only built in Release. With Visual C++ it is
important that all
Hi,
I'm trying to update an existing cmake project to be used on MacOsX. After a
lot of thinking, I can now build, using the right framworks/library/using the
good SDK/on the right ARCHitecture... It was hard, because there is nearly no
MacOsX cmake documentation (or not up to date).
The
It also may be caused by linking code compiled with /MT against code
compiled with /MD (or vice versa).
On Fri, May 21, 2010 at 10:48 AM, Chuck Atkins chuck.atk...@kitware.comwrote:
Does the problem happen in both Debug and Release builds?
Visual C++ has a well known problem of mixing debug
On 21. May, 2010, at 16:42 , Jérôme VERNET wrote:
Hi,
I'm trying to update an existing cmake project to be used on MacOsX. After a
lot of thinking, I can now build, using the right framworks/library/using the
good SDK/on the right ARCHitecture... It was hard, because there is nearly no
Le 21/05/10 18:20, Michael Wild a écrit :
On 21. May, 2010, at 16:42 , Jérôme VERNET wrote:
Hi,
I'm trying to update an existing cmake project to be used on MacOsX. After a
lot of thinking, I can now build, using the right framworks/library/using the
good SDK/on the right ARCHitecture...
oops...
Le 21/05/10 18:20, Michael Wild a écrit :
Well, the actual error message would have been of help here, wouldn't it? And while
you're at it, run with make VERBOSE=1 in order to see the actual commands
being run.
Here is what I get:
Copying OS X content
That is not a file, but really a folder and maybe that is messing up
CMake?
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton,
Yes, you have to copy every file individually. AFAIK there is a source file
property you can set to specify the location inside the bundle.
That is not a file, but really a folder and maybe that is messing up
CMake?
___
Mike Jackson
Le 21/05/10 22:08, Michael Wild a écrit :
Yes, you have to copy every file individually. AFAIK there is a source file
property you can set to specify the location inside the bundle.
That is not a file, but really a folder and maybe that is messing up
CMake?
Localized resources
[Didn't send to list, so I forward my reply to Jerome.]
Original Message
Subject: Re: [CMake] Need cmake help for MacOsX
Date: Fri, 21 May 2010 22:02:42 +0200
From: Werner Smekal sme...@iap.tuwien.ac.at
To: Jérôme VERNET vernet.jer...@wanadoo.fr
Hi Jerome,
On 5/21/10 4:42 PM,
Thanks for your help. Things are better, but far from perfect, see below
Le 21/05/10 22:34, Werner Smekal a écrit :
Hi Jerome,
On 5/21/10 4:42 PM, Jérôme VERNET wrote:
# copy SDL frameworks into app bundle for Mac OS X
if(APPLE)
INSTALL(DIRECTORY
Hi --
At the risk of asking a stupid question: I seem to have a situation
where CMake (2.8.1 on Windows XP) completely ignore an IF .. ELSE ..
ENDIF construct and basically does neither the IF nor the ELSE branch.
My CMakeLists.txt is as follows:
CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
On Fri, May 21, 2010 at 02:04:38PM -0700, Torsten Rohlfing wrote:
FIND_PACKAGE(ZLIB)
IF(ZLIB_FOUND)
MESSAGE( WARNING HAVE system zlib )
ELSEIF(ZLIB_FOUND)
MESSAGE( WARNING NO system zlib )
ENDIF(ZLIB_FOUND)
I don't see an else clause here, just two ifs (that check the same
condition).
17 matches
Mail list logo