is UNIX on Apple true? I mean the build-in-variables.
.e.g:
IF(UNIX)
...
IF(APPLE)
...
ENDIF(APPLE)
ENDIF(UNIX)
I don't have a Apple-maschine to test it.
Greetings
Micha
___
Powered by
On 07.08.09 09:05:26, Micha Renner wrote:
is UNIX on Apple true? I mean the build-in-variables.
Yes, MacOS is a Unix derivative, so UNIX is set.
Andreas
--
Your love life will be... interesting.
___
Powered by www.kitware.com
Visit other Kitware
hi,
How could I control my generated object files name? Because I found in my cmake
project, *.c/*.cc/*.cpp will generated to object *.c.o/*.cc.o/*.cpp.o, but I
really want to get *.o. Such as:
$ find . -name *.o
./src/CMakeFiles/RSLcommon.dir/BasicDdm.cc.o
Micha,
is UNIX on Apple true? I mean the build-in-variables.
Yes, MacOS is a Unix derivative, so UNIX is set.
Maybe obvious, but since I am new and learning, you can also do:
IF(UNIX AND NOT APPLE)
...
ENDIF(UNIX AND NOT APPLE)
-Jason
Hi Michael,
Thank you for your reply.
What is the best way to do that exactly? I am in cluding Carbon/
Carbon.h in my source files. but I guess CMAKE needs to know
where to fine them too. moving form XCode is harder than I
thought it would be.
include_directories
I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to
link my software correctly.
The issue had been described some time ago:
http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
I figured out that cmake-2.6.3/Modules/Platform/NetBSD.cmake contains some
ML wrote:
Hi Michael,
I still get the same compile errors as before. But works using Xcode for
me.
Is there another resource as I can't find an example of these basic
things on the wiki. Even Google searching is not really turning up much.
I did
Frank Mertens wrote:
I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to
link my software correctly.
The issue had been described some time ago:
http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
I figured out that
Brad King wrote:
Frank Mertens wrote:
The solution was simple: cp NetBSD.cmake OpenBSD.cmake.
I think those two files can be kept safely identical.
Currently OpenBSD.cmake has this line:
SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERSIONING 1)
I've applied the commit below.
Hello,
I use CMake with boost::python to generate python modules, and it does a
great job of creating the required .so files. There's an interesting
question, however, of how to test the resulting object. When doing an
out-of-source build, I end up with
build/myproj/foo.so
and in my source
On Fri, Aug 07, 2009 at 10:08:16AM -0400, Eric Jonas wrote:
I'd like to, as part of the build process, copy test_foo.py
to build/myproj/test_foo.py . That is, when I type make, if
src/myproj/test_foo.py differs from build/myproj/test_foo.py, copy it
over.
I've tried various incantations
There is a FAQ entry about this that ought to work. Why don't you post
what you have so we can see where you're going wrong?
Also you can use cmake -E copy_if_different as the command part. It is
platform-independent, unlike cp.
Tyler, thanks for the quick response -- after quite a bit
Hi,
I am trying to install ITK using cmake on my computer, but I got the error
message below. Any help in this regard is highly appreciated.
Regards,
Siamak Yousefi
CMake Error at
/home/syouse/cmake/share/cmake-2.6/Modules/CMakeTestCCompiler.cmake:32
(MESSAGE):
The C compiler /usr/bin/gcc is
On Fri, Aug 07, 2009 at 08:09:34AM -0700, Siamak Yousefi wrote:
CMake Error at
/home/syouse/cmake/share/cmake-2.6/Modules/CMakeTestCCompiler.cmake:32
(MESSAGE):
The C compiler /usr/bin/gcc is not able to compile a simple test program.
It fails with the following output:
Change Dir:
Hi,
I checked the access to /home/syouse/ITKb/CMakeFiles/CMakeTmp, it has the
permission of writing. This /usr/bin/gcc is the path to gcc and g++. My shell
is c shell. I run these three commands before configuring ITK:
setenv PATH ${PATH}:/home/syouse/cmake/bin
setenv CC /usr/bin/gcc
setenv
Brad King wrote:
Frank Mertens wrote:
I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly
to link my software correctly.
The issue had been described some time ago:
http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
I figured out that
Frank Mertens wrote:
Brad King wrote:
Frank Mertens wrote:
I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly
to link my software correctly.
The issue had been described some time ago:
http://www.cmake.org/pipermail/cmake/2006-November/011851.html.
I figured out
On Fri, Aug 07, 2009 at 08:43:51AM -0700, Siamak Yousefi wrote:
I checked the access to /home/syouse/ITKb/CMakeFiles/CMakeTmp, it has
the permission of writing. This /usr/bin/gcc is the path to gcc and
g++. My shell is c shell. I run these three commands before
configuring ITK:
setenv PATH
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I skimmed through CMake Testing With CTest
and
On Aug 7, 2009, at 9:30 AM, Bill Hoffman wrote:
ML wrote:
Hi Michael,
I still get the same compile errors as before. But works using
Xcode for me.
Is there another resource as I can't find an example of these basic
things on the wiki. Even Google searching is not really turning up
much.
Bill Hoffman wrote:
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I skimmed through CMake
Bill Hoffman wrote:
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I skimmed through CMake
Bill Hoffman wrote:
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I skimmed through CMake
Frank Mertens wrote:
Bill Hoffman wrote:
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I
Frank Mertens wrote:
Bill Hoffman wrote:
Frank Mertens wrote:
I'm running OpenBSD on a freshly refurbishes office server.
It does currently nothing else than running tests for my
inhouse needs. Give me the pointers and I set it up as testing
client for cmake, too.
Being new to ctest, I
Frank Mertens wrote:
Oh,... well I just run 'make Experimential' on the CVS source an hour ago.
It passed all tests! But I fear the dart stuff failed to send a report,
got some strange errors about '/proc/cpuinfo' missing. Right OpenBSD
has sysctl and no '/proc'. I probably have to stick my
Hi All,
Continuing this conversation
Folks, CMake is framework aware. You don't need to add the -F
stuff. You can either use a full path to a framework in
include_directories or
in target_link_libraries. Find_library will also find frameworks.
The following will work:
27 matches
Mail list logo
