[Cmake-commits] CMake branch, master, updated. v3.9.0-454-g92d16be

[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  92d16be9e6578600a273b338d003eb8908e5ed4e (commit)
  from  bfdfc6db9d51ac874ea12caa89c41a3211c917c2 (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=92d16be9e6578600a273b338d003eb8908e5ed4e
commit 92d16be9e6578600a273b338d003eb8908e5ed4e
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Aug 9 00:01:07 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Aug 9 00:01:07 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index e8ea5ee..666eb87 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 20170808)
+set(CMake_VERSION_PATCH 20170809)
 #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

Re: [CMake] CMake + Gradle for Android

[Eric Wing]

On 8/8/17, Jom O'Fisher  wrote:
> Yeah, we'd like to support any CMake more recent than 3.7.0 (which is the
> first version to support server mode). So your fork would need to be based
> on a somewhat recent CMake. We probably wouldn't support a path directly in
> build.gradle since that is typically a source controlled artifact. We'd let
> you set a file path in local.properties and/or specify a CMake version
> number in build.gradle where we'd search for it in some well-known
> locations.

I think I could live with local.properties. Any chance you could fast
track this and get it in soon?

Somewhat coincidentally, my fork of CMake happened close to the time
of where the Google fork seemed to happen. I tried the merge. I got
tons of conflicts for other things, not my changes. I'm about half-way
resolving them...but my changeset is relatively small so I've been
thinking I might just manually repatch on yours or try the
cherry-picking feature of Git.

Thanks,
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] CMake + Gradle for Android

[Jom O'Fisher]

Yeah, we'd like to support any CMake more recent than 3.7.0 (which is the
first version to support server mode). So your fork would need to be based
on a somewhat recent CMake. We probably wouldn't support a path directly in
build.gradle since that is typically a source controlled artifact. We'd let
you set a file path in local.properties and/or specify a CMake version
number in build.gradle where we'd search for it in some well-known
locations.


On Tue, Aug 8, 2017 at 5:21 PM, Eric Wing  wrote:

> Hi Jom,
>
> I'm glad to hear Android's CMake will eventually catch up.
>
> But since you are here, can you add a feature that allows a user to
> specify an alternate location for where CMake is located? There are
> two useful cases for this.
>
> 1) Users daring or desperate enough to try using a more recent CMake
> while they wait (perhaps they could have merged with Google's branch
> manually)
>
> 2) In my case, I'm trying to implement new features into CMake (Swift
> compiler support). It's not going to be mainlined anytime soon since
> it is a long project, so even when you catch up, I still need to be
> able to call my fork of CMake.
>
> I don't want to overwrite anything in the Android distribution, and I
> have people using my stuff and helping me, so we need a way to
> collaborate. A simple gradle argument that lets me specify an
> alternative path to CMake would fix my problem. (The other things I
> need are specifying a toolchain file which I think you already support
> and an Initial Cache (-C switch) which maybe is implicitly supported
> since it is just a generic CMake command line argument.
>
>
> Right now, I am doing the alternative method of calling CMake myself
> through Gradle/Groovy scripts as people used to do. But I never
> figured out how to get debugger integration with Android Studio as a
> consequence. I would really like to move to the official Google/CMake
> support, but I can't do that unless I can invoke a different CMake. (I
> did pull the Google fork of CMake and I think my changes are
> mergable.)
>
> Thanks,
> 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] CMake + Gradle for Android

[Eric Wing]

Hi Jom,

I'm glad to hear Android's CMake will eventually catch up.

But since you are here, can you add a feature that allows a user to
specify an alternate location for where CMake is located? There are
two useful cases for this.

1) Users daring or desperate enough to try using a more recent CMake
while they wait (perhaps they could have merged with Google's branch
manually)

2) In my case, I'm trying to implement new features into CMake (Swift
compiler support). It's not going to be mainlined anytime soon since
it is a long project, so even when you catch up, I still need to be
able to call my fork of CMake.

I don't want to overwrite anything in the Android distribution, and I
have people using my stuff and helping me, so we need a way to
collaborate. A simple gradle argument that lets me specify an
alternative path to CMake would fix my problem. (The other things I
need are specifying a toolchain file which I think you already support
and an Initial Cache (-C switch) which maybe is implicitly supported
since it is just a generic CMake command line argument.


Right now, I am doing the alternative method of calling CMake myself
through Gradle/Groovy scripts as people used to do. But I never
figured out how to get debugger integration with Android Studio as a
consequence. I would really like to move to the official Google/CMake
support, but I can't do that unless I can invoke a different CMake. (I
did pull the Google fork of CMake and I think my changes are
mergable.)

Thanks,
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-developers] Linking Apple frameworks

[Eric Wing]

On 8/8/17, Brad King  wrote:
> On 08/07/2017 05:27 PM, Eric Wing wrote:
>> I think that would be a mistake because it seems that the only purpose
>> of this change would be so you could bypass CMake and try to directly
>> invoke some kind of command line invocation on the dynamic library
>> inside the .framework bundle.
>
> The ld(1) man page on macOS says that "-framework foo" tells the
> linker to search for "foo.framework/foo".  For linking this is very
> similar to "-lfoo" searching for "libfoo.so" and "libfoo.a" in the
> linker search path.  We discourage the latter because it is hard to
> ensure that the proper library will be found.  I think framework
> libraries should be linked by absolute path too.
>
> For example, say one has these libraries in frameworks:
>
> /path/A/foo.framework/foo  # want this one
> /path/A/bar.framework/bar
> /path/B/foo.framework/foo
> /path/B/bar.framework/bar  # want this one
>
> How does one achieve this case with Xcode's abstractions or with
> the "-framework foo" flag?  CMake with imported targets already
> achieves this, and links via absolute path to each library file.
>
>> be treating the framework bundle as a whole because all parts of it
>> are designed to be useful.
>
> In cases where that is needed it is still possible to detect that
> a library file is part of a framework.
>
>> The bundle assets like any .nib files and
>> the Info.plist are sometimes critical components of the framework. So
>> things like copying the whole framework and embedding them in the app
>> bundle are important things to do.
> [snip]
>> But if you did decide to change this, I think it should only happen in
>> conjunction of solving the rest of the needed functionality for
>> dealing with frameworks, i.e. copying the entire framework bundle into
>> the app bundle, codesigning the framework in the app bundle,
>
> We already have ways of doing those things at installation and
> packaging time.  Linking the build-tree copy is too early.
>
> -Brad
>

So two more quick points.

1) The absolute path this is actually a problem, especially for iOS
because of the way the SDK stuff works. There are two subcases where
the CMake behavior breaks down:
a)  When the user needs to change the target SDK on the fly
a) When switching between simulator and device build, this
effectively changes the root of the SDK on the fly so different
binaries can be pulled in to link to. Unfortunately Apple doesn't use
their fat binary concept here, and actually causes problems for 3rd
party iOS frameworks because if you try to build a fat dynamic
library, the app store rejects it because you have simulator
architectures.

2) The packaging and installation conventions CMake imposes are just
plain wrong for Apple development. It needs to be an atomic piece as
part of the main build phase, not a two phase thing. Xcode knows it
must bundle all the resources, bundle the frameworks, manage the
sandboxing entitlements, and do all the codesigning in the correct
order and this is built into Xcode's build process. The CMake way
breaks this and basically gets in the way of developing any proper app
that would need to be shipped on the App store. It also breaks a lot
of the tooling around it since it assumes that once you hit the Run
button, Xcode puts everything together correctly. This can affect
everything from trying to test  InAppPurchase features to debugging
with Instruments. (And again, this is problematic for iOS which shares
the same expected atomic workflow.)

-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-developers

Re: [CMake] CMake 3.9.0 Windows zip file shows wrong version

[Adam Getchell]

Yeah, that was it, lol.

-- 
Adam Getchell
https://keybase.io/adamgetchell

> On Aug 8, 2017, at 1:33 AM, David Cole  wrote:
> 
> I suspect you are running a different cmake, not the one you've unzipped.
> 
> Type "where cmake" instead of "cmake --version" and Windows will list
> the directories where it finds an executable named cmake. The first
> one it lists is the one it is running when you type "cmake
> --version"...
> 
> If you want to force the one you've downloaded to run instead of that
> one, you could **prepend** to the PATH instead of appending to it.
> 
> 
> HTH,
> David C.
> 
> 
> 
> On Mon, Aug 7, 2017 at 9:07 PM, Adam Getchell  wrote:
>> Hi all,
>> 
>> The CMake 3.9.0 Windows zip file gives the wrong version. Here’s a snippet
>> from my AppVeyor logs [1]:
>> 
>> set CMAKE_URL="https://cmake.org/files/v3.9/cmake-3.9.0-win64-x64.zip;
>> appveyor DownloadFile %CMAKE_URL% -FileName cmake.zip
>> Downloading cmake.zip (25,944,520 bytes)...100%
>> 7z x cmake.zip -oC:\projects\dev
>> 7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04
>> Scanning the drive for archives:
>> 1 file, 25944520 bytes (25 MiB)
>> Extracting archive: cmake.zip
>> --
>> Path = cmake.zip
>> Type = zip
>> Physical Size = 25944520
>> Everything is Ok
>> Folders: 90
>> Files: 4922
>> Size: 66584952
>> Compressed: 25944520
>> set PATH=%PATH%;C:\projects\dev\cmake\bin
>> cmake --version
>> cmake version 3.8.2
>> CMake suite maintained and supported by Kitware (kitware.com/cmake).
>> 
>> [1] https://ci.appveyor.com/project/acgetchell/cdt-plusplus
>> --
>> Adam Getchell
>> https://keybase.io/adamgetchell
>> 
>> 
>> --
>> 
>> 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] CMake equivalent to Boost.Build site-config.jam oruser-config.jam

[Lectem]

I think that you are looking for the toolchain files :
https://cmake.org/cmake/help/v3.0/manual/cmake-toolchains.7.html

The other option is to use a cmake script to specify your variables which 
includes CMakelists.txt (or the other way around if you can modify the 
CMakelists.txt). This would be quite similar to ctests scripts.
Some good examples are in Daniel Pfeifer’s « Effective cmake » talk 
https://github.com/boostcon/cppnow_presentations_2017/blob/master/05-19-2017_friday/effective_cmake__daniel_pfeifer__cppnow_05-19-2017.pdf


De : Brian Davis
Envoyé le :mardi 8 août 2017 20:09
À : cmake Mailing List
Objet :[CMake] CMake equivalent to Boost.Build site-config.jam oruser-config.jam


Is there a CMake equivalent to a site-config.jam or user-config.jam

http://www.boost.org/build/doc/html/bbv2/recipies/site-config.html
basically a CMake file the user can put in a project directory that CMake will 
read first when using cmake-gui that allows user to specify stuff they don't 
want to have to keep specifying in cmake-gui each "delete cache"
such as 
set( CMAKE_INSTALL_PREFIX ${CURRENT_LIST_DIR}/install CACHE STRING "" FORCE)
set( CMAKE_DEBUG_POSTFIX d CACHE STRING "" FORCE )

There is cmake.exe

-C  
but requires command line
come to think of it would be nice if 
set( CMAKE_GENERATOR_PLATFORM "Visual Studio 12 2013 Win64" )
in desired user config file and CMake would just "make it so" on clicking 
Generate.
I can do this with my own projects, by implementing it myself, but when 
checking out 3rd party projs they can be all over the map on config allowing a 
user-config.cmake would provide mechanism to tame the config problems.
Desired workflow
1) Checkout 3rd party proj
2) put a CMakeUser.txt or whatever file per project
3) Run CMake GUI Generate
4) Click Open Project
5) Change whatever manual bits in in gui
6) Update project suing git witch branches versions
7) Delete Cache
8) Return to 3
9) Doopy doopy doo whatever else



-- 

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] CMake equivalent to Boost.Build site-config.jam or user-config.jam

[Brian Davis]

Is there a CMake equivalent to a site-config.jam or user-config.jam

http://www.boost.org/build/doc/html/bbv2/recipies/site-config.html

basically a CMake file the user can put in a project directory that CMake
will read first when using cmake-gui that allows user to specify stuff they
don't want to have to keep specifying in cmake-gui each "delete cache"

such as

set( CMAKE_INSTALL_PREFIX ${CURRENT_LIST_DIR}/install CACHE STRING "" FORCE)
set( CMAKE_DEBUG_POSTFIX d CACHE STRING "" FORCE )


There is cmake.exe

-C 

but requires command line

come to think of it would be nice if
set( CMAKE_GENERATOR_PLATFORM "Visual Studio 12 2013 Win64" )

in desired user config file and CMake would just "make it so" on clicking
Generate.

I can do this with my own projects, by implementing it myself, but when
checking out 3rd party projs they can be all over the map on config
allowing a user-config.cmake would provide mechanism to tame the config
problems.

Desired workflow

1) Checkout 3rd party proj

2) put a CMakeUser.txt or whatever file per project

3) Run CMake GUI Generate

4) Click Open Project

5) Change whatever manual bits in in gui

6) Update project suing git witch branches versions

7) Delete Cache

8) Return to 3

9) Doopy doopy doo whatever else
-- 

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] Can't get CMake to link pthreads to my lib

[Jean-Michaël Celerier]

I've tried this and also
set(THREADS_PREFER_PTHREAD_FLAG TRUE)

but this didn't work either.



---
Jean-Michaël Celerier
http://www.jcelerier.name

On Tue, Aug 8, 2017 at 4:01 PM, Rolf Eike Beer  wrote:

> Am 2017-08-08 15:45, schrieb Jean-Michaël Celerier:
>
>> Here's my CMakeLists.txt :
>>
>>
>
>> cmake_minimum_required(VERSION 3.8 FATAL_ERROR)
>> project(oscour)
>> set(CMAKE_INCLUDE_CURRENT_DIR ON)
>>
>> set(CMAKE_CXX_FLAGS "-fconcepts -fsanitize=address -fsanitize=undefined")
>> set(CMAKE_EXE_LINKER_FLAGS "-fconcepts -fsanitize=address
>> -fsanitize=undefined")
>>
>> add_subdirectory(uWebSockets)
>>
>
> set(CMAKE_THREAD_PREFER_PTHREAD On)
>
> find_package(Threads REQUIRED)
>>
>
> Greetings,
>
> Eike
> --
> --
>
> 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/opensou
> rce/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

[Cmake-commits] CMake branch, master, updated. v3.9.0-453-gbfdfc6d

[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  bfdfc6db9d51ac874ea12caa89c41a3211c917c2 (commit)
   via  6e5ad2716f708a7ce60cc24f0cf96c71614afb66 (commit)
  from  db6ea482f6a9905e643b0c343cc545df936c71dc (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=bfdfc6db9d51ac874ea12caa89c41a3211c917c2
commit bfdfc6db9d51ac874ea12caa89c41a3211c917c2
Merge: db6ea48 6e5ad27
Author: Brad King 
AuthorDate: Tue Aug 8 10:09:33 2017 -0400
Commit: Brad King 
CommitDate: Tue Aug 8 10:09:33 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-27-g6e5ad27

[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  6e5ad2716f708a7ce60cc24f0cf96c71614afb66 (commit)
   via  e4ea628b42bcef9dafbc504a62d2b9c8cfc8521c (commit)
   via  44e5fb9c7ea3e3b0288cc24ec85554112e966d73 (commit)
   via  7e08602c761cabe75c557eacf738b716a4a1e18a (commit)
   via  6276ec3726ce4bb92748b0a70b1102e38924b626 (commit)
  from  8fb12ce7a22ffe21cb9dfc20ffaf111d0897a34a (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:
 Utilities/Scripts/update-expat.bash |6 +-
 Utilities/cmexpat/CMakeLists.txt|7 +-
 Utilities/cmexpat/ConfigureChecks.cmake |2 +-
 Utilities/cmexpat/README|  139 
 Utilities/cmexpat/README.md |  126 
 Utilities/cmexpat/lib/expat.h   |3 +-
 Utilities/cmexpat/lib/loadlibrary.c |  141 
 Utilities/cmexpat/lib/siphash.h |   55 +++-
 Utilities/cmexpat/lib/xmlparse.c|  530 ++-
 Utilities/cmexpat/lib/xmlrole.c |   30 +-
 Utilities/cmexpat/lib/xmltok.c  |   13 +-
 Utilities/cmexpat/lib/xmltok_impl.c |   39 ++-
 12 files changed, 845 insertions(+), 246 deletions(-)
 delete mode 100644 Utilities/cmexpat/README
 create mode 100644 Utilities/cmexpat/README.md
 create mode 100644 Utilities/cmexpat/lib/loadlibrary.c


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

Re: [CMake] Can't get CMake to link pthreads to my lib

[Rolf Eike Beer]

Am 2017-08-08 15:45, schrieb Jean-Michaël Celerier:

Here's my CMakeLists.txt :





cmake_minimum_required(VERSION 3.8 FATAL_ERROR)
project(oscour)
set(CMAKE_INCLUDE_CURRENT_DIR ON)

set(CMAKE_CXX_FLAGS "-fconcepts -fsanitize=address 
-fsanitize=undefined")

set(CMAKE_EXE_LINKER_FLAGS "-fconcepts -fsanitize=address
-fsanitize=undefined")

add_subdirectory(uWebSockets)


set(CMAKE_THREAD_PREFER_PTHREAD On)


find_package(Threads REQUIRED)


Greetings,

Eike
--
--

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] Can't get CMake to link pthreads to my lib

[Jean-Michaël Celerier]

Here's my CMakeLists.txt :

>>>

cmake_minimum_required(VERSION 3.8 FATAL_ERROR)
project(oscour)
set(CMAKE_INCLUDE_CURRENT_DIR ON)

set(CMAKE_CXX_FLAGS "-fconcepts -fsanitize=address -fsanitize=undefined")
set(CMAKE_EXE_LINKER_FLAGS "-fconcepts -fsanitize=address
-fsanitize=undefined")

add_subdirectory(uWebSockets)

find_package(Threads REQUIRED)

add_library(oscour INTERFACE)
target_sources(oscour INTERFACE
  ${CMAKE_CURRENT_SOURCE_DIR}/oscour/oscour.hpp)

target_include_directories(oscour INTERFACE oscour/)
target_link_libraries(oscour INTERFACE uWS Threads::Threads)
target_compile_options(oscour INTERFACE -std=c++17)

add_executable(udp examples/udp.cpp)
target_link_libraries(udp PRIVATE oscour)

add_executable(tcp examples/tcp.cpp)
target_link_libraries(tcp PRIVATE oscour)



As you can see, I call
find_package(Threads REQUIRED)
but at no point my example executables, named udp and tcp, link to -pthread
(or -lpthread) (which of course makes my build fails).
I also tried to link them explicitely to Threads::Threads. This did not
work either.

e.g. when doing make in verbose mode, the link invocation is :

 /usr/bin/g++ -fconcepts -fsanitize=address -fsanitize=undefined -std=c++17
-fconcepts -fsanitize=address -fsanitize=undefined
CMakeFiles/complete.dir/examples/udp.cpp.o  -o udp  uWebSockets/libuWS.a
/usr/lib/libssl.so /usr/lib/libcrypto.so /usr/lib/libz.so

there is no hint of pthreads in there... what can I do ?

Best

Jean-Michaël Celerier
http://www.jcelerier.name
-- 

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-commits] CMake branch, master, updated. v3.9.0-451-gdb6ea48

[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  db6ea482f6a9905e643b0c343cc545df936c71dc (commit)
   via  bfcda4013a52e81a1ffc2f10a6006ba75b9b607d (commit)
  from  3ce807f3925c1771d21e6ea5b2203208ac0186db (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=db6ea482f6a9905e643b0c343cc545df936c71dc
commit db6ea482f6a9905e643b0c343cc545df936c71dc
Merge: 3ce807f bfcda40
Author: Brad King 
AuthorDate: Tue Aug 8 13:29:41 2017 +
Commit: Kitware Robot 
CommitDate: Tue Aug 8 09:29:48 2017 -0400

Merge topic 'gtest-dynamic-discovery'

bfcda401 Add dynamic test discovery for for Google Test

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bfcda4013a52e81a1ffc2f10a6006ba75b9b607d
commit bfcda4013a52e81a1ffc2f10a6006ba75b9b607d
Author: Matthew Woehlke 
AuthorDate: Thu Jul 27 09:47:28 2017 -0400
Commit: Matthew Woehlke 
CommitDate: Thu Jul 27 09:47:28 2017 -0400

Add dynamic test discovery for for Google Test

Add a new gtest_discover_tests function to GoogleTest.cmake,
implementing dynamic test discovery (i.e. tests are discovered by
actually running the test executable and asking for the list of
available tests, which is used to dynamically declare the tests) rather
than the source-parsing approach used by gtest_add_tests. Compared to
the source-parsing approach, this has the advantage of being robust
against users declaring tests in unusual ways, and much better support
for advanced features such as parameterized tests.

A unit test, modeled after the TEST_INCLUDE_DIR[S] test, is also
included. Note that the unit test does not actually require that Google
Test is available. The new functionality does not actually depend on
Google Test as such; it only requires that the test executable lists
tests in the expected format when invoked with --gtest_list_tests, which
the unit test can fake readily.

diff --git a/Help/release/dev/GoogleTest.rst b/Help/release/dev/GoogleTest.rst
new file mode 100644
index 000..1e4a10e
--- /dev/null
+++ b/Help/release/dev/GoogleTest.rst
@@ -0,0 +1,11 @@
+GoogleTest
+--
+
+* The :module:`GoogleTest` module gained a new command
+  :command:`gtest_discover_tests` implementing dynamic (build-time) test
+  discovery.  Unlike the source parsing approach, dynamic discovery executes
+  the test (in 'list available tests' mode) at build time to discover tests.
+  This is robust against unusual ways of labeling tests, provides much better
+  support for advanced features such as parameterized tests, and does not
+  require re-running CMake to discover added or removed tests within a test
+  executable.
diff --git a/Modules/FindGTest.cmake b/Modules/FindGTest.cmake
index c4b4535..cb71ef1 100644
--- a/Modules/FindGTest.cmake
+++ b/Modules/FindGTest.cmake
@@ -71,7 +71,7 @@
 # ^
 #
 # See :module:`GoogleTest` for information on the :command:`gtest_add_tests`
-# command.
+# and :command:`gtest_discover_tests` commands.
 
 include(${CMAKE_CURRENT_LIST_DIR}/GoogleTest.cmake)
 
diff --git a/Modules/GoogleTest.cmake b/Modules/GoogleTest.cmake
index 7415e06..41bd1dc 100644
--- a/Modules/GoogleTest.cmake
+++ b/Modules/GoogleTest.cmake
@@ -5,7 +5,33 @@
 GoogleTest
 --
 
-This module defines functions to help use the Google Test infrastructure.
+This module defines functions to help use the Google Test infrastructure.  Two
+mechanisms for adding tests are provided. :command:`gtest_add_tests` has been
+around for some time, originally via ``find_package(GTest)``.
+:command:`gtest_discover_tests` was introduced in CMake 3.10.
+
+The (older) :command:`gtest_add_tests` scans source files to identify tests.
+This is usually effective, with some caveats, including in cross-compiling
+environments, and makes setting additional properties on tests more convenient.
+However, its handling of parameterized tests is less comprehensive, and it
+requires re-running CMake to detect changes to the list of tests.
+
+The (newer) :command:`gtest_discover_tests` discovers tests by asking the
+compiled test executable to enumerate its tests.  This is more robust and
+provides better handling of parameterized tests, and does not require CMake
+to be re-run when tests change.  However, it may not work in a cross-compiling
+environment, and setting test properties is less convenient.
+
+More details can 

[Cmake-commits] CMake branch, master, updated. v3.9.0-449-g3ce807f

[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  3ce807f3925c1771d21e6ea5b2203208ac0186db (commit)
   via  165778c8090401b05999688f7805c95b10bc85b0 (commit)
   via  e3bcf72df8ca77d2db42866b4d85fd230dea9b32 (commit)
   via  21e86adaf6cb8829538e52714df7114763dcd29c (commit)
   via  1c61d240ddd5fe493427a10ad571b662ded97eb8 (commit)
   via  07a4be0d9cf1a628db7e65ecae834a0c8e9d4278 (commit)
   via  e4ea628b42bcef9dafbc504a62d2b9c8cfc8521c (commit)
   via  44e5fb9c7ea3e3b0288cc24ec85554112e966d73 (commit)
   via  7e08602c761cabe75c557eacf738b716a4a1e18a (commit)
   via  6276ec3726ce4bb92748b0a70b1102e38924b626 (commit)
   via  49640d362981e918d94ef92c7a184749bbd7473d (commit)
   via  acd462dd314c599e4d7b9231723729fdcc189bee (commit)
  from  b17b6dbb8e57f159274deec9e458ab421bee09ff (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=3ce807f3925c1771d21e6ea5b2203208ac0186db
commit 3ce807f3925c1771d21e6ea5b2203208ac0186db
Merge: 165778c 07a4be0
Author: Brad King 
AuthorDate: Tue Aug 8 13:23:31 2017 +
Commit: Kitware Robot 
CommitDate: Tue Aug 8 09:23:34 2017 -0400

Merge topic 'FindPkgConfig-freebsd-pkgconfig-dir'

07a4be0d FindPkgConfig: On FreeBSD search in `libdata/pkgconfig`

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=165778c8090401b05999688f7805c95b10bc85b0
commit 165778c8090401b05999688f7805c95b10bc85b0
Merge: e3bcf72 1c61d24
Author: Brad King 
AuthorDate: Tue Aug 8 13:22:37 2017 +
Commit: Kitware Robot 
CommitDate: Tue Aug 8 09:22:42 2017 -0400

Merge topic 'ctest-launch-match-details'

1c61d240 CTest: Report lines matched by launchers

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e3bcf72df8ca77d2db42866b4d85fd230dea9b32
commit e3bcf72df8ca77d2db42866b4d85fd230dea9b32
Merge: 21e86ad e4ea628
Author: Brad King 
AuthorDate: Tue Aug 8 13:22:23 2017 +
Commit: Kitware Robot 
CommitDate: Tue Aug 8 09:22:25 2017 -0400

Merge topic 'update-expat'

e4ea628b expat: Update CMake build for 2.2.3
44e5fb9c Merge branch 'upstream-expat' into update-expat
7e08602c expat 2017-08-02 (97c6bd01)
6276ec37 expat: Update script to get Expat 2.2.3

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=21e86adaf6cb8829538e52714df7114763dcd29c
commit 21e86adaf6cb8829538e52714df7114763dcd29c
Merge: b17b6db 49640d3
Author: Brad King 
AuthorDate: Tue Aug 8 13:21:57 2017 +
Commit: Kitware Robot 
CommitDate: Tue Aug 8 09:22:00 2017 -0400

Merge topic 'drop-HP-UX'

49640d36 HP-UX: Drop support for building CMake on HP-UX
acd462dd README: Add AIX to list of supported platforms

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c61d240ddd5fe493427a10ad571b662ded97eb8
commit 1c61d240ddd5fe493427a10ad571b662ded97eb8
Author: Bill Hoffman 
AuthorDate: Thu Jul 27 12:30:34 2017 -0400
Commit: Brad King 
CommitDate: Mon Aug 7 11:01:49 2017 -0400

CTest: Report lines matched by launchers

Since launchers show the entire stderr/stdout for a command and only
skip it if all of the lines are suppressed, it can be hard to tell if
individual suppressions are working.  Mark up the output reported to
CDash with a prefix for each line indicating whether it was a matched or
suppressed warning.  Lines that are suppressed are prefixed with
`[CTest: warning suppressed]` and lines that match the warning
expression are prefixed with `[CTest: warning matched]`. This should
make it easier for people to add suppressions as they will know what
they need to match and what they have already suppressed. This is an
issue because if there is more than one warning in a single compiler
output you have to suppress all of them before it will go away.

diff --git a/Source/CTest/cmCTestLaunch.cxx b/Source/CTest/cmCTestLaunch.cxx
index 5b21351..9be8696 100644
--- a/Source/CTest/cmCTestLaunch.cxx
+++ b/Source/CTest/cmCTestLaunch.cxx
@@ -508,7 +508,11 @@ void cmCTestLaunch::DumpFileToXML(cmXMLWriter& xml, 

Re: [cmake-developers] Linking Apple frameworks

[Brad King]

On 08/07/2017 05:27 PM, Eric Wing wrote:
> I think that would be a mistake because it seems that the only purpose
> of this change would be so you could bypass CMake and try to directly
> invoke some kind of command line invocation on the dynamic library
> inside the .framework bundle.

The ld(1) man page on macOS says that "-framework foo" tells the
linker to search for "foo.framework/foo".  For linking this is very
similar to "-lfoo" searching for "libfoo.so" and "libfoo.a" in the
linker search path.  We discourage the latter because it is hard to
ensure that the proper library will be found.  I think framework
libraries should be linked by absolute path too.

For example, say one has these libraries in frameworks:

/path/A/foo.framework/foo  # want this one
/path/A/bar.framework/bar
/path/B/foo.framework/foo
/path/B/bar.framework/bar  # want this one

How does one achieve this case with Xcode's abstractions or with
the "-framework foo" flag?  CMake with imported targets already
achieves this, and links via absolute path to each library file.

> be treating the framework bundle as a whole because all parts of it
> are designed to be useful.

In cases where that is needed it is still possible to detect that
a library file is part of a framework.

> The bundle assets like any .nib files and
> the Info.plist are sometimes critical components of the framework. So
> things like copying the whole framework and embedding them in the app
> bundle are important things to do.
[snip]
> But if you did decide to change this, I think it should only happen in
> conjunction of solving the rest of the needed functionality for
> dealing with frameworks, i.e. copying the entire framework bundle into
> the app bundle, codesigning the framework in the app bundle,

We already have ways of doing those things at installation and
packaging time.  Linking the build-tree copy is too early.

-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-developers] iOS: direction to official support and questions

[Raffi Enficiaud]

Hi CMake ML,

I am quite new to the topic of making toolchain files. However I need to 
build a not so trivial application for iOS and I want to do it with 
CMake, and if possible walk toward an official support of iOS in CMake.


I have looked a bit to the Android toolchains, and I have to say I found 
those quite complicated as a first reading :)


The target application I am building uses Qt and Boost.

So far, I have managed to have an IOS toolchain file that is generating 
a looking good XCode project, that I can compile properly (up until 
signing).


I can share the toolchain file: it is a collection of things I have 
found on the internet, but trimmed from what I think was not necessary. 
It is still in a not so nice state, but I am currently cleaning it.


There are things that I think are weird though:

* I need to have:
```
set(CMAKE_FIND_ROOT_PATH
${CMAKE_IOS_DEVELOPER_ROOT}
${CMAKE_IOS_SDK_ROOT}
${CMAKE_PREFIX_PATH}
/path/to/boost_1_64_0_build/install
CACHE string  "iOS find search path root")
```

where this path is hard coded, and points to the fat static libraries 
prefix path of boost. If I remove this path, FindBoost does not find the 
boost libraries anymore (of course I am passing BOOST_ROOT). In 
addition, I have this:


```
set (CMAKE_SYSTEM_FRAMEWORK_PATH
${CMAKE_IOS_SDK_ROOT}/System/Library/Frameworks
${CMAKE_IOS_SDK_ROOT}/System/Library/PrivateFrameworks
${CMAKE_IOS_SDK_ROOT}/Developer/Library/Frameworks
)

set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
```

this looks ok to me, as we are cross compiling.
Is this a problem of FindBoost, or the combinations of the options that 
are not ok?


* I need to add:
```
set(CMAKE_MACOSX_BUNDLE YES)
set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED "NO")
```

and this comes from https://public.kitware.com/Bug/view.php?id=15329 . 
As I understand it, this is a problem of try_compile: as signing of 
application is required for generating a binary for iOS, this one fails 
very early when CMake discovers the capabilities of the compiler. Some 
people made a workaround by short-cutting the compiler checks, which is 
to me a wrong direction to take. As mentioned in this ticket, the right 
solution would be that the try_compile commands not to require signing 
of the binaries (or sthg similar).

This is explained here: http://public.kitware.com/Bug/view.php?id=12288

* is this one https://cmake.org/Bug/view.php?id=12640 addressed?

* I am seeing exchanges concerning the IOS_INSTALL_COMBINED. Does this 
has something to do with toolchain? What is meant by "installation" in 
this case? Sorry for my naive question, but I do not understand the 
workflow very well.


* how can I have unit tests of the toolchain in a CI fashion. Ideally, I 
would like to have a target cross-compiled with this toolchain, and then 
running the iPhoneSimulator, and check the result (return code, process, 
command whatever).

Does anyone have experience with this?

Thanks,
Raffi




--

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] with cmake-3.9 my testprj breaks, I need to add "add_executable(Qt4::rcc IMPORTED)"

[Rolf Eike Beer]

  (and we don't use find_lib(QT) because once upon a time it was
  tried but not instantly found working for cross compiling).

We're investigating whether we simply can switch to find_lib(QT)
which should solve that.

Does this make sense or am I mislead?


I have used it for crosscompiling in the CMake 3.x timeframe and it 
worked fine as long as qmake is properly set up (i.e. has it's qt.conf 
so it finds it's paths).


Eike
--

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] with 3.9 my testprj breaks: mylib_autogen/include: No such file or directory

[Steffen Dettmer]

Hi,

On Mon, Aug 7, 2017 at 8:04 PM, Brad King  wrote:
> On 08/07/2017 09:01 AM, Steffen Dettmer wrote:
> > There is an include path to mylib_autogen/include as -I for g++, but
> > this directory does not exist and I get:
> >
> >   cc1plus: error [...] No such file or directory.
>
> Please open an issue for this and provide a sample project
> showing the problem.

thanks for your quick reply. With many iterations I was able to create
a very small example and opened an issue:

  https://gitlab.kitware.com/cmake/cmake/issues/17147

for it.

Steffen
-- 

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] CMake 3.9.0 Windows zip file shows wrong version

[David Cole via CMake]

I suspect you are running a different cmake, not the one you've unzipped.

Type "where cmake" instead of "cmake --version" and Windows will list
the directories where it finds an executable named cmake. The first
one it lists is the one it is running when you type "cmake
--version"...

If you want to force the one you've downloaded to run instead of that
one, you could **prepend** to the PATH instead of appending to it.


HTH,
David C.



On Mon, Aug 7, 2017 at 9:07 PM, Adam Getchell  wrote:
> Hi all,
>
> The CMake 3.9.0 Windows zip file gives the wrong version. Here’s a snippet
> from my AppVeyor logs [1]:
>
> set CMAKE_URL="https://cmake.org/files/v3.9/cmake-3.9.0-win64-x64.zip;
> appveyor DownloadFile %CMAKE_URL% -FileName cmake.zip
> Downloading cmake.zip (25,944,520 bytes)...100%
> 7z x cmake.zip -oC:\projects\dev
> 7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04
> Scanning the drive for archives:
> 1 file, 25944520 bytes (25 MiB)
> Extracting archive: cmake.zip
> --
> Path = cmake.zip
> Type = zip
> Physical Size = 25944520
> Everything is Ok
> Folders: 90
> Files: 4922
> Size: 66584952
> Compressed: 25944520
> set PATH=%PATH%;C:\projects\dev\cmake\bin
> cmake --version
> cmake version 3.8.2
> CMake suite maintained and supported by Kitware (kitware.com/cmake).
>
> [1] https://ci.appveyor.com/project/acgetchell/cdt-plusplus
> --
> Adam Getchell
> https://keybase.io/adamgetchell
>
>
> --
>
> 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] with cmake-3.9 my testprj breaks, I need to add "add_executable(Qt4::rcc IMPORTED)"

[Steffen Dettmer]

Hi!

thanks for your quick reply.

On Mon, Aug 7, 2017 at 7:56 PM, Robert Maynard
 wrote:
> >  CMake Error: Qt4::rcc target not found hello_world
>
> Did this work pre CMake 3.9?

Yes, it did. However I missed that some of our CMakeLists.txt
has "add_executable(Qt4::moc IMPORTED)". So the change seems only
to be that before QT4::rcc was not checked, but supposed to be set
since all the time. It is integral part of QT so there is no
reason to have moc but not rcc.

A team mate said that this is because we don't use find_lib(QT)
which internally handles all that, and that cmake has to perform
a lot of "magic" for QT, as it is not just "an ordinary library"
but much more, formally even an own programming language.

  (and we don't use find_lib(QT) because once upon a time it was
  tried but not instantly found working for cross compiling).

We're investigating whether we simply can switch to find_lib(QT)
which should solve that.

Does this make sense or am I mislead?

Steffen
-- 

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] Yet another CMake 3.9 CUDA issue

[Mueller-Roemer, Johannes Sebastian]

I attached the -system-information output for the build. I was not able to 
glean anything useful from it though, as CMakeError.log is empty, as previously 
mentioned.

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

From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Mueller-Roemer, 
Johannes Sebastian
Sent: Monday, August 7, 2017 09:28
To: cmake@cmake.org
Subject: [CMake] Yet another CMake 3.9 CUDA issue

Hi,

after solving a different issue (lack of .NET 3.5 Framework causing the CUDA 
MSBuild component to not work, discussion thread "Visual Studio with CUDA does 
not work in 3.9") and getting good results (parallel CUDA builds, yay!), I now 
wanted to try CMake 3.9 on a different machine, but no success :(

The machine is running Windows Server 2012 R2 with Visual Studio 2015 (2012 is 
installed as well). The CUDA SDK is installed in versions 7.5 and 8.0. .Net 3.5 
is installed as well. However, the following error is reported:

CMake Error at 
E:/BuildTools/cmake/share/cmake-3.9/Modules/CMakeDetermineCompilerId.cmake:247 
(message):
  No CUDA toolset found.
Call Stack (most recent call first):
  E:/BuildTools/cmake/share/cmake-3.9/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  
E:/BuildTools/cmake/share/cmake-3.9/Modules/CMakeDetermineCUDACompiler.cmake:73 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


-- Configuring incomplete, errors occurred!
See also "C:/Users/buildbot/Desktop/test/build/CMakeFiles/CMakeOutput.log".

The CMakeOutput.log is also not very informative and only contains:
The system is: Windows - 6.3.9600 - AMD64

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.igdfraunhofer.de

Avoid ctest truncation of output: CTEST_FULL_OUTPUT

=== MAIN VARIABLES

CMAKE_STATIC_LIBRARY_PREFIX == ""
CMAKE_STATIC_LIBRARY_SUFFIX == ".lib"
CMAKE_SHARED_LIBRARY_PREFIX == ""
CMAKE_SHARED_LIBRARY_SUFFIX == ".dll"
CMAKE_SHARED_MODULE_PREFIX == ""
CMAKE_SHARED_MODULE_SUFFIX == ".dll"


CMAKE_DL_LIBS == ""
CMAKE_LIBRARY_PATH_FLAG == "-LIBPATH:"
CMAKE_LINK_LIBRARY_FLAG == ""
CMAKE_SKIP_RPATH == "NO"
CMAKE_SYSTEM_INFO_FILE == "Platform/Windows"
CMAKE_SYSTEM_NAME == "Windows"
CMAKE_SYSTEM == "Windows-6.3.9600"
CMAKE_CXX_COMPILER == "C:/Program Files (x86)/Microsoft Visual Studio 
14.0/VC/bin/x86_amd64/cl.exe"
CMAKE_C_COMPILER == "C:/Program Files (x86)/Microsoft Visual Studio 
14.0/VC/bin/x86_amd64/cl.exe"
CMAKE_COMPILER_IS_GNUCC == ""
CMAKE_COMPILER_IS_GNUCXX == ""

// C shared library flag
CMAKE_SHARED_LIBRARY_C_FLAGS == ""
CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS == "-shared"
CMAKE_SHARED_LIBRARY_LINK_FLAGS == ""
CMAKE_SHARED_LIBRARY_RUNTIME_FLAG == ""
CMAKE_SHARED_LIBRARY_RUNTIME_FLAG_SEP == ""
CMAKE_SHARED_LIBRARY_LINK_STATIC_C_FLAGS == ""
CMAKE_SHARED_LIBRARY_LINK_DYNAMIC_C_FLAGS == ""

// C shared module flags
CMAKE_SHARED_MODULE_C_FLAGS  == ""
CMAKE_SHARED_MODULE_CREATE_C_FLAGS == "-shared"
CMAKE_SHARED_MODULE_LINK_STATIC_C_FLAGS == ""
CMAKE_SHARED_MODULE_LINK_DYNAMIC_C_FLAGS == ""

// C exe flags
CMAKE_EXE_LINK_STATIC_C_FLAGS == ""
CMAKE_EXE_LINK_DYNAMIC_C_FLAGS == ""

// CXX shared library flags
CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS == "-shared"
CMAKE_SHARED_LIBRARY_CXX_FLAGS == ""
CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS == ""
CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG == ""
CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG_SEP == ""
CMAKE_SHARED_LIBRARY_LINK_STATIC_CXX_FLAGS == ""
CMAKE_SHARED_LIBRARY_LINK_DYNAMIC_CXX_FLAGS == ""

// CXX shared module flags
CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS == "-shared"
CMAKE_SHARED_MODULE_CXX_FLAGS == ""
CMAKE_SHARED_MODULE_LINK_STATIC_CXX_FLAGS == ""
CMAKE_SHARED_MODULE_LINK_DYNAMIC_CXX_FLAGS == ""

// CXX exe flags
CMAKE_EXE_LINK_STATIC_CXX_FLAGS == ""
CMAKE_EXE_LINK_DYNAMIC_CXX_FLAGS == ""

CMAKE_USER_MAKE_RULES_OVERRIDE == ""
CMAKE_VERBOSE_MAKEFILE == "FALSE"
CMAKE_BUILD_TYPE == ""
CMAKE_CXX_FLAGS == "/DWIN32 /D_WINDOWS /W3 /GR /EHsc"
CMAKE_CXX_FLAGS_DEBUG == "/MDd /Zi /Ob0 /Od /RTC1"
CMAKE_CXX_FLAGS_MINSIZEREL == "/MD /O1 /Ob1 /DNDEBUG"
CMAKE_CXX_FLAGS_RELEASE == "/MD /O2 /Ob2 /DNDEBUG"
CMAKE_CXX_FLAGS_RELWITHDEBINFO == "/MD /Zi /O2 /Ob1 /DNDEBUG"

CMAKE_C_FLAGS == "/DWIN32 /D_WINDOWS /W3"
CMAKE_C_FLAGS_DEBUG == "/MDd /Zi /Ob0 /Od /RTC1"
CMAKE_C_FLAGS_MINSIZEREL == "/MD /O1 /Ob1 /DNDEBUG"
CMAKE_C_FLAGS_RELEASE == "/MD /O2 /Ob2 /DNDEBUG"
CMAKE_C_FLAGS_RELWITHDEBINFO == "/MD /Zi /O2 /Ob1 /DNDEBUG"

// build rules