Re: [CMake] Properly Detecting Win64

2011-04-20 Thread David Cole
On Tue, Apr 19, 2011 at 5:44 PM, James Bigler jamesbig...@gmail.com wrote: On Tue, Apr 12, 2011 at 2:24 PM, Bill Hoffman bill.hoff...@kitware.comwrote: On 4/12/2011 4:13 PM, David Cole wrote: Does somebody have reproducible steps to get to the point where CMAKE_SIZEOF_VOID_P disappears??

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread Michael Jackson
On Apr 20, 2011, at 8:55 AM, David Cole wrote: On Tue, Apr 19, 2011 at 5:44 PM, James Bigler jamesbig...@gmail.com wrote: On Tue, Apr 12, 2011 at 2:24 PM, Bill Hoffman bill.hoff...@kitware.com wrote: On 4/12/2011 4:13 PM, David Cole wrote: Does somebody have reproducible steps to get

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread j s
If it helps, I always configure from a clean directory.  This script is written in bash for cygwin, but I'm sure it would be easy enough to do from some other script: CMAKE=/cygdrive/C/Program\ Files\ \(x86\)/CMake\ 2.8/bin/cmake.exe mkdir win32 (cd win32; $CMAKE -G Visual Studio 10 ..) mkdir

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread Michael Jackson
I normally do this also BUT sometimes I try to short circuit the process because I just want to regenerate the Solution/Projects and not have to wait for a complete CMake configuration which takes a really long time on some project due to the number of tests that need to be performed. At the

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread j s
On Wed, Apr 20, 2011 at 10:55 AM, Michael Jackson mike.jack...@bluequartz.net wrote: I normally do this also BUT sometimes I try to short circuit the process because I just want to regenerate the Solution/Projects and not have to wait for a complete CMake configuration which takes a really

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread David Cole
On Wed, Apr 20, 2011 at 12:05 PM, j s j.s4...@gmail.com wrote: On Wed, Apr 20, 2011 at 10:55 AM, Michael Jackson mike.jack...@bluequartz.net wrote: I normally do this also BUT sometimes I try to short circuit the process because I just want to regenerate the Solution/Projects and not have to

Re: [CMake] Properly Detecting Win64

2011-04-20 Thread James Bigler
On Wed, Apr 20, 2011 at 10:23 AM, David Cole david.c...@kitware.com wrote: On Wed, Apr 20, 2011 at 12:05 PM, j s j.s4...@gmail.com wrote: On Wed, Apr 20, 2011 at 10:55 AM, Michael Jackson mike.jack...@bluequartz.net wrote: I normally do this also BUT sometimes I try to short circuit the

Re: [CMake] Properly Detecting Win64 - [Semi Off Topic Reply]

2011-04-20 Thread Michael Jackson
Hey Dave, So here are some timings for running CMake to the point where I can actually build my project. THe hardware is an Mac Pro 8 Core (16 Thread) 2.6GHz OS X 10.6.6 box also running Windows 7 x64. On OS X I use Makefiles in combination with Eclipse as the IDE so I generate straight

Re: [CMake] Properly Detecting Win64 - [Semi Off Topic Reply]

2011-04-20 Thread David Cole
But you've blown everything else away at that point, so the *build* is a full rebuild, right? CMake configure takes 60 seconds, but how long does the full build take? On Wed, Apr 20, 2011 at 12:58 PM, Michael Jackson mike.jack...@bluequartz.net wrote: Hey Dave, So here are some timings for

Re: [CMake] Properly Detecting Win64 - [Semi Off Topic Reply]

2011-04-20 Thread j s
On Wed, Apr 20, 2011 at 12:04 PM, David Cole david.c...@kitware.com wrote: But you've blown everything else away at that point, so the *build* is a full rebuild, right? CMake configure takes 60 seconds, but how long does the full build take? My guess is that CMake is invoking a lot of

Re: [CMake] Properly Detecting Win64 - [Semi Off Topic Reply]

2011-04-20 Thread j s
On Wed, Apr 20, 2011 at 12:58 PM, j s j.s4...@gmail.com wrote: On Wed, Apr 20, 2011 at 12:04 PM, David Cole david.c...@kitware.com wrote: But you've blown everything else away at that point, so the *build* is a full rebuild, right? CMake configure takes 60 seconds, but how long does the full

Re: [CMake] Properly Detecting Win64

2011-04-19 Thread James Bigler
On Tue, Apr 12, 2011 at 2:24 PM, Bill Hoffman bill.hoff...@kitware.comwrote: On 4/12/2011 4:13 PM, David Cole wrote: Does somebody have reproducible steps to get to the point where CMAKE_SIZEOF_VOID_P disappears?? I've never seen that... How many times do you have to re-configure before

Re: [CMake] Properly Detecting Win64

2011-04-13 Thread Rolf Eike Beer
Maybe you can base the package name by testing the generator name. I need to do that to e.g. get a useful build naming in CTest scripts. At that point CMAKE_SIZEOF_VOID_P is not available anyway. And I think that using this is just a bad idea. How do you decide if it's IA64 or AMD64? I use this

Re: [CMake] Properly Detecting Win64

2011-04-13 Thread Rolf Eike Beer
Maybe you can base the package name by testing the generator name. I need to do that to e.g. get a useful build naming in CTest scripts. At that point CMAKE_SIZEOF_VOID_P is not available anyway. And I think that using this is just a bad idea. How do you decide if it's IA64 or AMD64? [...]

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread James Bigler
On Mon, Jan 17, 2011 at 11:27 AM, Michael Jackson mike.jack...@bluequartz.net wrote: On Jan 17, 2011, at 1:23 PM, Eric Noulard wrote: 2011/1/17 Michael Jackson mike.jack...@bluequartz.net: I have the following code: if ( ${CMAKE_SIZEOF_VOID_P} EQUAL 8 )

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread j s
On Tue, Apr 12, 2011 at 2:13 PM, James Bigler jamesbig...@gmail.com wrote: On Mon, Jan 17, 2011 at 11:27 AM, Michael Jackson mike.jack...@bluequartz.net wrote: On Jan 17, 2011, at 1:23 PM, Eric Noulard wrote: 2011/1/17 Michael Jackson mike.jack...@bluequartz.net: I have the following

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread James Bigler
On Tue, Apr 12, 2011 at 1:27 PM, j s j.s4...@gmail.com wrote: On Tue, Apr 12, 2011 at 2:13 PM, James Bigler jamesbig...@gmail.comwrote: On Mon, Jan 17, 2011 at 11:27 AM, Michael Jackson mike.jack...@bluequartz.net wrote: On Jan 17, 2011, at 1:23 PM, Eric Noulard wrote: 2011/1/17

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread David Cole
On Tue, Apr 12, 2011 at 4:07 PM, James Bigler jamesbig...@gmail.com wrote: On Tue, Apr 12, 2011 at 1:27 PM, j s j.s4...@gmail.com wrote: On Tue, Apr 12, 2011 at 2:13 PM, James Bigler jamesbig...@gmail.comwrote: On Mon, Jan 17, 2011 at 11:27 AM, Michael Jackson mike.jack...@bluequartz.net

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread Bill Hoffman
On 4/12/2011 4:13 PM, David Cole wrote: Does somebody have reproducible steps to get to the point where CMAKE_SIZEOF_VOID_P disappears?? I've never seen that... How many times do you have to re-configure before you start seeing this behavior? That sounds like something is just really wrong

Re: [CMake] Properly Detecting Win64

2011-04-12 Thread Michael Jackson
On Apr 12, 2011, at 4:24 PM, Bill Hoffman wrote: On 4/12/2011 4:13 PM, David Cole wrote: Does somebody have reproducible steps to get to the point where CMAKE_SIZEOF_VOID_P disappears?? I've never seen that... How many times do you have to re-configure before you start seeing this

[CMake] Properly Detecting Win64

2011-01-17 Thread Michael Jackson
I have the following code: if ( ${CMAKE_SIZEOF_VOID_P} EQUAL 8 ) set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Win64) elseif( ${CMAKE_SIZEOF_VOID_P} EQUAL 4 ) set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Win32) else() set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Unknown)

Re: [CMake] Properly Detecting Win64

2011-01-17 Thread Eric Noulard
2011/1/17 Michael Jackson mike.jack...@bluequartz.net: I have the following code: if ( ${CMAKE_SIZEOF_VOID_P} EQUAL 8 )        set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Win64) elseif( ${CMAKE_SIZEOF_VOID_P} EQUAL 4 )        set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Win32) else()        

Re: [CMake] Properly Detecting Win64

2011-01-17 Thread Michael Jackson
On Jan 17, 2011, at 1:23 PM, Eric Noulard wrote: 2011/1/17 Michael Jackson mike.jack...@bluequartz.net: I have the following code: if ( ${CMAKE_SIZEOF_VOID_P} EQUAL 8 ) set(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-Win64) elseif( ${CMAKE_SIZEOF_VOID_P} EQUAL 4 )