[cmake-developers] [CMake 0014893]: ENABLE_LANGUAGE(ASM_MASM) adds back default configuration types
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14893 == Reported By:Mattias Ljungstrom Assigned To: == Project:CMake Issue ID: 14893 Category: CMake Reproducibility:sometimes Severity: minor Priority: normal Status: new == Date Submitted: 2014-04-22 04:05 EDT Last Modified: 2014-04-22 04:05 EDT == Summary:ENABLE_LANGUAGE(ASM_MASM) adds back default configuration types Description: Under windows7, using Visual Studio 12 with target v120_xp. If I use ENABLE_LANGUAGE(ASM_MASM) after set(CMAKE_CONFIGURATION_TYPES Debug;Release;Final CACHE STRING FORCE) it will add back the default configuration types (minSizeRel and relWithDebInfo). This happens sometimes, it seems to depend on the cache somehow. Workaround is to move ENABLE_LANGUAGE(ASM_MASM) to start of config file. == Issue History Date ModifiedUsername FieldChange == 2014-04-22 04:05 Mattias LjungstromNew Issue == -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] target_compile_features remaining issues
On 04/21/2014 02:42 PM, Stephen Kelly wrote:
Brad King wrote:
Later CMake learns about the -std=c++11 flag for that compiler and
honors the CXX_STANDARD request by passing it. Now the compiler
has its extensions disabled and the project fails to build. This
was due to an update in CMake, not the project.
Is the same problem present with CMAKE_*_COMPILE_OPTIONS_{PIE,PIC,DLL} ?
Yes, but that is less fundamental than the language standard level.
We need a way for a project to say that it should not build unless
CMake knows how to nominally enable support for the given language
level.
This requirement is inconsistent with what people keep asking me for (namely
something like what the qmake CONFIG += c++11 does - enable a c++11 flag if
known, and do nothing if not), and is inconsistent with the decay- topic.
Yes, and the CXX_STANDARD property in the decay- topic satisfies this
use case. We just need another interface to specify that the standard
request is a strict requirement.
I think it be determined with code equivalent to
if (target-GetProperty(CXX_STANDARD == std::string(11)
!makefile-GetDefinition(CMAKE_CXX11_STANDARD_COMPILE_OPTION))
{
// FATAL_ERROR
}
Yes, so long as we set CMAKE_CXX11_STANDARD_COMPILE_OPTION to an empty
string on the compilers that support C++11 by default, like VS 12 (2013).
We would need to know the compile options of compilers supported by existing
versions of CMake, and ensure that the option is recorded for new
CompilerIds and new releases of existing compiler ids too.
Yes, but for projects that have this requirement it is better to fail
due to a missing setting in CMake than work accidentally and fail later
when CMake is updated. Even with a missing setting in CMake it will
typically be possible to work around it locally by adding the setting
to the cache.
However, I guess two different interfaces are needed if you want to ensure
the 'require some notion of C++11' concept.
Perhaps another boolean property like CXX_STANDARD_REQUIRED would work.
Thanks,
-Brad
--
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 the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.0-rc4 now ready for testing!
I am proud to announce the CMake 3.0 fourth release candidate. Sources and binaries are available at: http://www.cmake.org/files/v3.0/?C=M;O=D Documentation is available at: http://www.cmake.org/cmake/help/v3.0 Release notes appear below and are also published at http://www.cmake.org/cmake/help/v3.0/release/3.0.0.html Some of the more significant features of CMake 3.0 are: * Compatibility options supporting code written for CMake versions prior to 2.4 have been removed. * The CMake language has been extended with *Bracket Argument* and *Bracket Comment* syntax inspired by Lua long brackets. * The CMake documentation has been converted to reStructuredText and uses Sphix generation. * Generators for Visual Studio 10 (2010) and later were renamed to include the product year like generators for older VS versions: * Visual Studio 10 - Visual Studio 10 2010 * Visual Studio 11 - Visual Studio 11 2012 * Visual Studio 12 - Visual Studio 12 2013 This clarifies which generator goes with each Visual Studio version. The old names are recognized for compatibility. * A new CodeLite extra generator is available for use with the Makefile or Ninja generators. * A new Kate extra generator is available for use with the Makefile or Ninja generators. * The add_library() command learned a new INTERFACE library type. Interface libraries have no build rules but may have properties defining usage requirements and may be installed, exported, and imported. This is useful to create header-only libraries that have concrete link dependencies on other libraries. * The export() command learned a new EXPORT mode that retrieves the list of targets to export from an export set configured by the install(TARGETS) command EXPORT option. This makes it easy to export from the build tree the same targets that are exported from the install tree. * The project() command learned to set some version variables to values specified by the new VERSION option or to empty strings. See policy CMP0048. * Several long-outdated commands that should no longer be called have been disallowed in new code by policies: * Policy CMP0029 disallows subdir_depends() * Policy CMP0030 disallows use_mangled_mesa() * Policy CMP0031 disallows load_command() * Policy CMP0032 disallows output_required_files() * Policy CMP0033 disallows export_library_dependencies() * Policy CMP0034 disallows utility_source() * Policy CMP0035 disallows variable_requires() * Policy CMP0036 disallows build_name() --- Changes made since CMake 3.0.0-rc3: Brad King (10): Help: Revise and format policy CMP0025 and CMP0047 docs Do not warn by default when policy CMP0025 or CMP0047 is not set CMakeDetermineVSServicePack: Format documentation CMakeDetermineVSServicePack: Match versions more robustly CMakeDetermineVSServicePack: Add VS 11 update 4 Fortran: Detect pointer size on Intel archs with PGI (#14870) CMakeRCInformation: Do not mention 'Fortran' in documentation CMakeRCInformation: Recognize 'windres' tools with '.' in name (#14865) Drop /lib32 and /lib64 from link directories and RPATH (#14875) cmArchiveWrite: Handle NULL error string (#14882) Nils Gladitz (1): Policies: omit warnings about unset policies when they are actually set to NEW Robert Maynard (1): Qt4Macros: Make QT4_CREATE_MOC_COMMAND a function Sean McBride (1): create_test_sourcelist: Initialize variable at declaration Stephen Kelly (1): Help: Fix typo in cmake-qt manual. -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [ANNOUNCE] CMake 3.0-rc4 now ready for testing!
hi all, I am proud to announce the CMake 3.0 fourth release candidate. [snip] Changes made since CMake 3.0.0-rc3: i wonder, why did 90e22f8f713c not make it into rc4? it is a bug fix for the osx bundle generator, while the patch itself is trivial, the bug is a showstopper for me ... so it would be great if it can make it into rc4. thanks a lot, tim [1] https://github.com/Kitware/CMake/commit/90e22f8f713c -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [ANNOUNCE] CMake 3.0-rc4 now ready for testing!
On 04/22/2014 11:55 AM, Tim Blechmann wrote: i wonder, why did 90e22f8f713c not make it into rc4? it is a bug fix for the osx bundle generator, while the patch itself is trivial, the bug is a showstopper for me ... so it would be great if it can make it into rc4. Normally release candidates only get changes needed to fix bugs in new features, regressions from previous CMake releases, or environmental changes such as support for a new Visual Studio update. Any other changes, even bug fixes, have a risk of adding a new regression from a previous release candidate. This fix was none of the above. Still, this particular change has a very low risk of adding a regression so I've rebased it and merged to the 'release' branch: OS X: Fix Info.plist placement in a CFBundle http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=149ce5db It will be in the next candidate. -Brad -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Added CUBINFATBIN support to FindCUDA
It should already support cuda run time building by default. This is what the OBJ target is for CUDA_WRAP_SRCS. This is what cuda_add_library and cuda_add_executable do. On Fri, Apr 18, 2014 at 5:18 AM, Tobias Zirr opensou...@alphanew.netwrote: Hello, I just added CUBIN FATBIN compilation support to the FindCUDA module provided with the official CMake package. Up to now, the module has been restricted to compiling JIT/PTX cuda modules for device-only compilation and run-time module loading. The modified FindCUDA module is based on the latest version from the repository. Since I am unfamiliar with CMake's development infrastructure, I will simply submit it here, in hope that it either finds its way or results in additional directions being given. Best regards, Tobias -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- 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 the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
