[cmake-developers] [CMake 0014885]: Linking to frameworks in Xcode generator is buggy

The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=14885 == Reported By:Aggelos Kolaitis Assigned To:

[cmake-developers] [CMake 0014886]: [PATCH] Make documentation generation python3 compatible.

The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=14886 == Reported By:Uwe L. Korn Assigned To:

[cmake-developers] Topic UseSWIG-guess_module_name

Hi, I wondered why my topic UseSWIG-guess_module_name to fix #10080 was not merged yet. Did I miss a negative review ? J. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support

[cmake-developers] [CMake 0014887]: CMake fails to compile - error: use of undeclared identifier 'abi'

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14887 == Reported By:cakersq Assigned To:

Re: [cmake-developers] Topic UseSWIG-guess_module_name

On 04/18/2014 06:19 AM, Julien Schueller wrote: I wondered why my topic UseSWIG-guess_module_name to fix #10080 was not merged yet. Did I miss a negative review ? Yes: http://www.cmake.org/Bug/view.php?id=10080#c35708 -Brad -- Powered by www.kitware.com Please keep messages on-topic

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

On 04/18/2014 03:07 AM, Rolf Eike Beer wrote: what about nuking at least all control characters and whitespace from variable names in 3.1? I don't think that anyone has used them on purpose, and accidentially using them will only cause trouble. If we're going to change this I don't want it

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

Brad King wrote: On 04/18/2014 03:07 AM, Rolf Eike Beer wrote: what about nuking at least all control characters and whitespace from variable names in 3.1? I don't think that anyone has used them on purpose, and accidentially using them will only cause trouble. If we're going to

[cmake-developers] [CMake 0014888]: FeatureSummary does not recognize Qt 4

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14888 == Reported By:Peter Kuemmel Assigned To:

Re: [cmake-developers] Default generator

On 2014-04-17 07:56, Peter Kümmel wrote: Is there a way to configure the default generator for command-line cmake calls? If you're using bash: 'alias cmake=cmake -GNinja' (for example)... I'm not sure how folks would feel about having a different default built into the cmake binary itself

[cmake-developers] [CMake 0014889]: Cpack crashes when issuing a bad Wix Patch

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14889 == Reported By:Nicolas H. Assigned To:

[cmake-developers] [CMake 0014890]: cpack, wix, It's not possible to patch directories (patch attached)

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14890 == Reported By:Nicolas H. Assigned To:

Re: [cmake-developers] [PATCH] remove x placeholder from STREQUAL operands

On Fri, Apr 18, 2014 at 10:06:36 -0400, Matthew Woehlke wrote: Where a variable is created (e.g. the SET command), presumably. Internally-created variables would then be missed. string(TOUPPER mystr varname with spaces) I don't think the performance hit should be so bad if only writes are

Re: [cmake-developers] target_compile_features remaining issues

On 04/15/2014 11:39 AM, Stephen Kelly wrote: I think we should reverse our earlier decision and go ahead and add an error whenever a feature is requested that we do not know *is* supported for the current {id, version}. Yes, I think that makes sense. Such an error can be relaxed in the

[cmake-developers] [CMake 0014891]: CMake incorrectly handles path to gfortran compiler containing spaces

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14891 == Reported By:vitaut Assigned To:

Re: [cmake-developers] Learning from the source

Hi Ingwie, It depends on what exactly you're referring to. If you mean calls to find_library and find_path, those usually have a set of known directories and patterns that they search for. However, if you're referring to the configure time checks line CHECK_INCLUDE_FILE and related functions,