[cmake-developers] [CMake 0011700]: bootstrap fails when using gcc, g++
The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=11700 == Reported By:Brian Lewis Assigned To: == Project:CMake Issue ID: 11700 Category: Modules Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-01-14 12:29 EST Last Modified: 2011-01-14 12:29 EST == Summary:bootstrap fails when using gcc, g++ Description: $ CC=/usr/local/gcc-3.3.1/bin/gcc CXX=/usr/local/gcc-3.3.1/bin/g++ ./bootstrap make eventually fails with gcc: `-b' must come at the start of the command line because the flags set in Modules/Platform/SCO_SV.cmake are only appropriate for the default SCO compiler. Additional Information: The attached patch fixes the issue for me. Thanks. == Issue History Date ModifiedUsername FieldChange == 2011-01-14 12:29 Brian LewisNew Issue 2011-01-14 12:29 Brian LewisFile Added: sco-gcc.patch == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On 01/14/2011 01:28 PM, Manuel Klimek wrote: I'm fine with making it optional. Another option would be to make it hidden, as we want tools and not users to interact with it. Your call. Actually, with an option then the file name becomes moot: $ cmake ... -DCMAKE_EXPORT_COMPILE_RULES=compile_commands.json Okay. Does JSON support any kind of schema? Why would we need a schema? For documenation? Or do you plan to use meta-tools on it? Just curious. Pretty much every time I've ever written code that generates a .xml file someone eventually comes along asking for a schema. -Brad ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On Fri, Jan 14, 2011 at 10:53 AM, Brad King brad.k...@kitware.com wrote: On 01/14/2011 01:28 PM, Manuel Klimek wrote: I'm fine with making it optional. Another option would be to make it hidden, as we want tools and not users to interact with it. Your call. Actually, with an option then the file name becomes moot: $ cmake ... -DCMAKE_EXPORT_COMPILE_RULES=compile_commands.json Hm, I was actually going more for a bool option - I'd really like a file name that's easily recognizable by a tool with minimal user configuration. We can of course put in a second option with the file name with a good default. Cheers, /Manuel Okay. Does JSON support any kind of schema? Why would we need a schema? For documenation? Or do you plan to use meta-tools on it? Just curious. Pretty much every time I've ever written code that generates a .xml file someone eventually comes along asking for a schema. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On 01/14/2011 01:58 PM, Manuel Klimek wrote: Hm, I was actually going more for a bool option - I'd really like a file name that's easily recognizable by a tool with minimal user configuration. Sure. If you are trying to create a standard file name/format then you should choose a marketable name for it. That will make it recognizable, distinct, googleable, and not tied to CMake or any build system. It will also provide a meaningful name for the CMake option: $ cmake ... -DCMAKE_EXPORT_$coolname=1 -Brad ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On 01/14/2011 05:46 PM, Manuel Klimek wrote:
I'm currently trying to figure out the best point where to add that
option...
In the cmMakefileTargetGenerator you can test for the option with
this-Makefile-IsOn(...)
Is there a good example I can base it on? So far I followed
CMAKE_BUILD_TYPE through the code base, which suggests that I need to
- find a .cmake file in modules in which I can put the option
- document it in cmDocumentVariables
Probably like CMAKE_VERBOSE_MAKEFILE which is another option to the
Makefile generator. See CMakeGenericSystem.cmake. Surround it by
if(${CMAKE_GENERATOR} MATCHES Make)
...
endif()
so that it only shows up for Makefile generators.
-Brad
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
