[Cmake-commits] CMake branch, master, updated. v3.11.1-545-g38d854d

2018-04-19 Thread 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  38d854dccff6ddeb69c217252dd9ed9f87fe1b19 (commit)
  from  c14497191bf4412b7b7f5241030f251373e4c0ae (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=38d854dccff6ddeb69c217252dd9ed9f87fe1b19
commit 38d854dccff6ddeb69c217252dd9ed9f87fe1b19
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Apr 20 00:01:09 2018 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Apr 20 00:01:09 2018 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index f32f2ee..7aadb3b 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 11)
-set(CMake_VERSION_PATCH 20180419)
+set(CMake_VERSION_PATCH 20180420)
 #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
https://cmake.org/mailman/listinfo/cmake-commits

[CMake] Experiments in CMake support for Clang (header & standard) modules

2018-04-19 Thread David Blaikie 
Hi there,

I'm experimenting with creating examples (& potential changes to CMake
itself, if needed/useful) of building clang modules (currently using the
semi-backwards compatible "header modules", with the intent of also/moving
towards supporting pre-standard C++ modules in development in Clang).

The basic commands required are:

  clang++ -fmodules -xc++ -Xclang -emit-module -Xclang -fmodules-codegen
-fmodule-name=foo foo.modulemap -o foo.pcm
  clang++ -fmodules -c -fmodule-file=foo.pcm use.cpp
  clang++ -c foo.pcm
  clang++ foo.o use.o -o a.out

My current very simplistic prototype, to build a module file, its
respective module object file, and include those in the library/link for
anything that depends on this library:

  add_custom_command(
  COMMAND ${CMAKE_CXX_COMPILER} ${CMAKE_CXX_FLAGS} -xc++ -c -Xclang
-emit-module -fmodules -fmodule-name=Hello
${CMAKE_CURRENT_SOURCE_DIR}/module.modulemap -o
${CMAKE_CURRENT_BINARY_DIR}/hello_module.pcm -Xclang -fmodules-codegen
  DEPENDS module.modulemap hello.h
  OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/hello_module.pcm
  COMMENT "Generating hello_module.pcm"
  )
  add_library (Hello hello.cxx ${CMAKE_CURRENT_BINARY_DIR}/hello_module.pcm)
  target_include_directories(Hello PUBLIC ${CMAKE_CURRENT_SOURCE_DIR})
  target_compile_options(Hello PUBLIC -fmodules -Xclang
-fmodule-file=${CMAKE_CURRENT_BINARY_DIR}/hello_module.pcm)

(this is based on the example in the CMake docs using Hello/Demo)

This also required one modification to CMake itself to classify a pcm file
as a C++ file that needs to be compiled (to execute the 3rd line in the
basic command list shown above).

But this isn't ideal - I don't /think/ I've got the dependencies quite
right & things might not be rebuilding at the right times.
Also it involves hardcoding a bunch of things like the pcm file names,
header files, etc.

Ideally, at least for a simplistic build, I wouldn't mind generating a
modulemap from all the .h files (& have those headers listed in the
add_library command - perhaps splitting public and private headers in some
way, only including the public headers in the module file, likely).
Eventually for the standards-proposal version, it's expected that there
won't be any modulemap file, but maybe all headers are included in the
module compilation (just pass the headers directly to the compiler).

This also doesn't start to approach the issue of how to build modules for
external libraries - which I'm happy to discuss/prototype too, though
interested in working to streamline the inter-library but intra-project
(not inter-project) case first.

Stephen - I saw you were asking some questions about this here (
https://groups.google.com/a/isocpp.org/forum/#!topic/modules/sDIYoU8Uljw &
https://github.com/steveire/ModulesExperiments - didn't really understand
how this example applied/worked, though - I guess maybe it's a prototype
syntax proposal?)

Basically: What do folks think about supporting these sort of features in
CMake C++ Builds? Any pointers on how I might best implement this with or
without changes to CMake?

Thanks a bunch,
- Dave
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Zaak Beekman 
Thanks Jano, that's the work flow I was considering.

On Thu, Apr 19, 2018 at 5:33 PM Jano Svitok  wrote:

> You don't have to install cmake. Just get the zip version, unzip in
> somewhere along your sources and you are done.
> I'm not sure whether any runtime dlls are needed, but I suppose not.
>
> We use cmake like that. We've committed a copy in our git repo, and have a
> simple means to update cmake for everyone
> in the team at once.
>
> Jano
>
> On Thu, Apr 19, 2018 at 6:55 PM, Zaak Beekman  wrote:
>
>> Ha, yeah that’s an option. The problem is that they’re not “my”
>> contractors. They are the client’s contractors. We’ll see.
>> On Thu, Apr 19, 2018 at 12:52 PM Cristian Adam 
>> wrote:
>>
>>> On Thu, Apr 19, 2018 at 5:46 PM, Zaak Beekman 
>>> wrote:
>>>
 The situation is that we have a client who works with other contractors
 who use almost exclusively windows and MSVS. This client wants to
 distribute MSVS solution files with the source code so that other
 contractors don’t have to install cmake. (There are some restrictions/red
 tape for installing additional software on the contractor machines…)

>>>
>>> Why not distribute CMake as source code? Compile it so that they don't
>>> have to "install" it.
>>>
>>> On the other hand Visual Studio 2017 comes with their own version of
>>> CMake! Just make sure your contractors use VS2017 :D
>>>
>>> Cheers,
>>> Cristian.
>>>
>>>
>>
>> --
>>
>
>> 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:
>> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Jano Svitok 
You don't have to install cmake. Just get the zip version, unzip in
somewhere along your sources and you are done.
I'm not sure whether any runtime dlls are needed, but I suppose not.

We use cmake like that. We've committed a copy in our git repo, and have a
simple means to update cmake for everyone
in the team at once.

Jano

On Thu, Apr 19, 2018 at 6:55 PM, Zaak Beekman  wrote:

> Ha, yeah that’s an option. The problem is that they’re not “my”
> contractors. They are the client’s contractors. We’ll see.
> On Thu, Apr 19, 2018 at 12:52 PM Cristian Adam 
> wrote:
>
>> On Thu, Apr 19, 2018 at 5:46 PM, Zaak Beekman  wrote:
>>
>>> The situation is that we have a client who works with other contractors
>>> who use almost exclusively windows and MSVS. This client wants to
>>> distribute MSVS solution files with the source code so that other
>>> contractors don’t have to install cmake. (There are some restrictions/red
>>> tape for installing additional software on the contractor machines…)
>>>
>>
>> Why not distribute CMake as source code? Compile it so that they don't
>> have to "install" it.
>>
>> On the other hand Visual Studio 2017 comes with their own version of
>> CMake! Just make sure your contractors use VS2017 :D
>>
>> Cheers,
>> Cristian.
>>
>>
>
> --
>
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Zaak Beekman 
Ha, yeah that’s an option. The problem is that they’re not “my”
contractors. They are the client’s contractors. We’ll see.
On Thu, Apr 19, 2018 at 12:52 PM Cristian Adam 
wrote:

> On Thu, Apr 19, 2018 at 5:46 PM, Zaak Beekman  wrote:
>
>> The situation is that we have a client who works with other contractors
>> who use almost exclusively windows and MSVS. This client wants to
>> distribute MSVS solution files with the source code so that other
>> contractors don’t have to install cmake. (There are some restrictions/red
>> tape for installing additional software on the contractor machines…)
>>
>
> Why not distribute CMake as source code? Compile it so that they don't
> have to "install" it.
>
> On the other hand Visual Studio 2017 comes with their own version of
> CMake! Just make sure your contractors use VS2017 :D
>
> Cheers,
> Cristian.
>
>
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Cristian Adam 
On Thu, Apr 19, 2018 at 5:46 PM, Zaak Beekman  wrote:

> The situation is that we have a client who works with other contractors
> who use almost exclusively windows and MSVS. This client wants to
> distribute MSVS solution files with the source code so that other
> contractors don’t have to install cmake. (There are some restrictions/red
> tape for installing additional software on the contractor machines…)
>

Why not distribute CMake as source code? Compile it so that they don't have
to "install" it.

On the other hand Visual Studio 2017 comes with their own version of CMake!
Just make sure your contractors use VS2017 :D

Cheers,
Cristian.
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Zaak Beekman 
On Thu, Apr 19, 2018 at 11:51 AM Konstantin Tokarev 
wrote:

> Then your best choice is probably Premake (http://premake.github.io/)
>

No.

Big project. Have build system. CMake has 1st class language support for
Fortran. I can't introduce a LUA dependency.
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Konstantin Tokarev 


19.04.2018, 18:46, "Zaak Beekman" :
> Greetings fellow CMake users!
>
> While I know this topic has been discussed intermittently over the years I 
> was wondering if anyone had any further insight.
>
> The situation is that we have a client who works with other contractors who 
> use almost exclusively windows and MSVS. This client wants to distribute MSVS 
> solution files with the source code so that other contractors don’t have to 
> install cmake. (There are some restrictions/red tape for installing 
> additional software on the contractor machines…)

Then your best choice is probably Premake (http://premake.github.io/)

>
> I know the official party line is “CMake must use absolute paths, rerun CMake 
> to regenerate the MSVS solution files.” I also know that 
> CMAKE_USE_RELATIVE_PATHS was abandoned.
>
> Does anyone have any updated insight on this issue? Is there any mechanism, 
> other than either manually or automatically editing the solution files to 
> cause them to use relative paths?
>
> Another thought might be to include a statically linked CMake windows binary 
> with the source, but I need to investigate whether the CMake licensing allows 
> for that.
>
> Thanks,
> Zaak
>
> Izaak "Zaak" Beekman
>
> ---
> HPC Scientist
> ParaTools Inc.
> ibeek...@paratools.com
> 1509 16th St, NW
> Washington, DC 20036
> mobile: (917) 797-3239
> ---
> ​
>
> ,--
>
> 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:
> https://cmake.org/mailman/listinfo/cmake


-- 
Regards,
Konstantin
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Generating MSVS solution files that can be passed around

2018-04-19 Thread Zaak Beekman 
Greetings fellow CMake users!

While I know this topic has been discussed intermittently over the years

I was wondering if anyone had any further insight.

The situation is that we have a client who works with other contractors who
use almost exclusively windows and MSVS. This client wants to distribute
MSVS solution files with the source code so that other contractors don’t
have to install cmake. (There are some restrictions/red tape for installing
additional software on the contractor machines…)

I know the official party line is “CMake must use absolute paths, rerun
CMake to regenerate the MSVS solution files.” I also know that
CMAKE_USE_RELATIVE_PATHS was abandoned.

Does anyone have any updated insight on this issue? Is there any mechanism,
other than either manually or automatically editing the solution files to
cause them to use relative paths?

Another thought might be to include a statically linked CMake windows
binary with the source, but I need to investigate whether the CMake
licensing allows for that.

Thanks,
Zaak

Izaak "Zaak" Beekman

---

HPC Scientist
ParaTools Inc. 
ibeek...@paratools.com
1509 16th St, NW
Washington, DC 20036
mobile: (917) 797-3239
---
​
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.11.1-544-gc144971

2018-04-19 Thread 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  c14497191bf4412b7b7f5241030f251373e4c0ae (commit)
   via  1a2eb621053c3f32c6eca2a962af436c0bd1044a (commit)
   via  c86386caa3b4ace68573b1eeea45da40f304db3f (commit)
   via  87f2cf3b1ce0ef7b8e71eae0f44cf9753660d423 (commit)
   via  13952a3b7fb930baeeda299bf186e29d57d794fe (commit)
   via  1f6649b7d118e9de2a51c9e48b5fea527f608fc1 (commit)
   via  8d07408a62c03123c0c49b9946025930d1d61e16 (commit)
   via  e70da3f0f3fe2f4373152953ba9822ce0f368cf5 (commit)
  from  423de692f91fada3b060359dd52608de29ac3a3a (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=c14497191bf4412b7b7f5241030f251373e4c0ae
commit c14497191bf4412b7b7f5241030f251373e4c0ae
Merge: 1a2eb62 87f2cf3
Author: Brad King 
AuthorDate: Thu Apr 19 12:26:28 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:26:34 2018 -0400

Merge topic 'FindJPEG-imported-targets'

87f2cf3b1c FindJPEG: Add imported target support and full test
13952a3b7f FindJPEG: Add multi config support and associated docs
1f6649b7d1 FindJPEG: Add version detection and associated test update and 
docs
8d07408a62 FindJPEG: Cleanup documentation formatting
e70da3f0f3 FindJPEG: Clean up whitepaces and lowercase function names

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1a2eb621053c3f32c6eca2a962af436c0bd1044a
commit 1a2eb621053c3f32c6eca2a962af436c0bd1044a
Merge: 423de69 c86386c
Author: Brad King 
AuthorDate: Thu Apr 19 08:25:05 2018 -0400
Commit: Brad King 
CommitDate: Thu Apr 19 08:25:05 2018 -0400

Merge branch 'release-3.11'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=87f2cf3b1ce0ef7b8e71eae0f44cf9753660d423
commit 87f2cf3b1ce0ef7b8e71eae0f44cf9753660d423
Author: Mateusz Loskot 
AuthorDate: Tue Apr 17 23:52:53 2018 +0200
Commit: Brad King 
CommitDate: Wed Apr 18 08:59:06 2018 -0400

FindJPEG: Add imported target support and full test

diff --git a/Help/release/dev/FindJPEG-imported-targets.rst 
b/Help/release/dev/FindJPEG-imported-targets.rst
new file mode 100644
index 000..32cf2f6
--- /dev/null
+++ b/Help/release/dev/FindJPEG-imported-targets.rst
@@ -0,0 +1,4 @@
+FindJPEG-imported-targets
+-
+
+* The :module:`FindJPEG` module now provides imported targets.
diff --git a/Modules/FindJPEG.cmake b/Modules/FindJPEG.cmake
index fa4f3a1..9542f69 100644
--- a/Modules/FindJPEG.cmake
+++ b/Modules/FindJPEG.cmake
@@ -7,6 +7,14 @@
 #
 # Find the JPEG library (libjpeg)
 #
+# Imported targets
+# 
+#
+# This module defines the following :prop_tgt:`IMPORTED` targets:
+#
+# ``JPEG::JPEG``
+#   The JPEG library, if found.
+#
 # Result variables
 # 
 #
@@ -14,7 +22,7 @@
 #
 # ``JPEG_FOUND``
 #   If false, do not try to use JPEG.
-# ``JPEG_INCLUDE_DIR``
+# ``JPEG_INCLUDE_DIRS``
 #   where to find jpeglib.h, etc.
 # ``JPEG_LIBRARIES``
 #   the libraries needed to use JPEG.
@@ -26,7 +34,7 @@
 #
 # The following cache variables may also be set:
 #
-# ``JPEG_INCLUDE_DIR``
+# ``JPEG_INCLUDE_DIRS``
 #   where to find jpeglib.h, etc.
 # ``JPEG_LIBRARY_RELEASE``
 #   where to find the JPEG library (optimized).
@@ -36,6 +44,8 @@
 # Obsolete variables
 # ^^
 #
+# ``JPEG_INCLUDE_DIR``
+#   where to find jpeglib.h, etc. (same as JPEG_INCLUDE_DIRS)
 # ``JPEG_LIBRARY``
 #   where to find the JPEG library.
 
@@ -82,6 +92,34 @@ find_package_handle_standard_args(JPEG
 
 if(JPEG_FOUND)
   set(JPEG_LIBRARIES ${JPEG_LIBRARY})
+  set(JPEG_INCLUDE_DIRS "${JPEG_INCLUDE_DIR}")
+
+  if(NOT TARGET JPEG::JPEG)
+add_library(JPEG::JPEG UNKNOWN IMPORTED)
+if(JPEG_INCLUDE_DIRS)
+  set_target_properties(JPEG::JPEG PROPERTIES
+INTERFACE_INCLUDE_DIRECTORIES "${JPEG_INCLUDE_DIRS}")
+endif()
+if(EXISTS "${JPEG_LIBRARY}")
+  set_target_properties(JPEG::JPEG PROPERTIES
+IMPORTED_LINK_INTERFACE_LANGUAGES "C"
+IMPORTED_LOCATION "${JPEG_LIBRARY}")
+endif()
+if(EXISTS "${JPEG_LIBRARY_RELEASE}")
+  set_property(TARGET JPEG::JPEG APPEND PROPERTY
+IMPORTED_CONFIGURATIONS RELEASE)
+  set_target_properties(JPEG::JPEG PROPERTIES
+IMPORTED_LINK_INTERFACE_LANGUAGES_RELEASE "C"
+IMPORTED_LOCATION_RELEASE "${JPEG_LIBRARY_RELEASE}")
+endif()
+if(EXISTS "${JPEG_LIBRARY_DEBUG}")
+  set_property(TARGET

[Cmake-commits] CMake branch, release, updated. v3.11.1-2-gc86386c

2018-04-19 Thread 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  c86386caa3b4ace68573b1eeea45da40f304db3f (commit)
   via  bdf660cab5234aa5e533691b0fe03c0766c9a9f0 (commit)
  from  fbe6cd1596bf280edd49aeb8f981f99d7cd8beb3 (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/InstallRequiredSystemLibraries.cmake |8 
 1 file changed, 8 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.11.1-536-g423de69

2018-04-19 Thread 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  423de692f91fada3b060359dd52608de29ac3a3a (commit)
   via  c4a2059eae1473db68fad8980d15d8200cc3e739 (commit)
   via  3c6388553aef091556b64daf9bcb6f64fbdcdba2 (commit)
   via  6c13ddd6cb0c51afd2789db34b41416b5706336b (commit)
   via  541b53375de703ad5bb7a90cd72beefbb5452f96 (commit)
   via  bdf660cab5234aa5e533691b0fe03c0766c9a9f0 (commit)
   via  909ab169eb83f0a60f717aa87c5549e77e09e35f (commit)
   via  a61ae3fb8017a297bd3f3efc447a1f1f29619bdf (commit)
   via  391a5837ee859c749c2a988eb873a2a9a2c58f91 (commit)
   via  3c47ac5b2571939f7d987d9f23a9969b1f67f46e (commit)
   via  459739678443d2d2074d6e1475e4267c6c110e05 (commit)
   via  e95b3fd9bbca94cb5f217847031c9c8f393aee78 (commit)
   via  84f9f63fccdadb9b8a0bdb3260a0c7a3f71cb251 (commit)
   via  9fa0f2eb5638b5863c573c0ef1922d4cb2c729d5 (commit)
   via  d67962c55a4be2653d40b27c4f5fc38fc5c223b0 (commit)
  from  67752aece33ca0643a354ce0f2037afc66d15bfc (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=423de692f91fada3b060359dd52608de29ac3a3a
commit 423de692f91fada3b060359dd52608de29ac3a3a
Merge: c4a2059 bdf660c
Author: Brad King 
AuthorDate: Thu Apr 19 12:24:32 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:24:40 2018 -0400

Merge topic 'InstallRequiredSystemLibraries-mfcm'

bdf660cab5 InstallRequiredSystemLibraries: Check for existence of mfcm dlls

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c4a2059eae1473db68fad8980d15d8200cc3e739
commit c4a2059eae1473db68fad8980d15d8200cc3e739
Merge: 3c63885 d67962c
Author: Brad King 
AuthorDate: Thu Apr 19 12:23:48 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:23:52 2018 -0400

Merge topic 'depfile-flag'

d67962c55a SunPro,XL: Add depfile flags to support Ninja generator

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3c6388553aef091556b64daf9bcb6f64fbdcdba2
commit 3c6388553aef091556b64daf9bcb6f64fbdcdba2
Merge: 6c13ddd a61ae3f
Author: Brad King 
AuthorDate: Thu Apr 19 12:23:05 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:23:08 2018 -0400

Merge topic 'CheckIncludeFile-required-libs'

a61ae3fb80 CheckIncludeFiles: Honor CMAKE_REQUIRED_LIBRARIES
391a5837ee cmake_policy: Add undocumented PARENT_SCOPE option to GET
3c47ac5b25 OpenWatcom: Add workaround for lack of error on missing library

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6c13ddd6cb0c51afd2789db34b41416b5706336b
commit 6c13ddd6cb0c51afd2789db34b41416b5706336b
Merge: 541b533 909ab16
Author: Brad King 
AuthorDate: Thu Apr 19 12:20:56 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:21:00 2018 -0400

Merge topic 'doc-synopsis-markup'

909ab169eb Help: Fix command-line synopsis markup syntax

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=541b53375de703ad5bb7a90cd72beefbb5452f96
commit 541b53375de703ad5bb7a90cd72beefbb5452f96
Merge: 67752ae 4597396
Author: Brad King 
AuthorDate: Thu Apr 19 12:20:08 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 19 08:20:15 2018 -0400

Merge topic '17870-effective-system-name'

4597396784 Apple: Use include_guard() within compiler config
e95b3fd9bb Apple: Use CMAKE_EFFECTIVE_SYSTEM_NAME to share compiler info
84f9f63fcc Modules: Introduce CMAKE_EFFECTIVE_SYSTEM_NAME to lookup 
compiler info
9fa0f2eb56 CMakeFindPackageMode: Perform platform-specific initialization

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bdf660cab5234aa5e533691b0fe03c0766c9a9f0
commit bdf660cab5234aa5e533691b0fe03c0766c9a9f0
Author: Christof Krüger 
AuthorDate: Wed Apr 18 02:05:33 2018 -0400
Commit: Brad King 
CommitDate: Wed Apr 18 09:18:57 2018 -0400

InstallRequiredSystemLibraries: Check for existence of mfcm dlls

Previously, only existence of `mfc${v}.dll` and