[cmake-developers] Nightly dashboards from mug.neocisinc
The massive test failures on the Nightly from mug.neocisinc are my fault, so no need to investigate: I moved some scripts around yesterday, and missed one reference to the moved scripts, so ninja wasn't quite where it was supposed to be anymore... I'll get it fixed up today. Sorry, David C, -- 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] Nightly dashboards from mug.neocisinc
On 08/07/2013 07:32 AM, David Cole wrote: The massive test failures on the Nightly from mug.neocisinc are my fault, so no need to investigate: I moved some scripts around yesterday, and missed one reference to the moved scripts, so ninja wasn't quite where it was supposed to be anymore... I'll get it fixed up today. Great, thanks for letting us know! -Brad -- 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] Nightly dashboards from mug.neocisinc
The massive test failures on the Nightly from mug.neocisinc are my fault, so no need to investigate However, the 18 new warnings on that same dashboard are real, and specific to Visual Studio 2012 and later. As shown by this subsequent Experimental, where all the tests pass again after I fixed up my script: http://open.cdash.org/viewBuildError.php?type=1buildid=2991315 Looks like CMake needs Visual Studio 2012 (and 2013, too) Nightly Expected dashboards. (Feel free to move the mug.neocisinc dashboards into the Expected section if you'd like. I'll keep sending them for the foreseeable future.) David C. -- 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] Nightly dashboards from mug.neocisinc
On 08/07/2013 08:56 AM, David Cole wrote: Looks like CMake needs Visual Studio 2012 (and 2013, too) Nightly Expected dashboards. It had them once on dash5-vm5 but it ran out of disk space after a windows update and no longer works. We haven't had time to set up a new one. Once mug.neocisinc is clean I'll use that. Thanks. -Brad -- 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] Nightly dashboards from mug.neocisinc
On 08/07/2013 08:56 AM, David Cole wrote: However, the 18 new warnings on that same dashboard are real http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ae6a5ea5 -Brad -- 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
[cmake-developers] QNX QCC and _CMAKE_TOOLCHAIN_PREFIX
Hi there,
I can use a trivial toolchain file to compile for QNX with qcc:
SET(CMAKE_SYSTEM_NAME QNX)
SET(arch gcc_ntoarmv7le)
SET(CMAKE_C_COMPILER qcc -V${arch})
SET(CMAKE_CXX_COMPILER QCC -V${arch})
SET(CMAKE_FIND_ROOT_PATH $ENV{QNX_TARGET}/armle-v7 $ENV{QNX_TARGET})
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
However, I just noticed that when I build, /usr/bin/ar is used instead of
/home/stephen/bbndk/host_10_1_0_132/linux/x86/usr/bin/ntoarm-ar
When cross-compiling with g++, the _CMAKE_TOOLCHAIN_PREFIX is set by
examining the name of the compiler in CMakeDetermineCXXCompiler.cmake.
When using qcc, the COMPILER_BASENAME doesn't match, and the appropriate
prefix is not encoded into the name anyway. I was thinking that
CMakeDetermineCXXCompiler.cmake could be extended to handle QCC and use the
CMAKE_CXX_COMPILER_TARGET.
However, currently the CMAKE_CXX_COMPILER_TARGET needs to be of the form
gcc_ntoarch, not just ntoarch, so the QNX specific code in
CMakeDetermineCXXCompiler.cmake would have to account for that, and other
possible suffixes (the version is optional):
stephen@hal:~/bbndk/host_10_1_0_132/linux/x86/usr/bin$ ./QCC -V
cc: targets available in
/home/stephen/bbndk/host_10_1_0_132/linux/x86/etc/qcc:
4.6.3,gcc_ntoarmv7le_gpp
4.6.3,gcc_ntox86_gpp
4.6.3,gcc_ntox86_cpp
4.6.3,gcc_ntoarmv7le_cpp-ne
4.6.3,gcc_ntoarmv7le
4.6.3,gcc_ntox86_cpp-ne
4.6.3,gcc_ntox86(default)
4.6.3,gcc_ntoarmv7le_cpp
Can I extend the CMakeDetermineCXXCompiler.cmake with handling for that?
That would mean that with a recent enough cmake version, I can replace the
SET(arch gcc_ntoarmv7le)
SET(CMAKE_C_COMPILER qcc -V${arch})
SET(CMAKE_CXX_COMPILER QCC -V${arch})
in my toolchain file with
SET(arch gcc_ntoarmv7le)
SET(CMAKE_C_COMPILER qcc)
SET(CMAKE_CXX_COMPILER QCC)
SET(CMAKE_C_COMPILER_TARGET ${arch})
SET(CMAKE_CXX_COMPILER_TARGET ${arch})
and it will 'just work'.
I also notice that CMakeDetermineCXXCompiler.cmake doesn't have specific
handling for clang, and it could be extended similarly. Note that there are
two ways to use clang as a cross-compiler. One is specifying -target, which
CMAKE_C_COMPILER_TARGET does, and the other is creating a symlink or copy so
that the name contains the triple:
stephen@hal:/tmp$ /usr/bin/clang -dumpmachine
x86_64-pc-linux-gnu
stephen@hal:/tmp$ ln -s clang arm-linux-gnueabihf-clang
stephen@hal:/tmp$ ./arm-linux-gnueabihf-clang -dumpmachine
arm--linux-gnueabihf
So, possibly both ways should be handled in the clang case. I haven't
actually done any testing for the clang cases yet though to find out if the
missing _CMAKE_TOOLCHAIN_PREFIX causes a problem. I don't recall ever
hitting any, which confuses me somewhat.
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
[cmake-developers] get_target_property() windows vs mac
Dear To Whom This May Concern, I had a question regarding the function get_target_property(). I am using the following call: get_target_property(cdp-exe cdp LOCATION) This call is supposed to get the location of my executable file. This line of code works correctly on Macs, but it does not work correctly on Windows. Here's what happens when I attempt to get the location of my executable file on Windows: C:/Users/Admin/Perforce/10.160.0.30_1667/llondon_multi_tenant_workspace/projects/MultiTenant_1/DMServices/build/$(Configuration)/cdp.exe The variable $(Configuration) is not set and I am not sure why and I am unable to get the correct location to my executable. Are different properties/calls are needed for Windows vs. Mac? Any help or advice on this would be much appreciated. This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents. -- 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] Please review CXXFeatures.cmake
Brad King wrote: On 08/02/2013 05:20 PM, Rolf Eike Beer wrote: Brad, please don't merge that next week Okay. We're preparing 2.8.12 rc1 this week so I think we'll hold off CXXFeatures until after 2.8.12 anyway. I have pushed a fix for 14303 to next. Please have a look. Without this parallel memcheck is very broken (which would be a regression to 2.8.11). Eike -- signature.asc Description: This is a digitally signed message part. -- 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] get_target_property() windows vs mac
On 08/07/2013 03:51 PM, Loretta London wrote: get_target_property(cdp-exe cdp LOCATION) This call is supposed to get the location of my executable file. This line of code works correctly on Macs, but it does not work correctly on Windows. Here's what happens when I attempt to get the location of my executable file on Windows: C:/Users/Admin/Perforce/10.160.0.30_1667/llondon_multi_tenant_workspace/projects/MultiTenant_1/DMServices/build/$(Configuration)/cdp.exe The variable $(Configuration) is not set and I am not sure why and I am unable to get the correct location to my executable. Are different properties/calls are needed for Windows vs. Mac? Any help or advice on this would be much appreciated. In multi-configuration generators like VS and Xcode the actual build configuration is not known at CMake time, only at build time. The $(Configuration) is a VS project file placeholder for the location. See the documentation of the LOCATION property: http://www.cmake.org/cmake/help/v2.8.11/cmake.html#prop_tgt:LOCATION The paragraph starting with For a non-imported target, this property is provided for compatibility with CMake 2.4 and below... explains what you can do instead depending on the use case. FYI, this list is for developer discussion. A better place to ask usage questions is on the user list: http://www.cmake.org/mailman/listinfo/cmake Thanks, -Brad -- 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
