Re: [CMake] CMake 2.8.8/9 and Xcode 4.4
Brad fixed this today, and if the nightly builds work overnight tonight, nightly builds of CMake will be able to use xcode-select to dynamically determine the location of Xcode. This fix will be in the next official CMake release, 2.8.10. On Fri, Aug 10, 2012 at 8:44 PM, Etuka Onono wrote: > By xcode plist, I mean xcode's version.plist... > > On 11 Aug 2012, at 01:38, Etuka Onono wrote: > >> I have had trouble building xcode projects from Cmake since xcode changed >> its location from /Developer/Application. >> Having built and played with my own cmake version, I now see that the reason >> I have not been able to generate xcode projects is because I have chosen to >> install xcode in a different directory to /Application - I have >> /Developer/Xcode.app. >> >> search paths for the xcode plist are hardcoded in >> cmGlobalXCodeGenerator::New ( (cmGlobalXCodeGenerator.cxx,). >> >> Michael Toy (thanks Michael!) pointed out that the path for the Xcode plist >> is hardcoded in cmGlobalXCodeGenerator::New, whereas other cmake >> deductions, such as where to find command line tools and the like, use >> xcode-select in Darwin.cmake. I can work around the plist location for now, >> but the location should be deduced as well to prevent bozos like me getting >> lost. >> >> Thanks, >> >> Etuka > > -- > > 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
Re: [CMake] CMake 2.8.8/9 and Xcode 4.4
By xcode plist, I mean xcode's version.plist... On 11 Aug 2012, at 01:38, Etuka Onono wrote: > I have had trouble building xcode projects from Cmake since xcode changed its > location from /Developer/Application. > Having built and played with my own cmake version, I now see that the reason > I have not been able to generate xcode projects is because I have chosen to > install xcode in a different directory to /Application - I have > /Developer/Xcode.app. > > search paths for the xcode plist are hardcoded in cmGlobalXCodeGenerator::New > ( (cmGlobalXCodeGenerator.cxx,). > > Michael Toy (thanks Michael!) pointed out that the path for the Xcode plist > is hardcoded in cmGlobalXCodeGenerator::New, whereas other cmake deductions, > such as where to find command line tools and the like, use xcode-select in > Darwin.cmake. I can work around the plist location for now, but the location > should be deduced as well to prevent bozos like me getting lost. > > Thanks, > > Etuka -- 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
[CMake] CMake 2.8.8/9 and Xcode 4.4
I have had trouble building xcode projects from Cmake since xcode changed its location from /Developer/Application. Having built and played with my own cmake version, I now see that the reason I have not been able to generate xcode projects is because I have chosen to install xcode in a different directory to /Application - I have /Developer/Xcode.app. search paths for the xcode plist are hardcoded in cmGlobalXCodeGenerator::New ( (cmGlobalXCodeGenerator.cxx,). Michael Toy (thanks Michael!) pointed out that the path for the Xcode plist is hardcoded in cmGlobalXCodeGenerator::New, whereas other cmake deductions, such as where to find command line tools and the like, use xcode-select in Darwin.cmake. I can work around the plist location for now, but the location should be deduced as well to prevent bozos like me getting lost. Thanks, Etuka -- 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
[CMake] Bug fix requests for the *next* release of CMake...
Hi all, Replies requested. Short replies only. Read on. Just a short reply with bug numbers or links to the bugs is all we need here. Example one-line reply: http://public.kitware.com/Bug/view.php?id=13463 Please move specific discussions into the bugs themselves or start a new thread to talk about it... Replies on this thread should just be a collector for bug numbers. We are aiming for approximately quarterly releases from now on, scheduling them every 3 to 4 months. The next release of CMake will likely be version 2.8.10, scheduled to have an "rc1" release candidate on Wed. October 17, 2012 -- just 9 weeks from next Wednesday. If you have a particular issue that you think should be fixed for inclusion in 2.8.10, please bring it up within the next two weeks. Ideally, each issue will be discussed as needed on the mailing list to come to any consensus about what should be done to fix it, and then an entry in the bug tracker may be used to keep it on the radar screen, and to track activity related to it. You can see what's on the roadmap for this release here: http://public.kitware.com/Bug/roadmap_page.php?version_id=100 Patches are always welcome. Patches that include testing of any new features, or tests that prove a bug is really fixed on the dashboards, (basically any patch with testing) is preferred over a patch with no testing. Also, if you are *adding* code, then you also probably need to add *tests* of that code, so that the coverage percentage stays as is or rises. Please discuss issues here as needed, and add notes to existing issues in the bug tracker that you are interested in seeing fixed -- we will be looking at the mailing list and activity in the bug tracker to help prioritize the bug fixes that will occur in the near future. Thanks, David Cole Kitware, Inc. P.S. - as a nice summary of what we accomplished in the CMake 2.8.9 release, see here: http://public.kitware.com/Bug/changelog_page.php?version_id=93 -- it currently lists 74 issues that we resolved: nice job, everybody! (Many of those were specifically addressed because somebody asked for it right here on the mailing list... Don't be shy!) -- 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
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
Agreed on all points. -- Mike Jackson On Aug 10, 2012, at 2:52 PM, Bill Hoffman wrote: > On 8/10/2012 2:30 PM, Michael Jackson wrote: >> 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. >> > > We never printed a special warning when Xcode was not installed in the past? > Why now? > >> 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. >> > cmake-gui to date has no platform specific code in it... We could have the > check for compiler on the mac complain. I think we might do that with nmake > on windows... > >> >> * 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. > > Sure there is, and the word on the web for all other people wanting this > compiler is to do just that. A quick google search shows this: > > > http://www.macobserver.com/tmo/article/install_the_command_line_c_compilers_in_os_x_lion/ > > http://technopracticum.wordpress.com/2012/05/08/installing-a-command-line-c-compiler-for-mac-os-x-10-7-lion/ > > http://superuser.com/questions/400179/gcc-on-os-x-lion-with-xcode-4-3-1 > > http://stackoverflow.com/questions/10002981/g-wont-work-on-lion > > http://apple.stackexchange.com/questions/48099/gcc-not-found-but-xcode-is-installed > > http://stackoverflow.com/questions/9329243/xcode-4-4-command-line-tools > > http://www.quora.com/Mac-OS-X-10-7-Lion/What-is-the-path-for-gcc-in-Mac-OS-X-Lion > > > Basically, where did gcc go? You need to install the command line tools... > Seems to be the question and answer spinning around the web. This was a HUGE > change by Apple to make the command line tools not install by default with > Xcode. That is my opinion and I stand by it.. :) > > > -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
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
On 8/10/2012 2:30 PM, Michael Jackson wrote: 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. We never printed a special warning when Xcode was not installed in the past? Why now? 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. cmake-gui to date has no platform specific code in it... We could have the check for compiler on the mac complain. I think we might do that with nmake on windows... * 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. Sure there is, and the word on the web for all other people wanting this compiler is to do just that. A quick google search shows this: http://www.macobserver.com/tmo/article/install_the_command_line_c_compilers_in_os_x_lion/ http://technopracticum.wordpress.com/2012/05/08/installing-a-command-line-c-compiler-for-mac-os-x-10-7-lion/ http://superuser.com/questions/400179/gcc-on-os-x-lion-with-xcode-4-3-1 http://stackoverflow.com/questions/10002981/g-wont-work-on-lion http://apple.stackexchange.com/questions/48099/gcc-not-found-but-xcode-is-installed http://stackoverflow.com/questions/9329243/xcode-4-4-command-line-tools http://www.quora.com/Mac-OS-X-10-7-Lion/What-is-the-path-for-gcc-in-Mac-OS-X-Lion Basically, where did gcc go? You need to install the command line tools... Seems to be the question and answer spinning around the web. This was a HUGE change by Apple to make the command line tools not install by default with Xcode. That is my opinion and I stand by it.. :) -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
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
Yes, it's true, but now there's extra required beyond simply "installing Xcode". Brad's partially addressed the problem here today, with this commit, now in 'next': http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e88bae77c3388a5b474b081e572004f02772d162 However, in order to run on one of these new systems, and get a good command line build going, you probably have to do something like: xcrun bash cmake in the "Xcode environment" Ctrl+D to go back to the non-Xcode env So. just like all the other makefile generators, you have a sane "build env" at CMake configure time. Using xcode-select should get us part way there, but now that we have this new world of command line tools separate from "installing Xcode", we do have to adapt to it somehow. Having these emails in the mailing list archive is at least a start to get people thinking in the right direction. Cheers, David P.S. -- thanks for chiming in and being a little pedantic... good word for a Friday :-) On Fri, Aug 10, 2012 at 2:30 PM, Michael Jackson wrote: > 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 JacksonPrincipal Software Engineer > BlueQuartz SoftwareDayton, Ohio > mike.jack...@bluequartz.net 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 -- 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
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
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 JacksonPrincipal Software Engineer BlueQuartz SoftwareDayton, Ohio mike.jack...@bluequartz.net 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
[CMake] nested variables with @ONLY: ${${PROJECT}_FLAGS} vs. @@PROJECT@_FLAGS@
When templating ProjectConfig.cmake files, I like to have
${MY_CMAKE_VARIABLE} stuff in the output, so I use @ONLY at configure
time, e.g.,
configure_file(ProjectConfig.cmake.in
"${PROJECT_BINARY_DIR}/ProjectConfig.cmake" @ONLY)
The @-syntax in ProjectConfig.cmake.in works okay most of the time,
but fails when there are nested variables. Withotu @ONLY, a statement
like
${${PROJECT_NAME}_FLAGS}
would first be expanded to
${MyProject_FLAGS}
and then
.
The syntax
@@PROJECT_NAME@_FLAGS@
merely expands @PROJECT_NAME@, though.
Is there are workaround for this?
Cheers,
Nico
--
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
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
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
Re: [CMake] CMake 2.8.8-2.8.9 - Generate Xcode 4.4.1 project
There is never any reason to run CMake as root or to use sudo to
configure a project build tree with CMake.
Mixing and matching use of sudo/non-sudo within the same build tree is
simply asking for file permissions problems.
On Fri, Aug 10, 2012 at 10:22 AM, Romain LEGUAY wrote:
> Hi again!
>
> I succeed to generate a Xcode project (with a normal user) with cmake-gui.
> I hope this new information can lead you to the solution.
>
> Regards,
> Romain
>
> Le 10/08/12 11:34, Romain LEGUAY a écrit :
>
> Hi everyone!
>
> I have a problem to generate a Xcode project.
>
> I completely remove Xcode 4.4.1 (and command line tools) and CMake 2.8.9.
>
> I reinstall Xcode 4.4.1 and command line tools and CMake 2.8.9.
>
> I had this error when I try to generate a XCode project ('cmake -GXcode .'):
> xcodebuild: error: developer tools not installed; download from
>
> Thanks to Yu You, I apply this command:
> sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
>
> And now I have the same error as previously:
> cmake -GXcode .
> -- The CXX compiler identification is GNU 4.2.1
> -- Checking whether CXX compiler has -isysroot
> -- Checking whether CXX compiler has -isysroot - yes
> -- Checking whether CXX compiler supports OSX deployment target flag
> -- Checking whether CXX compiler supports OSX deployment target flag - yes
> -- Check for working CXX compiler using: Xcode
> -- Check for working CXX compiler using: Xcode -- broken
> CMake Error at /Applications/CMake
> 2.8-9.app/Contents/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:45
> (MESSAGE):
> The C++ compiler "/usr/bin/llvm-g++" is not able to compile a simple test
> program.
>
> It fails with the following output:
>
>Change Dir: /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
>
> Run Build Command:/Applications/CMake\ 2.8-9.app/Contents/bin/cmakexbuild
> -project CMAKE_TRY_COMPILE.xcodeproj build -target
> cmTryCompileExec2932044491 -configuration Debug
>
> === BUILD NATIVE TARGET cmTryCompileExec2932044491 OF PROJECT
> CMAKE_TRY_COMPILE WITH CONFIGURATION Debug ===
>
> Check dependencies
>
> CompileC
>
> CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.o
> testCXXCompiler.cxx normal x86_64 c++
> com.apple.compilers.llvm.clang.1_0.compiler
>
> cd /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
> /Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 -x c++
> -arch x86_64 -fmessage-length=0 -Wno-trigraphs -fpascal-strings -O0
> -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type
> -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors
> -Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function
> -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value
> -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants
> -Wno-conversion -Wno-sign-compare -Wno-shorten-64-to-32 -Wno-newline-eof
> -Wc++11-extensions "-DCMAKE_INTDIR=\"Debug\"" -i2012-08-10 11:13:51.477
> xcodebuild[1087:3603] DVTAssertions: Warning in
> /SourceCache/IDEXcode3ProjectSupport/IDEXcode3ProjectSupport-1559/Xcode3Sources/XcodeIDE/Frameworks/DevToolsBase/pbxcore/SpecificationTypes/XCCommandLineToolSpecification.m:810
>
> Details: Unable to get message category info for tool
> '/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2'.
>
> Reason: i686-apple-darwin11-llvm-gcc-4.2: no input files
>
> Object:
>
> Method: -messageCategoryInfoForExecutablePath:
>
> Thread: {name = (null), num = 4}
>
> Please file a bug at http://bugreport.apple.com with this warning message
> and any useful information you can provide.
>
> sysroot
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
> -fasm-blocks -Wdeprecated-declarations -Winvalid-offsetof
> -mmacosx-version-min=10.7 -Wno-sign-conversion
> -I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug/include
>
> -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
>
> -I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources/x86_64
>
> -I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources
> -Wmost -Wno-four-char-constants -Wno-unknown-pragmas
> -F/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug -g -MMD
> -MT dependencies -MF
>
> /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.d
> --serialize-diagnostics
>
> /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.dia
> -c
>
> /Users/rleguay/temp/t
Re: [CMake] CMake 2.8.8-2.8.9 - Generate Xcode 4.4.1 project
Hi again!
I succeed to generate a Xcode project (with a normal user) with cmake-gui.
I hope this new information can lead you to the solution.
Regards,
Romain
Le 10/08/12 11:34, Romain LEGUAY a écrit :
Hi everyone!
I have a problem to generate a Xcode project.
I completely remove Xcode 4.4.1 (and command line tools) and CMake 2.8.9.
I reinstall Xcode 4.4.1 and command line tools and CMake 2.8.9.
I had this error when I try to generate a XCode project ('cmake
-GXcode .'):
xcodebuild: error: developer tools not installed; download from
Thanks to Yu You, I apply this command:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
And now I have the same error as previously:
cmake -GXcode .
-- The CXX compiler identification is GNU 4.2.1
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler using: Xcode
-- Check for working CXX compiler using: Xcode -- broken
CMake Error at /Applications/CMake
2.8-9.app/Contents/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:45
(MESSAGE):
The C++ compiler "/usr/bin/llvm-g++" is not able to compile a simple
test
program.
It fails with the following output:
Change Dir: /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
Run Build Command:/Applications/CMake\
2.8-9.app/Contents/bin/cmakexbuild
-project CMAKE_TRY_COMPILE.xcodeproj build -target
cmTryCompileExec2932044491 -configuration Debug
=== BUILD NATIVE TARGET cmTryCompileExec2932044491 OF PROJECT
CMAKE_TRY_COMPILE WITH CONFIGURATION Debug ===
Check dependencies
CompileC
CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.o
testCXXCompiler.cxx normal x86_64 c++
com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 -x c++
-arch x86_64 -fmessage-length=0 -Wno-trigraphs -fpascal-strings -O0
-Wno-missing-field-initializers -Wno-missing-prototypes
-Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual
-Wno-exit-time-destructors -Wformat -Wno-missing-braces -Wparentheses
-Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter
-Wno-unused-variable -Wunused-value -Wno-uninitialized
-Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants
-Wno-conversion -Wno-sign-compare -Wno-shorten-64-to-32
-Wno-newline-eof -Wc++11-extensions "-DCMAKE_INTDIR=\"Debug\""
-i2012-08-10 11:13:51.477 xcodebuild[1087:3603] DVTAssertions:
Warning in
/SourceCache/IDEXcode3ProjectSupport/IDEXcode3ProjectSupport-1559/Xcode3Sources/XcodeIDE/Frameworks/DevToolsBase/pbxcore/SpecificationTypes/XCCommandLineToolSpecification.m:810
Details: Unable to get message category info for tool
'/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2'.
Reason: i686-apple-darwin11-llvm-gcc-4.2: no input files
Object:
Method: -messageCategoryInfoForExecutablePath:
Thread: {name = (null), num = 4}
Please file a bug at http://bugreport.apple.com with this warning
message
and any useful information you can provide.
sysroot
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
-fasm-blocks -Wdeprecated-declarations -Winvalid-offsetof
-mmacosx-version-min=10.7 -Wno-sign-conversion
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug/include
-I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources/x86_64
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources
-Wmost -Wno-four-char-constants -Wno-unknown-pragmas
-F/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug -g -MMD
-MT dependencies -MF
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.d
--serialize-diagnostics
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.dia
-c
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
-o
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.o
i686-apple-darwin11-llvm-gcc-4.2:
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.dia:
No such file or directory
cc1plus:
[CMake] CMake 2.8.8-2.8.9 - Generate Xcode 4.4.1 project
Hi everyone!
I have a problem to generate a Xcode project.
I completely remove Xcode 4.4.1 (and command line tools) and CMake 2.8.9.
I reinstall Xcode 4.4.1 and command line tools and CMake 2.8.9.
I had this error when I try to generate a XCode project ('cmake -GXcode .'):
xcodebuild: error: developer tools not installed; download from
Thanks to Yu You, I apply this command:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
And now I have the same error as previously:
cmake -GXcode .
-- The CXX compiler identification is GNU 4.2.1
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler using: Xcode
-- Check for working CXX compiler using: Xcode -- broken
CMake Error at /Applications/CMake
2.8-9.app/Contents/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:45
(MESSAGE):
The C++ compiler "/usr/bin/llvm-g++" is not able to compile a simple test
program.
It fails with the following output:
Change Dir: /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
Run Build Command:/Applications/CMake\ 2.8-9.app/Contents/bin/cmakexbuild
-project CMAKE_TRY_COMPILE.xcodeproj build -target
cmTryCompileExec2932044491 -configuration Debug
=== BUILD NATIVE TARGET cmTryCompileExec2932044491 OF PROJECT
CMAKE_TRY_COMPILE WITH CONFIGURATION Debug ===
Check dependencies
CompileC
CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.o
testCXXCompiler.cxx normal x86_64 c++
com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp
/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 -x c++
-arch x86_64 -fmessage-length=0 -Wno-trigraphs -fpascal-strings -O0
-Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type
-Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors
-Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function
-Wno-unused-label -Wno-unused-parameter -Wno-unused-variable
-Wunused-value -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow
-Wno-four-char-constants -Wno-conversion -Wno-sign-compare
-Wno-shorten-64-to-32 -Wno-newline-eof -Wc++11-extensions
"-DCMAKE_INTDIR=\"Debug\"" -i2012-08-10 11:13:51.477
xcodebuild[1087:3603] DVTAssertions: Warning in
/SourceCache/IDEXcode3ProjectSupport/IDEXcode3ProjectSupport-1559/Xcode3Sources/XcodeIDE/Frameworks/DevToolsBase/pbxcore/SpecificationTypes/XCCommandLineToolSpecification.m:810
Details: Unable to get message category info for tool
'/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2'.
Reason: i686-apple-darwin11-llvm-gcc-4.2: no input files
Object:
Method: -messageCategoryInfoForExecutablePath:
Thread: {name = (null), num = 4}
Please file a bug at http://bugreport.apple.com with this warning message
and any useful information you can provide.
sysroot
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
-fasm-blocks -Wdeprecated-declarations -Winvalid-offsetof
-mmacosx-version-min=10.7 -Wno-sign-conversion
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug/include
-I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources/x86_64
-I/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/DerivedSources
-Wmost -Wno-four-char-constants -Wno-unknown-pragmas
-F/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/Debug -g -MMD
-MT dependencies -MF
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.d
--serialize-diagnostics
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.dia
-c
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
-o
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.o
i686-apple-darwin11-llvm-gcc-4.2:
/Users/rleguay/temp/test/DummyProject/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec2932044491.build/Objects-normal/x86_64/testCXXCompiler.dia:
No such file or directory
cc1plus: error: unrecognized command line option
"-Wno-exit-time-destructors"
cc1plus: error: unrecognized command line option "-Wc++11-extensions"
cc1plus: error: unrecognized command line option "-Wno-sign-convers
Re: [CMake] Eclipse generator on mac
Hi, Can you please post the output of the following command here ? > > g++ -v -E -x c++ -dD /dev/null > > (or clang if you're using that). > > It would be even better if you could create a bug report at > http://public.kitware.com/Bug for this and put the information there :-) > I've created a bug entry: http://public.kitware.com/Bug/view.php?id=13464 > Is there something I can do about this? Seeing everything three times is > > > really confusing. > > Ah, this is this one: > > http://public.kitware.com/Bug/view.php?id=13189 > I thought this would be a good idea but know it seems people are more > complaining about it than liking it... > Yeah this is the one. When relying on Eclipse and the Eclipse static analyser I can understand the complains. > > I am talking about the Source project. Generated > > > using -DCMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT=TRUE. > > > If I add the team provided myself it all works ok, but this makes it > > > impossible to regenerate the project files. Can CMake add the team > provider > > > during generation? > > Probably, I'll have a look. > > Can you create a ticket at http://public.kitware.com/Bug for cmake for > that ? > http://public.kitware.com/Bug/view.php?id=13465 -- Met vriendelijke groet, Alexander Broekhuis -- 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
