[Cmake-commits] CMake branch, master, updated. v3.9.0-rc5-166-g9ab399b

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  9ab399ba8226f167fa9af761c610f2390461adab (commit)
  from  1e34b42e7163b1f210b8a536b721af31fb059787 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ab399ba8226f167fa9af761c610f2390461adab
commit 9ab399ba8226f167fa9af761c610f2390461adab
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Jun 28 00:01:06 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Jun 28 00:01:06 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index b441e9a..4b2411d 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170627)
+set(CMake_VERSION_PATCH 20170628)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[cmake-developers] [ANNOUNCE] CMake 3.9.0-rc5 is ready for testing

[Robert Maynard]

I am proud to announce the fifth CMake 3.9 release candidate.
  https://cmake.org/download/

Documentation is available at:
  https://cmake.org/cmake/help/v3.9

Release notes appear below and are also published at
  https://cmake.org/cmake/help/v3.9/release/3.9.html

Some of the more significant changes in CMake 3.9 are:

* "CUDA" is now supported by the Visual Studio Generators for VS
  2010 and above.  This complements the existing support by the
  Makefile Generators and the "Ninja" generator. CUDA 8.0.61 or higher
  is recommended due to known bugs in the VS integration by earlier
  versions.

* CMake is now aware of the "C++ standards" and "C standards" and
  their associated meta-features for the following "compiler ids":
  "Cray", "PGI", and "XL".

* The "add_library()" command "IMPORTED" option learned to support
  Object Libraries.

* All "find_" commands now have a "PACKAGE_ROOT" search path group
  that is first in the search heuristics.  If a "find_" command is
  called from inside a find module, then the CMake variable and
  environment variable named "_ROOT" are used as prefixes
  and are the first set of paths to be searched.

* The "install(TARGETS)" command learned a new "OBJECTS" option to
  specify where to install Object Libraries.

* The "install(EXPORT)" command learned how to export Object
  Libraries.

* A "BUILD_WITH_INSTALL_NAME_DIR" target property and corresponding
  "CMAKE_BUILD_WITH_INSTALL_NAME_DIR" variable were added to control
  whether to use the "INSTALL_NAME_DIR" target property value for
  binaries in the build tree.  This is for macOS "install_name" as
  "BUILD_WITH_INSTALL_RPATH" is for "RPATH".

* A "CUDA_PTX_COMPILATION" target property was added to Object
  Libraries to support compiling to ".ptx" files instead of host
  object files.

* A new "GoogleTest" module was added to provide the
  "gtest_add_tests()" function independently of the "FindGTest"
  module. The function was also updated to support keyword arguments,
  with functionality expanded to allow a test name prefix and suffix
  to be specified, the dependency on the source files to be optional
  and the list of discovered test cases to be returned to the caller.

* The "Ninja" generator has loosened the dependencies of object
  compilation.  Object compilation now depends only on custom targets
  and custom commands associated with libraries on which the object's
  target depends and no longer depends on the libraries themselves.
  Source files in dependent targets may now compile without waiting
  for their targets' dependencies to link.

* Interprocedural optimization (IPO) is now supported for GNU and
  Clang compilers using link time optimization (LTO) flags.  See the
  "INTERPROCEDURAL_OPTIMIZATION" target property and
  "CheckIPOSupported" module.

* The "TARGET_OBJECTS" "generator expression" is now supported by
  the "add_custom_command()" and "file(GENERATE)" commands.

CMake 3.9 Release Notes
***

Changes made since CMake 3.8 include the following.


New Features



Languages
-

* "CUDA" is now supported by the Visual Studio Generators for VS
  2010 and above.  This complements the existing support by the
  Makefile Generators and the "Ninja" generator. CUDA 8.0.61 or higher
  is recommended due to known bugs in the VS integration by earlier
  versions.

* CMake is now aware of the "C++ standards" and "C standards" and
  their associated meta-features for the following "compiler ids":
  "Cray", "PGI", and "XL".


Generators
--

* Visual Studio Generators for VS 2010 and above learned to support
  the "ASM_NASM" language when "nasm" is installed.

* The "Xcode" generator learned to create Xcode schema files. This
  is an experimental feature and can be activated by setting the
  "CMAKE_XCODE_GENERATE_SCHEME" variable to a "TRUE" value.


Commands


* The "add_library()" command "IMPORTED" option learned to support
  Object Libraries.

* All "find_" commands now have a "PACKAGE_ROOT" search path group
  that is first in the search heuristics.  If a "find_" command is
  called from inside a find module, then the CMake variable and
  environment variable named "_ROOT" are used as prefixes
  and are the first set of paths to be searched.

* The "find_library()" command learned to search "libx32" paths when
  the build targets the "x32" ABI.  See the
  "FIND_LIBRARY_USE_LIBX32_PATHS" global property.

* The "include_external_msproject()" command learned to use the
  "MAP_IMPORTED_CONFIG_" target property to map current
  configurations to the external configurations.

* The "install(TARGETS)" command learned a new "OBJECTS" option to
  specify where to install Object Libraries.

* The "install(EXPORT)" command learned how to export Object
  Libraries.

* The "project()" command learned an optional "DESCRIPTION"
  parameter to set the "PROJECT_DESCRIPTION" variable.

* The "separate_arguments()" command gained a "NATIVE_COMMAND" mode
  that 

[CMake] [ANNOUNCE] CMake 3.9.0-rc5 is ready for testing

[Robert Maynard]

I am proud to announce the fifth CMake 3.9 release candidate.
  https://cmake.org/download/

Documentation is available at:
  https://cmake.org/cmake/help/v3.9

Release notes appear below and are also published at
  https://cmake.org/cmake/help/v3.9/release/3.9.html

Some of the more significant changes in CMake 3.9 are:

* "CUDA" is now supported by the Visual Studio Generators for VS
  2010 and above.  This complements the existing support by the
  Makefile Generators and the "Ninja" generator. CUDA 8.0.61 or higher
  is recommended due to known bugs in the VS integration by earlier
  versions.

* CMake is now aware of the "C++ standards" and "C standards" and
  their associated meta-features for the following "compiler ids":
  "Cray", "PGI", and "XL".

* The "add_library()" command "IMPORTED" option learned to support
  Object Libraries.

* All "find_" commands now have a "PACKAGE_ROOT" search path group
  that is first in the search heuristics.  If a "find_" command is
  called from inside a find module, then the CMake variable and
  environment variable named "_ROOT" are used as prefixes
  and are the first set of paths to be searched.

* The "install(TARGETS)" command learned a new "OBJECTS" option to
  specify where to install Object Libraries.

* The "install(EXPORT)" command learned how to export Object
  Libraries.

* A "BUILD_WITH_INSTALL_NAME_DIR" target property and corresponding
  "CMAKE_BUILD_WITH_INSTALL_NAME_DIR" variable were added to control
  whether to use the "INSTALL_NAME_DIR" target property value for
  binaries in the build tree.  This is for macOS "install_name" as
  "BUILD_WITH_INSTALL_RPATH" is for "RPATH".

* A "CUDA_PTX_COMPILATION" target property was added to Object
  Libraries to support compiling to ".ptx" files instead of host
  object files.

* A new "GoogleTest" module was added to provide the
  "gtest_add_tests()" function independently of the "FindGTest"
  module. The function was also updated to support keyword arguments,
  with functionality expanded to allow a test name prefix and suffix
  to be specified, the dependency on the source files to be optional
  and the list of discovered test cases to be returned to the caller.

* The "Ninja" generator has loosened the dependencies of object
  compilation.  Object compilation now depends only on custom targets
  and custom commands associated with libraries on which the object's
  target depends and no longer depends on the libraries themselves.
  Source files in dependent targets may now compile without waiting
  for their targets' dependencies to link.

* Interprocedural optimization (IPO) is now supported for GNU and
  Clang compilers using link time optimization (LTO) flags.  See the
  "INTERPROCEDURAL_OPTIMIZATION" target property and
  "CheckIPOSupported" module.

* The "TARGET_OBJECTS" "generator expression" is now supported by
  the "add_custom_command()" and "file(GENERATE)" commands.

CMake 3.9 Release Notes
***

Changes made since CMake 3.8 include the following.


New Features



Languages
-

* "CUDA" is now supported by the Visual Studio Generators for VS
  2010 and above.  This complements the existing support by the
  Makefile Generators and the "Ninja" generator. CUDA 8.0.61 or higher
  is recommended due to known bugs in the VS integration by earlier
  versions.

* CMake is now aware of the "C++ standards" and "C standards" and
  their associated meta-features for the following "compiler ids":
  "Cray", "PGI", and "XL".


Generators
--

* Visual Studio Generators for VS 2010 and above learned to support
  the "ASM_NASM" language when "nasm" is installed.

* The "Xcode" generator learned to create Xcode schema files. This
  is an experimental feature and can be activated by setting the
  "CMAKE_XCODE_GENERATE_SCHEME" variable to a "TRUE" value.


Commands


* The "add_library()" command "IMPORTED" option learned to support
  Object Libraries.

* All "find_" commands now have a "PACKAGE_ROOT" search path group
  that is first in the search heuristics.  If a "find_" command is
  called from inside a find module, then the CMake variable and
  environment variable named "_ROOT" are used as prefixes
  and are the first set of paths to be searched.

* The "find_library()" command learned to search "libx32" paths when
  the build targets the "x32" ABI.  See the
  "FIND_LIBRARY_USE_LIBX32_PATHS" global property.

* The "include_external_msproject()" command learned to use the
  "MAP_IMPORTED_CONFIG_" target property to map current
  configurations to the external configurations.

* The "install(TARGETS)" command learned a new "OBJECTS" option to
  specify where to install Object Libraries.

* The "install(EXPORT)" command learned how to export Object
  Libraries.

* The "project()" command learned an optional "DESCRIPTION"
  parameter to set the "PROJECT_DESCRIPTION" variable.

* The "separate_arguments()" command gained a "NATIVE_COMMAND" mode
  that 

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

[Brad King]

On 06/27/2017 11:36 AM, Robert Dailey wrote:
> Ok maybe I'm misunderstanding the design intent for toolchain files. 

Originally they were intended to contain information local to the
machine, like `set(CMAKE_ANDROID_NDK /path/on/my/machine/to/ndk)`.
In controlled environments that share many things it makes sense
to have deployable toolchain files instead.

> Basically, some things I like to determine programmatically. Putting
> in them in the toolchain file violates the "introspection" rule, but
> also results in code duplication

Toolchain files can `include()` other files from next to them.  That
can be used to avoid duplicate code.

The only information you need within your toolchain file logic to
compute CMAKE_ANDROID_NDK_DEPRECATED_HEADERS is CMAKE_ANDROID_NDK.
If you add logic to find/require CMAKE_ANDROID_NDK up front then you
can check its version.

CMake's `Modules/Platform/Android-Determine.cmake` file has very little
logic to choose `CMAKE_ANDROID_NDK` if it is not set by the user.  You
can either duplicate this in a toolchain file helper or take advantage
of knowledge about your controlled environments to have a shorter version.

-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/mailman/listinfo/cmake-developers

[Cmake-commits] CMake annotated tag, v3.9.0-rc5, created. v3.9.0-rc5

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The annotated tag, v3.9.0-rc5 has been created
at  1b4e85bc5475db2dfab9188f363042843d07974d (tag)
   tagging  372de3f8039f69b3a2edcf7120083ec4097f8bd3 (commit)
  replaces  v3.9.0-rc4
 tagged by  Brad King
on  Tue Jun 27 11:56:08 2017 -0400

- Log -
CMake 3.9.0-rc5
-BEGIN PGP SIGNATURE-

iQJKBAABCAA0FiEExsJlMku+vcNQtRPQLSzvEDSSFoQFAllSgBgWHGJyYWQua2lu
Z0BraXR3YXJlLmNvbQAKCRAtLO8QNJIWhLU8D/9L48kO10K76sZ6OW/IFBCDy5We
cJ+FoL1g8HeFQms2XRQqOn4Js6DRsM5kUfKxvP7lJBNfqVlQYgXp4NvuAL714e1k
Lvgy4wIY5mOz45Z+8/FGPzTZS102T7wq3g3AdHbJ1kxkgcq9569gyJhrQ6WRb9gE
srD6FvMPppko/h/l/ozsHV0wcyRRqtTUUyLelEn94JRyxSpEz/NS3DytwxjUH0Hp
fzdU77wwRoUitooIZg4noYS65ehpNWnD/degbuVo5l0/BDzTaTulKjTt/R+APhtn
4/jzQv698TYz0gBjca2G7CqGvV3AM9TCQUUjMiwiR+tdF61/daGg3gWY+twf3CTh
qPJUxiduCCXUmq0REsf55yr94V20sYvaiGF/921SYxWrfPzW1yxV9K8coD71Kni9
aWeIloeyB7yKmtZZ9ajfGDHBqe1+M2F02SEd6eyMUSLEw26EQ0cmwlrjR19qNzyz
ZLcGGeulbOLlgH98jNKwof2SXTrWRMTNZk4VM66JDbIwnaOrsNwwY+Eg1jf66/ZN
LtpBnTKLClnP6ECn6Q3UMDIhHZpTMGMhoQ0z33wb9WYOKW/TTaN4aHgkzYBWVTMt
JnQ0OIuLiEp2rpdfyHWp4Uf0kXVE0HoDeUrPnYNH0pWFgLvmBp8p0yfLgm7pSp6A
h0d9aa8FUlTrRAxtWg==
=33A3
-END PGP SIGNATURE-

Brad King (12):
  GCC,Clang: Mark CMAKE__COMPILER_{AR,RANLIB} as advanced
  Merge branch 'toolchain-binutils-advanced' into release-3.9
  GetPrerequisites: Do not warn about non-absolute UCRT system libraries
  Merge branch 'GetPrerequisites-ucrt-no-warn' into release-3.9
  Tests: Enable languages explicitly in RunCMake.target_compile_features
  target_compile_features: Do not crash on non-enabled language
  VS: Fix support for nvcc flags not in our flag table
  Merge branch 'vs-cuda-fix-flags' into release-3.9
  Merge branch 'fix-crash-on-non-enabled-language-features' into release-3.9
  FindDoxygen: Add private prefix to internal variables
  Merge branch 'FindDoxygen-internal-var' into release-3.9
  CMake 3.9.0-rc5

---


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc5-165-g1e34b42

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  1e34b42e7163b1f210b8a536b721af31fb059787 (commit)
   via  372de3f8039f69b3a2edcf7120083ec4097f8bd3 (commit)
  from  4d623861c566a490a05245ef8ed88a761ac030cc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1e34b42e7163b1f210b8a536b721af31fb059787
commit 1e34b42e7163b1f210b8a536b721af31fb059787
Merge: 4d62386 372de3f
Author: Brad King 
AuthorDate: Tue Jun 27 11:57:54 2017 -0400
Commit: Brad King 
CommitDate: Tue Jun 27 11:57:54 2017 -0400

Merge branch 'release-3.9'


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc5

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, release has been updated
   via  372de3f8039f69b3a2edcf7120083ec4097f8bd3 (commit)
  from  7f1fd07b19fc43ab9bd1c41b9c518069a4da3b7d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

[Robert Dailey]

On Tue, Jun 27, 2017 at 10:22 AM, Brad King  wrote:
> On 06/27/2017 11:14 AM, Robert Dailey wrote:
>> Also at $DAYJOB, we all work on the same code base. Our product is
>> tested and verified to work on a distinct set of configurations. Why
>> would I ask each user to create their own toolchain file?
>
> If you have a toolchain file that works in some finite set of
> tested environments then there is no reason not to share it
> among them.
>
> Why can't the logic to choose `CMAKE_ANDROID_NDK_DEPRECATED_HEADERS`
> be in your toolchain file?  All it needs to know is the NDK location.

Ok maybe I'm misunderstanding the design intent for toolchain files. I
agree they shouldn't do much introspection (i.e. "business logic"),
but I've always made sure to provide multiple toolchain files if
necessary in version control, one per supported (tested) configuration
for the code base. Generally speaking, I provide one per supported
platform (Android, Windows, Linux, etc). However, I will not specify
things in the toolchain file that are not "static". Basically, some
things I like to determine programmatically. Putting in them in the
toolchain file violates the "introspection" rule, but also results in
code duplication since I have to do that same introspection in each
toolchain file.

So my specific case is this: Unified headers have been supported since
NDK r14. However, because of certain libraries and language features
that we use, our code fails to compile due to bugs in the unified
headers. Again for our specific code base, these bugs are addressed in
NDK r15b. So now I'm faced with a situation: Just because unified
headers are present doesn't mean we should use them. So I can no
longer base the decision to use unified headers on when they were
introduced, but it needs to be based on an arbitrary NDK version.

To solve this issue, I have come up with this logic:
https://gist.github.com/rcdailey/0ee52bfca634e7da55b6f86b9af91911

This CMake logic allows me to obtain the version of the NDK the user
has on their system and based on that version I can strategically set
the CMAKE_ANDROID_NDK_DEPRECATED_HEADERS variable. This is all
transparent to users on my team. None of them have done the research I
have into this, so they would not know which NDK to use or when to set
this flag to 1 or 0. We support r14 and r15 in different environments.

Maybe my situation is the exception to the rule, but I just don't see
an elegant way to do what I want.
-- 

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/mailman/listinfo/cmake-developers

[CMake] CMake cannot find 32 bit Open SSL on 64 bit Ubuntu 14.04

[Bakary Diarra]

I have a 64 bit Ubuntu 14.04 VM and I am trying to compile a 32 bit
application that depends on openssl and I keep getting the following error:

-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108
(message):
  Could NOT find OpenSSL, try to set the path to OpenSSL root folder in
the
  system variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES) (found
  version "1.0.1f")

I have created the following test case to reproduce the error.

**DockerFile**

FROM ubuntu:trusty

LABEL maintainer="diarra_bak...@test.com"
LABEL version="1.0"

RUN dpkg --add-architecture i386 && \
apt-get update && \
apt-get install -y \
git\
cmake\
curl:i386\
libcurl4-openssl-dev:i386\
libssl-dev:i386\
uuid-dev:i386
RUN apt-get install -y \
gcc-multilib\
g++-multilib

**CMakeLists.txt**

cmake_minimum_required(VERSION 2.8)

find_package(OpenSSL REQUIRED)

**x86_32.cmake**

SET(CMAKE_SYSTEM_NAME Linux)

# which compilers to use for C and C++
set(CMAKE_C_COMPILER gcc)
set(CMAKE_C_FLAGS -m32)
set(CMAKE_CXX_COMPILER g++)
set(CMAKE_CXX_FLAGS -m32)

Run the following commands

mkdir cmake
cd cmake
cmake -DCMAKE_TOOLCHAIN_FILE=x86_32.cmake ..

Thanks in advance

*Bakary Diarra*
-- 

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/mailman/listinfo/cmake

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

[Brad King]

On 06/27/2017 11:14 AM, Robert Dailey wrote:
> Also at $DAYJOB, we all work on the same code base. Our product is
> tested and verified to work on a distinct set of configurations. Why
> would I ask each user to create their own toolchain file?

If you have a toolchain file that works in some finite set of
tested environments then there is no reason not to share it
among them.

Why can't the logic to choose `CMAKE_ANDROID_NDK_DEPRECATED_HEADERS`
be in your toolchain file?  All it needs to know is the NDK location.

-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/mailman/listinfo/cmake-developers

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

[Robert Dailey]

On Mon, Jun 26, 2017 at 3:32 PM, Brad King  wrote:
> On 06/26/2017 11:58 AM, Robert Dailey wrote:
>> Why does this only work in the toolchain file?
>
> 1. It needs to be set early.
>
> 2. It needs to propagate into try_compile projects.
>
> The toolchain file is sufficient for both.  A cache entry is okay
> for (1) but for (2) one would additionally need to set this:
>
>   
> https://cmake.org/cmake/help/v3.9/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.html
>
> ...though that is really meant for toolchain files too.
>
> Note that toolchain files are meant to be local to the machine, not
> distributed with source trees and full of introspection logic.  The
> (local) author of the toolchain file should know the NDK version and
> choose whether to use `CMAKE_ANDROID_NDK_DEPRECATED_HEADERS`.
>
> Your project code could check the NDK version and error out if
> the `CMAKE_ANDROID_NDK_DEPRECATED_HEADERS` is not correct.

Your idea of erroring out seems like the best alternative solution,
although again I strongly feel this is something that should be
automated. It makes the user's life easier. If we know it only works a
certain way and have the necessary information to make that decision
programmatically, then why not? Software is supposed to make our lives
easier. Adding unnecessary manual steps doesn't really serve any
benefit IMHO.

Also at $DAYJOB, we all work on the same code base. Our product is
tested and verified to work on a distinct set of configurations. Why
would I ask each user to create their own toolchain file? Each time a
change is needed, I'd have to email the whole team and ask them to
make a specific change to their toolchain file. This is very
unproductive. I can't say I agree with your philosophy.
-- 

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/mailman/listinfo/cmake-developers

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc4-11-g7f1fd07

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, release has been updated
   via  7f1fd07b19fc43ab9bd1c41b9c518069a4da3b7d (commit)
   via  d194bd915be3d99fda2d9e504655a78ee983f984 (commit)
  from  fd771df773224560a60850647b898280a0ec84fa (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Modules/FindDoxygen.cmake |   12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc4-175-g4d62386

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  4d623861c566a490a05245ef8ed88a761ac030cc (commit)
   via  7f1fd07b19fc43ab9bd1c41b9c518069a4da3b7d (commit)
  from  f7cc2cc2b693061c39ea6452935c67396da4b9e4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4d623861c566a490a05245ef8ed88a761ac030cc
commit 4d623861c566a490a05245ef8ed88a761ac030cc
Merge: f7cc2cc 7f1fd07
Author: Brad King 
AuthorDate: Tue Jun 27 10:59:03 2017 -0400
Commit: Brad King 
CommitDate: Tue Jun 27 10:59:03 2017 -0400

Merge branch 'release-3.9'


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc4-173-gf7cc2cc

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  f7cc2cc2b693061c39ea6452935c67396da4b9e4 (commit)
   via  d194bd915be3d99fda2d9e504655a78ee983f984 (commit)
  from  b43d0fd04b635a5de56d104d7dc1ab908b739c00 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f7cc2cc2b693061c39ea6452935c67396da4b9e4
commit f7cc2cc2b693061c39ea6452935c67396da4b9e4
Merge: b43d0fd d194bd9
Author: Brad King 
AuthorDate: Tue Jun 27 14:54:16 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 10:54:25 2017 -0400

Merge topic 'FindDoxygen-internal-var'

d194bd91 FindDoxygen: Add private prefix to internal variables

Acked-by: Kitware Robot 
Merge-request: !1012


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d194bd915be3d99fda2d9e504655a78ee983f984
commit d194bd915be3d99fda2d9e504655a78ee983f984
Author: Brad King 
AuthorDate: Tue Jun 27 08:38:15 2017 -0600
Commit: Brad King 
CommitDate: Tue Jun 27 10:45:45 2017 -0400

FindDoxygen: Add private prefix to internal variables

Since commit v3.9.0-rc1~55^2 (Improve Doxygen support, 2017-04-10) we
accidentally leave a non-prefixed internal `result` variable set.
This may interfere with project code.  Add a prefix to avoid this.

diff --git a/Modules/FindDoxygen.cmake b/Modules/FindDoxygen.cmake
index 0d9e161..26d44b9 100644
--- a/Modules/FindDoxygen.cmake
+++ b/Modules/FindDoxygen.cmake
@@ -389,10 +389,10 @@ macro(_Doxygen_find_doxygen)
 COMMAND "${DOXYGEN_EXECUTABLE}" --version
 OUTPUT_VARIABLE DOXYGEN_VERSION
 OUTPUT_STRIP_TRAILING_WHITESPACE
-RESULT_VARIABLE result
+RESULT_VARIABLE _Doxygen_version_result
 )
-if(result)
-message(WARNING "Unable to determine doxygen version: ${result}")
+if(_Doxygen_version_result)
+message(WARNING "Unable to determine doxygen version: 
${_Doxygen_version_result}")
 endif()
 
 # Create an imported target for Doxygen
@@ -623,11 +623,11 @@ if(TARGET Doxygen::doxygen)
 execute_process(
 COMMAND "${DOXYGEN_EXECUTABLE}" -s -g "${_Doxygen_tpl}"
 OUTPUT_QUIET
-RESULT_VARIABLE result
+RESULT_VARIABLE _Doxygen_tpl_result
 )
-if(result)
+if(_Doxygen_tpl_result)
 message(FATAL_ERROR
-"Unable to generate Doxyfile template: ${result}")
+"Unable to generate Doxyfile template: ${_Doxygen_tpl_result}")
 elseif(NOT EXISTS "${_Doxygen_tpl}")
 message(FATAL_ERROR
 "Doxygen has failed to generate a Doxyfile template")

---

Summary of changes:
 Modules/FindDoxygen.cmake |   12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[cmake-developers] Create target with dependency to all targets similar to 'cmake_check_build_system'

[maikel van den Hurk]

I am wondering why there is no entry to create a target which is a dependency 
for each target like the `cmake_check_build_system`. It feels bit hacky to 
overload add_dependencies() to achieve this or am I overlooking something.

Would something like this be good to add? If yes I could have a look into 
adding this, any pointers would be appreciated.


Thanks,

Maikel
-- 

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/mailman/listinfo/cmake-developers

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc4-171-gb43d0fd

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  b43d0fd04b635a5de56d104d7dc1ab908b739c00 (commit)
   via  126effbb9c345ccea9823f81c5323e7de1a6402c (commit)
   via  4fd6507a528ab1a9858eee2914e8d5a2b92bffdb (commit)
   via  33d6145f873029577e3498b843b6ef5646c594b8 (commit)
   via  43c3afa74538fd7b78bcf534bfb3fa93c3c1f191 (commit)
   via  dc11a20d7b308f15cc0080f6c14ea06d96dbc2c7 (commit)
   via  fd771df773224560a60850647b898280a0ec84fa (commit)
   via  1d86103846d4e8557c3cc77d3c1f2dce9231663d (commit)
   via  bbc1f3642cb86ce59908ee33eeb409d7921f73f8 (commit)
   via  a3e442bbfc8374c90aec9836ee40aa35a43c1bc2 (commit)
   via  e03a1b3b6185e36a5905db3d2551c9575fb074aa (commit)
   via  869904271ba0e8b855043894360b5dc7fe1e3b56 (commit)
   via  46d25e782ebd9b6c50771b6f30433c58fae03a51 (commit)
   via  ec409a116fd58a541a7700df12dfdfc045f0df17 (commit)
   via  dcdab5cf23b361d6c6dcaf0dfcefdd821792 (commit)
   via  0a8f469af921d64431ed237022a02d39cac3ebb5 (commit)
  from  b8858bd4046958b94b11e794e2a9aab9124414a4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b43d0fd04b635a5de56d104d7dc1ab908b739c00
commit b43d0fd04b635a5de56d104d7dc1ab908b739c00
Merge: 126effb fd771df
Author: Brad King 
AuthorDate: Tue Jun 27 09:23:18 2017 -0400
Commit: Brad King 
CommitDate: Tue Jun 27 09:23:18 2017 -0400

Merge branch 'release-3.9'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=126effbb9c345ccea9823f81c5323e7de1a6402c
commit 126effbb9c345ccea9823f81c5323e7de1a6402c
Merge: 4fd6507 ec409a1
Author: Brad King 
AuthorDate: Tue Jun 27 13:21:17 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 09:21:38 2017 -0400

Merge topic 'vs_csharp_custom_command'

ec409a11 Vs: fix CSharp custom command by introducing inline MSBuild 
s
dcdab5cf Vs: factor out computation of  tag for CSharp source files
0a8f469a Vs: refactor WriteCustomRule for preparation of CSharp support

Acked-by: Kitware Robot 
Merge-request: !970


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4fd6507a528ab1a9858eee2914e8d5a2b92bffdb
commit 4fd6507a528ab1a9858eee2914e8d5a2b92bffdb
Merge: 33d6145 a3e442b
Author: Brad King 
AuthorDate: Tue Jun 27 13:21:02 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 09:21:15 2017 -0400

Merge topic 'FindCUDA-no-empty-genex'

a3e442bb FindCUDA: Fix CUDA_NVCC_FLAGS_ for separable compilation

Acked-by: Kitware Robot 
Merge-request: !1008


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=33d6145f873029577e3498b843b6ef5646c594b8
commit 33d6145f873029577e3498b843b6ef5646c594b8
Merge: 43c3afa 46d25e7
Author: Brad King 
AuthorDate: Tue Jun 27 13:20:42 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 09:20:51 2017 -0400

Merge topic 'FindCUDA-no-find_host_program'

46d25e78 FindCUDA: Use find_program if find_host_program is not available

Acked-by: Kitware Robot 
Merge-request: !1009


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=43c3afa74538fd7b78bcf534bfb3fa93c3c1f191
commit 43c3afa74538fd7b78bcf534bfb3fa93c3c1f191
Merge: dc11a20 e03a1b3
Author: Brad King 
AuthorDate: Tue Jun 27 13:20:28 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 09:20:32 2017 -0400

Merge topic 'fix-crash-on-non-enabled-language-features'

e03a1b3b target_compile_features: Do not crash on non-enabled language
86990427 Tests: Enable languages explicitly in 
RunCMake.target_compile_features

Acked-by: Kitware Robot 
Merge-request: !1010


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc11a20d7b308f15cc0080f6c14ea06d96dbc2c7
commit dc11a20d7b308f15cc0080f6c14ea06d96dbc2c7
Merge: b8858bd bbc1f36
Author: Brad King 
AuthorDate: Tue Jun 27 13:18:26 2017 +
Commit: Kitware Robot 
CommitDate: Tue Jun 27 09:18:34 2017 -0400

Merge topic 'vs-cuda-fix-flags'

bbc1f364 VS: Fix support for nvcc flags not in our flag table

Acked-by: Kitware Robot 
Merge-request: !1007


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a3e442bbfc8374c90aec9836ee40aa35a43c1bc2
commit a3e442bbfc8374c90aec9836ee40aa35a43c1bc2
Author:  

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc4-9-gfd771df

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, release has been updated
   via  fd771df773224560a60850647b898280a0ec84fa (commit)
   via  1d86103846d4e8557c3cc77d3c1f2dce9231663d (commit)
   via  bbc1f3642cb86ce59908ee33eeb409d7921f73f8 (commit)
   via  e03a1b3b6185e36a5905db3d2551c9575fb074aa (commit)
   via  869904271ba0e8b855043894360b5dc7fe1e3b56 (commit)
  from  c24e66561356af461245a59dda8f5161399d48a6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Source/cmMakefile.cxx  |   21 ++--
 Source/cmVisualStudio10TargetGenerator.cxx |6 +++---
 Tests/CudaOnly/SeparateCompilation/CMakeLists.txt  |5 +
 .../target_compile_features/CMakeLists.txt |2 +-
 .../target_compile_features/RunCMakeTest.cmake |1 +
 .../alias_target-stderr.txt|2 +-
 .../target_compile_features/alias_target.cmake |1 +
 .../cxx_not_enabled-result.txt}|0
 .../cxx_not_enabled-stderr.txt |4 
 .../target_compile_features/cxx_not_enabled.cmake  |2 ++
 .../imported_target-stderr.txt |2 +-
 .../target_compile_features/imported_target.cmake  |1 +
 .../invalid_args-stderr.txt|2 +-
 .../target_compile_features/invalid_args.cmake |1 +
 .../invalid_args_on_interface-stderr.txt   |2 +-
 .../invalid_args_on_interface.cmake|1 +
 .../no_matching_c_feature-stderr.txt   |2 +-
 .../no_matching_c_feature.cmake|1 +
 .../no_matching_cxx_feature-stderr.txt |2 +-
 .../no_matching_cxx_feature.cmake  |1 +
 .../target_compile_features/no_target-stderr.txt   |2 +-
 .../target_compile_features/no_target.cmake|1 +
 .../not_a_c_feature-stderr.txt |2 +-
 .../target_compile_features/not_a_c_feature.cmake  |1 +
 .../not_a_cxx_feature-stderr.txt   |2 +-
 .../not_a_cxx_feature.cmake|1 +
 .../not_enough_args-stderr.txt |2 +-
 .../target_compile_features/not_enough_args.cmake  |1 +
 .../utility_target-stderr.txt  |2 +-
 29 files changed, 56 insertions(+), 17 deletions(-)
 copy Tests/RunCMake/{Android/BadSYSROOT-result.txt => 
target_compile_features/cxx_not_enabled-result.txt} (100%)
 create mode 100644 
Tests/RunCMake/target_compile_features/cxx_not_enabled-stderr.txt
 create mode 100644 Tests/RunCMake/target_compile_features/cxx_not_enabled.cmake


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] ctest: building test in parellel

[Damian Dixon]

> I'm not sure to understand.
​> ​
Do you want to **build** test in parallel or **run** test in parallel?

​I want to build a test in parallel.

​> How are you calling ctest?

ctest -V -R '^DDOTUT_x11$'


I'm only running one test executable at a time.


​> cmake
cmake
-DCMAKE_TOOLCHAIN_FILE=../../Build/buildconfigs/any-linux-gcc-x86_64.cmake
../../Build

The build system we have contains 30 odd external libraries and about 40 of
our own.
​
> make
make -j8

This builds everything but the tests.

We've been leaving the build of the tests to ctest upto now.

However ctest now appears to be building more than just the tests. Its not
rebuilding everything just some of the libraries.

make on its own seems to respect the dependencies and only rebuild what is
required unless I've run ctest.



On 27 June 2017 at 13:03, Eric Noulard  wrote:

>
>
> 2017-06-27 13:32 GMT+02:00 Damian Dixon :
>
>> Hi,
>>
>> Is there anyway to build tests in parallel when using ctest?
>>
>
> I'm not sure to understand.
> Do you want to **build** test in parallel or **run** test in parallel?
>
>
>>
>> I am generating makefiles on Linux.
>>
>
> Then
>
> $ make -j 8
>
> should build in parallel.
>
>
>>
>> Part of the reason I am asking this is that if I pre-build the test for
>> some unknown reason ctest rebuilds the source files.
>>
>
> Then you have to verify your test dependencies. ctest should only run the
> tests not build then unless you call ctest
> with --build-xxx option.
>
> How are you calling ctest?
>
> ctest --parallel 8
> or
> ctest -j 8
>
> should run tests in parallel.
>
> This works for me (either parallel build or parallel test run) but I'm
> using ninja.
>
>
> Could you give us more detail on how you run cmake, make and ctest ?
>
>
> --
> Eric
>
-- 

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/mailman/listinfo/cmake

Re: [CMake] Unable to build cmoka project using cmake

[Rajesh Kumar]

Any suggestions please?

Regards
Rajesh

On Thu, Jun 22, 2017, 1:17 PM Rajesh Kumar  wrote:

> Hi Chuck,
>
> Comments are inline.
>
> Regards
> Rajesh
>
> On Wed, Jun 21, 2017, 8:32 PM Chuck Atkins 
> wrote:
>
>> Hi Rajesh,
>>  We would need more information to be useful:
>>
>
>>- What version of CMake are you using? - 3.9.20170615 ( on 20170615 I
>>have downloaded the source code from git repository and complied on my AIX
>>machine)
>>- What compiler and version are you using? - gcc 4.2.0
>>
>>
>>- What OS and version are you using?
>>
>>
>>- Do you have separate source and build directories? AIX 1.6
>>- How are you running cmake? This is the command I am running to
>>build cmocka project. cmake $cmockasource path -Wno-dev --trace. Also I
>>tried compiling cmocka project by forcing the C compiler with
>>CMAKE_C_COMPILERFORCED, but no luck.
>>
>>
>> --
>> Chuck Atkins
>> Staff R Engineer, Scientific Computing
>> Kitware, Inc.
>>
>>
>> On Wed, Jun 21, 2017 at 5:47 AM, Rajesh Kumar 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am unable to build cmocka project using Cmake. The below are the
>>> errors which I'm facing.
>>>
>>> "The C compiler identification is unknown"
>>> "System is unknown to cmake, create: to use this system, please send
>>> your config file to cm...@www.cmake.org so it can be added to cmake"
>>>
>>> Please suggest.
>>>
>>> Regards
>>> Rajesh
>>>
>>> --
>>>
>>> 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/mailman/listinfo/cmake
>>>
>>
>>
-- 

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/mailman/listinfo/cmake

Re: [CMake] ctest: building test in parellel

[Eric Noulard]

2017-06-27 13:32 GMT+02:00 Damian Dixon :

> Hi,
>
> Is there anyway to build tests in parallel when using ctest?
>

I'm not sure to understand.
Do you want to **build** test in parallel or **run** test in parallel?


>
> I am generating makefiles on Linux.
>

Then

$ make -j 8

should build in parallel.


>
> Part of the reason I am asking this is that if I pre-build the test for
> some unknown reason ctest rebuilds the source files.
>

Then you have to verify your test dependencies. ctest should only run the
tests not build then unless you call ctest
with --build-xxx option.

How are you calling ctest?

ctest --parallel 8
or
ctest -j 8

should run tests in parallel.

This works for me (either parallel build or parallel test run) but I'm
using ninja.


Could you give us more detail on how you run cmake, make and ctest ?


-- 
Eric
-- 

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/mailman/listinfo/cmake

Re: [CMake] ctest: building test in parellel

[Damian Dixon]

Sadly -j does not appear to help.

I have also tried setting the gmake MAKEFLAGS environment as well.

On 27 June 2017 at 12:34, Craig Scott  wrote:

> Does the -j option to ctest not do what you want?
>
> On Tue, Jun 27, 2017 at 9:32 PM, Damian Dixon 
> wrote:
>
>> Hi,
>>
>> Is there anyway to build tests in parallel when using ctest?
>>
>> I am generating makefiles on Linux.
>>
>> Part of the reason I am asking this is that if I pre-build the test for
>> some unknown reason ctest rebuilds the source files.
>>
>> I am currently using cmake 3.8.0.
>>
>> Thanks
>> Damian
>>
>> --
>>
>> 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/mailman/listinfo/cmake
>>
>
>
>
> --
> Craig Scott
> Melbourne, Australia
> https://crascit.com
>
-- 

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/mailman/listinfo/cmake

Re: [CMake] ctest: building test in parellel

[Craig Scott]

Does the -j option to ctest not do what you want?

On Tue, Jun 27, 2017 at 9:32 PM, Damian Dixon 
wrote:

> Hi,
>
> Is there anyway to build tests in parallel when using ctest?
>
> I am generating makefiles on Linux.
>
> Part of the reason I am asking this is that if I pre-build the test for
> some unknown reason ctest rebuilds the source files.
>
> I am currently using cmake 3.8.0.
>
> Thanks
> Damian
>
> --
>
> 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/mailman/listinfo/cmake
>



-- 
Craig Scott
Melbourne, Australia
https://crascit.com
-- 

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/mailman/listinfo/cmake

[CMake] ctest: building test in parellel

[Damian Dixon]

Hi,

Is there anyway to build tests in parallel when using ctest?

I am generating makefiles on Linux.

Part of the reason I am asking this is that if I pre-build the test for
some unknown reason ctest rebuilds the source files.

I am currently using cmake 3.8.0.

Thanks
Damian
-- 

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/mailman/listinfo/cmake

Re: [CMake] Visual Studio with CUDA does not work in 3.9

[Mueller-Roemer, Johannes Sebastian]

If anyone else runs into this issue: I was able to solve it by re-installing 
the .NET 3.5 Framework which a recent Update had apparently removed (because I 
have previously built "native" CUDA VS projects on this machine without issues).

This solved the issue for me. If you have an error message like

error MSB4062: The "Nvda.Build.CudaTasks.SanitizePaths" task could not be 
loaded from the assembly C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\BuildCustomizations\Nvda.Build.CudaTasks.v8.0.dll.
Could not load file or assembly 'Microsoft.Build.Utilities.v3.5, 
Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of 
its dependencies. The system cannot find the file specified.
Confirm that the  declaration is correct, that the assembly and all 
its dependencies are available, and that the task contains a public class that 
implements

in your cmake error log, you are running into the same issue.

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
Tel +49 6151 155-606  |  Fax +49 6151 155-139
johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de


-Original Message-
From: Robert Maynard [mailto:robert.mayn...@kitware.com] 
Sent: Friday, June 23, 2017 15:40
To: Mueller-Roemer, Johannes Sebastian 

Cc: CMake MailingList 
Subject: Re: [CMake] Visual Studio with CUDA does not work in 3.9

Hi

Unfortunately you are going to need to provide more information to help track 
down the issue. We currently have machines that verify
2015/8.0 and 2013/7.5 properly work (
https://open.cdash.org/index.php?project=CMake=1=1=buildname=63=CUDA
)

Can you please provide run from the build directory cmake --system-information 
 and send the results?

On Fri, Jun 23, 2017 at 9:11 AM, Mueller-Roemer, Johannes Sebastian 
 wrote:
> Hi Robert,
>
> yes, according to the Windows installed program list, I have "NVIDIA CUDA 
> Visual Studio Integration 8.0" installed. I can also create CUDA projects via 
> "New project" and have an Nsight menu entry.
>
> Regards
> Johannes Mueller-Roemer
>
> Fraunhofer-Institut für Graphische Datenverarbeitung IGD 
> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany Tel +49 6151 155-606  
> |  Fax +49 6151 155-139 johannes.mueller-roe...@igd.fraunhofer.de | 
> www.igd.fraunhofer.de
>
>
> -Original Message-
> From: Robert Maynard [mailto:robert.mayn...@kitware.com]
> Sent: Friday, June 23, 2017 14:52
> To: Mueller-Roemer, Johannes Sebastian 
> 
> Cc: CMake MailingList 
> Subject: Re: [CMake] Visual Studio with CUDA does not work in 3.9
>
> Hi,
>
> Do you have the NVIDIA CUDA Visual Studio Integration tools installed?
> This is needed for support when using the Visual Studio Generator(s).
> Otherwise you can still use ninja or the nmake generators.
>
> On Fri, Jun 23, 2017 at 7:06 AM, Mueller-Roemer, Johannes Sebastian 
>  wrote:
>> The absolute minimum example
>>
>>
>>
>> cmake_minimum_required(VERSION 3.9 FATAL_ERROR)
>>
>> project(cuda-test LANGUAGES C CXX CUDA)
>>
>> add_executable(cuda-test main.cu)
>>
>>
>>
>> Fails to configure with the error:
>>
>> CMake Error at CMakeLists.txt:2 (project):
>>
>>   No CMAKE_CUDA_COMPILER could be found.
>>
>>
>>
>> Am I missing something, or is the support mentioned in the change 
>> list simply not true?
>>
>>
>>
>> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
>>
>> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
>>
>> Tel +49 6151 155-606  |  Fax +49 6151 155-139
>>
>> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>>
>>
>>
>>
>> --
>>
>> 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/mailman/listinfo/cmake
-- 

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