Few pointers talking about the issue:
- http://yourmacguy.wordpress.com/2009/08/24/boot-snow-leopard-64-bit/
- http://arstechnica.com/apple/2009/08/mac-os-x-10-6/5/
Hth
Jc
On Tue, Feb 5, 2013 at 11:00 AM, Sean McBride wrote:
> On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said:
>
> >And
On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said:
>And the reason it says i386 is that CPACK_SYSTEM_NAME defaults to the
>output of uname -p which on OS X 10.7.5 is 'i386'
>
>So CMake is behaving as documented, and OS X is wrong ;-) Quelle Surprise!
OS X returns 'i386' for 'uname -p' deliber
I meant that when I build cmake and then ran 'make package' it cmake out
i386, even though by default it only generates 64-bit binaries.
Jean-Christophe pointed out that on Kitware's builds they override this
with a better CPACK_SYSTEM_NAME.
And the reason it says i386 is that CPACK_SYSTEM_NAME d
What do you mean by "it's wrong"?
It's a universal binary with x86_64 being one of them.
On Feb 5, 2013, at 10:04 AM, Jean-Christophe Fillion-Robin
wrote:
> Hi Kent,
>
> Probably because the CPACK_SYSTEM_NAME is explicitly specified. See
> http://cmake.org/gitweb?p=cmake.git;a=blob;f=Utili
Hi Kent,
Probably because the CPACK_SYSTEM_NAME is explicitly specified. See
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Utilities/Release/dashmacmini5_release.cmake;h=36b095287e80d26ed1b684b6c1a69d9bda1963ba;hb=HEAD#l19
Hth
Jc
On Tue, Feb 5, 2013 at 9:47 AM, Kent Williams wrote:
> Building o
Building on OS X 10.7.5 with XCode 4.5.2
Compiling with default compiler Apple clang version 4.1
(tags/Apple/clang-421.11.66)
The packages available for download on cmake.org are named
http://www.cmake.org/files/v2.8/cmake-2.8.10.2-Darwin64-universal.dmg
My question is this: how is the architectu
