[cmake-developers] [CMake 0014339]: CheckCXXCompilerFlag seems to have problems with XL and BCC
The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=14339 == Reported By:Rolf Eike Beer Assigned To: == Project:CMake Issue ID: 14339 Category: Modules Reproducibility:have not tried Severity: minor Priority: normal Status: new == Date Submitted: 2013-08-04 06:53 EDT Last Modified: 2013-08-04 06:53 EDT == Summary:CheckCXXCompilerFlag seems to have problems with XL and BCC Description: http://open.cdash.org/testDetails.php?test=202113167build=2987847 http://open.cdash.org/testDetails.php?test=202039283build=2987228 In both cases I doubt that -std=cxx11 is a valid compiler flag, so this shouldn't have been detected as valid. == Issue History Date ModifiedUsername FieldChange == 2013-08-04 06:53 Rolf Eike Beer New Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Introducing the ${Foo_TARGETS} variable (IntroduceTARGETSVariable branch)
Alexander Neundorf wrote:
On Monday 29 July 2013, Stephen Kelly wrote:
Alexander Neundorf wrote:
So it can be used in tll() calls to link against the library (package).
What makes it differ from Foo_LIBRARIES, is that CMake checks that each
of the items listed in this variable
* is an existing target
* has the INTERFACE_INCLUDE_DIRS property set.
Are you really certain it is always an error for a target to not set
this?
I think so.
If I want to use symbols from a library, I should include its headers, and
for that the include dirs need to be known.
For header-only libraries even more.
Are there cases where this is not the case ?
There will/can be in the future.
add_library(picon INTERFACE)
set_property(TARGET picon INTERFACE_POSITION_INDEPENDENT_CODE ON)
add_library(picoff INTERFACE)
set_property(TARGET picoff INTERFACE_POSITION_INDEPENDENT_CODE ON)
...
# Use linking to psuedo targets to enable compiler options:
add_executable(foo main.cpp)
target_link_libraries(foo PRIVATE picon)
add_executable(bar main.cpp)
target_link_libraries(bar PRIVATE picoff)
Or:
add_library(cxx11features INTERFACE)
set_property(TARGET cxx11features
INTERFACE_COMPILE_OPTIONS
$$CXX_COMPILER_ID:GNU:-std=c++0x
$$CXX_COMPILER_ID:Clang:-std=c++11
)
set(IS_GNU $CXX_COMPILER_ID:GNU)
set(IS_46 $VERSION_GREATER:$CXX_COMPILER_VERSION,4.6)
set_property(TARGET cxx11features
INTERFACE_COMPILE_DEFINITIONS
$$AND:${IS_GNU},${IS_46}:CXXFEATURES_NULLPTR_FOUND
)
# Possibly also specify libcxx compiler option if using
# recent clang on apple.
...
add_executable(foo main.cpp)
target_link_libraries(foo cxx11features)
Thanks,
Steve.
--
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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Suspicious Clang versions
That's a Rogue Research machine. Don't doubt it. :-) Sean McBride uses custom builds of clang on some of the Rogue machines. I'm sure he'll chime in here. (If he hasn't already, and I just missed it...) -Original Message- From: Rolf Eike Beer e...@sf-mail.de To: cmake-developers cmake-developers@cmake.org Sent: Sat, Aug 3, 2013 11:05 pm Subject: [cmake-developers] Suspicious Clang versions http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Especially as http://open.cdash.org/testDetails.php?test=201937829build=2986379 (MacOS 10.8) shows 3.4.0. But since even 3.4 does not seem to be released I wonder what's going on there? Eike -- -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Suspicious Clang versions
Yeah, it's confusing... :( http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Apple has their own fork/branch of clang which they use in Xcode. AFAICT it's not so different from the open source one, it's probably more to do with them not wanting to tie Xcode's release schedule to clang's. Anyway, very confusingly, Apple uses their own version numbering scheme. So that's Apple clang 4.0. It comes with whatever version of Xcode that machine's running (4.4 I think?). Especially as http://open.cdash.org/testDetails.php?test=201937829build=2986379 (MacOS 10.8) shows 3.4.0. But since even 3.4 does not seem to be released I wonder what's going on there? That one is the open source clang, which I build from svn. It's not from Xcode. It's my 'bleeding edge' build machine. clang is always getting stricter and getting new warnings, so this help us fix them before a CMake/VTK/ITK release. Sean -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
