501:[mjack...@ferb:~]$ cd Desktop/
502:[mjack...@ferb:Desktop]$ mkdir Test
503:[mjack...@ferb:Desktop]$ cd Test; mkdir Build; cd Build
509:[mjack...@ferb:Build]$ cmake ../
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- CMAKE_SIZEOF_VOID_P: 4 <============ THIS IS WRONG FOR X64 builds
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/mjackson/Desktop/Test/Build
#---------
project (Test)
message(STATUS "CMAKE_SIZEOF_VOID_P: ${CMAKE_SIZEOF_VOID_P}")
So you are saying that I need to write my own Try_Compile and test for
the size? Which is fine by me I just want to be clear on the
recommendation.
_________________________________________________________
Mike Jackson mike.jack...@bluequartz.net
www.bluequartz.net
On Jun 11, 2009, at 2:46 PM, Bill Hoffman wrote:
Michael Jackson wrote:
And what if you are on a system like OS X where the default build
is 32 bit but you can have a 64 bit binary built? Then
CMAKE_SIZEOF_VOID_P is going to be invalid.
No, it is done with a try compile based on the current compiler
settings.
-Bill
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
