I am going to be *very* pedantic here so you may slap me upside the head. The 
compiler was never "just there" on OS X. It has *always* required the 
installation of the developer tools. With 10.8 it would seem that installing 
"Xcode" is not enough to get the command line tools any more. The developer now 
needs to know to also install the "Command Line Tools" in addition (or in leau 
of*) Xcode.

About the best CMake-Gui could do is detect you are on OS X 10.8 or greater and 
ask the developer if they have in fact installed the command line tools or used 
Xcode-select (or what ever it is) to select the proper version of Xcode. Beyond 
that we are getting to the point that Windows is at where one is expected to 
have a fully functioning Visual Studio Command Prompt for CMake to generate 
Visual Studio Projects. A pain yes, but a fact of life.


* There is actually a separate download for the command line tools that it 
looks like it could be installed without Xcode though I have not actually tried 
this myself.

Have a nice weekend.
___________________________________________________________
Mike Jackson                    Principal Software Engineer
BlueQuartz Software                            Dayton, Ohio
[email protected]              www.bluequartz.net

On Aug 10, 2012, at 1:55 PM, Bill Hoffman wrote:

> On 8/9/2012 6:04 PM, Jerry Krinock wrote:
> 
>> Although not requiring installation of Xcode's command-line tools
>> would be nice, at a minimum, CMake's runtime, or at least its
>> installer, should check for any needed prerequisites and inform the
>> user if a prerequisite is missing.  I've spent several hours in the
>> last few days trying to figure out why CMake 2.8.8 just wouldn't work
>> on a new Mac, until someone pointed out to me that it was necessary
>> to install Xcode's command-line tools.  The error messages I received
>> from CMake just added to the confusion.
>> 
>> 
> 
> Just curious what would an autotools or makefile based project do on a new 
> mac?  I am guessing it will not print anything other than, there is no 
> compiler found.  That said we will try to make cmake print a helpful message 
> or work out of the box.  I am just wondering how other projects are handling 
> the sudden disappearance of the compiler from the command line...  (it has 
> been there since the very first OSX Mac...)
> 
> -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

--

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

Reply via email to