[CMake] CMake on OpenVMS

2015-09-04 Thread Custin, Jay (CSC Sw Middleware) 
Has ANYONE actually gotten CMake working on OpenVMS?  I see numerous traces of 
OpenVMS riddled throughout the configuration/bootstrap code, but after spending 
almost two solid days trying to get past the "Configure" phase I have decided I 
needed to formally inquire.

SenseiC
-- 

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 [nmake target] is adding backslash at end of cd command

2015-09-04 Thread André Netzeband 

Hi

I have a very strange issue with generated nmake makefiles from cmake 3.3.1
In a very complex project with many sub-cmake files (Ogre3D) the 
generated nmake makefiles (build.make) contain backslashes at the end of 
some cd commands. Like this:


lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\BaseSystem.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\CameraController.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\GameEntityManager.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\GraphicsSystem.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\LogicSystem.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\SdlInputHandler.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\Threading\MessageQueueSystem.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\TutorialGameState.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\src\Utils\HdrUtils.cpp.obj
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\build.make
lib\OgreSamplesCommon_d.lib: 
Samples\2.0\Common\CMakeFiles\OgreSamplesCommon.dir\objects1.rsp
@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --green 
--bold 
--progress-dir=D:\Projects\CPP\Libraries\Ogre3D\ogre\build-vc64\CMakeFiles 
--progress-num=$(CMAKE_PROGRESS_10) "Linking CXX static library 
..\..\..\lib\OgreSamplesCommon_d.lib"

cd Samples\2.0\Common
$(CMAKE_COMMAND) -P 
CMakeFiles\OgreSamplesCommon.dir\cmake_clean_target.cmake

cd ..\..\..\
cd Samples\2.0\Common
D:\Compiler\MVS14.0\VC\bin\amd64\link.exe /lib 
/out:..\..\..\lib\OgreSamplesCommon_d.lib 
@CMakeFiles\OgreSamplesCommon.dir\objects1.rsp

cd ..\..\..\

Unfortunately these backslashes at the end of cd ..\..\..\ are 
interpreted as multi-line backslashes. Thus the makefile will not do this:

cd ..\..\..
cd Samples\2.0\Common

But it will do this:
cd ..\..\.. cd Samples\2.0\Common

And of course this is not a correct command.
I searched a lot in the internet to find a hint, how to prevent such a 
behaviour, but I was not able to find any answer. Also all the other 
projects I have compiled that uses cmake do not have a single cd in the 
build.make file. So I was not able to check if this is a general issue 
of cmake.


Is this an error of cmake or is something wrong configured in the project?
What forces cmake in this project to change the directory so often and 
why does cmake not add any cd commands to other project using cmake? Is 
there an option to prevent cd-command generation and using absolute 
paths for all files?


Best regards,
André
--

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 on OpenVMS (some clarification)

2015-09-04 Thread Custin, Jay (CSC Sw Middleware) 
While I specifically want this on OpenVMS/Integrity (V8.3 or higher), I have 
not tried this on an Alpha yet (vast majority of the coding/builds I do involve 
the Integrity platform).  It took some manual editing of files, etc. to get 
this far:

<>
CXX has ios::binary openmode
-
CXX  -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -I/PRJ_ROOT/CMAKE-3_3_1/Source   
-I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c /PRJ_ROOT/CMAKE
-3_3_1/Source/cmake.cxx -o cmake.o

#ifndef cmIML_ABI_H
.^
%CXX-E-MISSINGENDIF, the #endif for this directive is missing
at line number 33 in file LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]ABI.h;4

cmIML_INT__VERIFY_TYPE(cmIML_INT_intptr_t,  sizeof(void*));
^
%CXX-E-NOTCOMPREDEC, declaration is incompatible with
  "int (*cmIML_INT_intptr_t__VERIFY__)[4U]" (declared at line 839)
at line number 839 in file LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]INT.h;23
<

I have the GNU Not VMS (GNV) Bash environment with the latest code base for GNV 
(including Perl 5.22) and CMake (3.3.1).
-- 

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] Protobuf Libraries not found on OS X

2015-09-04 Thread Daniel Schepler 
Doesn't CMAKE_PREFIX_PATH work for you?
--
Daniel Schepler

From: CMake [cmake-boun...@cmake.org] on behalf of Michael Jackson 
[mike.jack...@bluequartz.net]
Sent: Friday, September 04, 2015 10:33 AM
To: CMake list
Subject: Re: [CMake] Protobuf Libraries not found on OS X

Odd, I built from source and there does not seem to be any way to add a custom 
search path (akin to QtDir or something like that) for the searching. I added a 
few lines to the FindProtobuf.cmake file to make it look for "Protobuf_DIR" as 
an environment variable. If I installed it into /usr/local I bit the default 
paths would find it.

I guess I could submit the patch as a bug report for the next version of CMake.

Thanks
Mike Jackson
On Sep 4, 2015, at 11:53 AM, Nils Guillermin 
> wrote:

I'm on Mac OS X 10.10.4 and I use protobuf installed through homebrew.

Nils

On Thu, Sep 3, 2015 at 1:48 PM, Michael Jackson 
> wrote:
I have compiled the Protocol Buffer library on OS X and I am using the 
following CMake code to try and find the compiled libraries:

find_package(Protobuf REQUIRED)


but when configuring I get the usual

CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
PROTOBUF_LIBRARY (ADVANCED)

Looking at the FindProtobuf.cmake file that came with CMake 3.3.0 it looks like 
the module would ONLY work with MSVC built Protobuf libraries as the specific 
paths that are searched for are Visual Studio specific. Is this the correct 
behavior? Does anyone else use Protobuffers on OS X? I am thinking of rolling 
my on FindProtobuf.cmake file to have cmake look in more places.

---
Mike Jackson

--

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 on OpenVMS (some clarification)

2015-09-04 Thread Bill Hoffman 

On 9/4/2015 9:42 AM, Custin, Jay (CSC Sw Middleware) wrote:

While I specifically want this on OpenVMS/Integrity (V8.3 or higher), I
have not tried this on an Alpha yet (vast majority of the coding/builds
I do involve the Integrity platform).  It took some manual editing of
files, etc. to get this far:

<>

CXX has ios::binary openmode

-

CXX -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -I/PRJ_ROOT/CMAKE-3_3_1/Source
-I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c /PRJ_ROOT/CMAKE

-3_3_1/Source/cmake.cxx -o cmake.o

#ifndef cmIML_ABI_H

.^

%CXX-E-MISSINGENDIF, the #endif for this directive is missing

at line number 33 in file LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]ABI.h;4

cmIML_INT__VERIFY_TYPE(cmIML_INT_intptr_t,  sizeof(void*));

^

%CXX-E-NOTCOMPREDEC, declaration is incompatible with

   "int (*cmIML_INT_intptr_t__VERIFY__)[4U]" (declared at line 839)

at line number 839 in file
LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]INT.h;23

<

I have the GNU Not VMS (GNV) Bash environment with the latest code base
for GNV (including Perl 5.22) and CMake (3.3.1).

I worked on this years ago.  I did manage to get most of it working, but 
no one ever setup a dashboard for it, so I am sure it fails now.   If 
you do manage to get it working it would be great if you could run a 
nightly dashboard... :)


-Bill


--

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] New to cmake and I have a problem.

2015-09-04 Thread Jay Cotton 
Hi:

I need to add an 'S' to the ar flags.  Now, I have found that I can edit
the link.txt file but,
this is not a real solution.  I am certain there is a way to do this with
the CMakeCache.txt file.
I just don't see how.  Any help would be appreciated.

tnx

JC
-- 

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] Protobuf Libraries not found on OS X

2015-09-04 Thread Michael Jackson 
It _should_. I think this was a case of "operator" error. Not sure I defined 
CMAKE_PREFIX_PATH properly with the path to the protobuf libraries. I'll give 
that a try and I am sure that it will work properly.

Thanks for the sanity check
Mike J.

On Sep 4, 2015, at 2:59 PM, Daniel Schepler  
wrote:

> Doesn't CMAKE_PREFIX_PATH work for you?
> -- 
> Daniel Schepler
> From: CMake [cmake-boun...@cmake.org] on behalf of Michael Jackson 
> [mike.jack...@bluequartz.net]
> Sent: Friday, September 04, 2015 10:33 AM
> To: CMake list
> Subject: Re: [CMake] Protobuf Libraries not found on OS X
> 
> Odd, I built from source and there does not seem to be any way to add a 
> custom search path (akin to QtDir or something like that) for the searching. 
> I added a few lines to the FindProtobuf.cmake file to make it look for 
> "Protobuf_DIR" as an environment variable. If I installed it into /usr/local 
> I bit the default paths would find it.
> 
> I guess I could submit the patch as a bug report for the next version of 
> CMake.
> 
> Thanks
> Mike Jackson
> On Sep 4, 2015, at 11:53 AM, Nils Guillermin  
> wrote:
> 
>> I'm on Mac OS X 10.10.4 and I use protobuf installed through homebrew.
>> 
>> Nils
>> 
>> On Thu, Sep 3, 2015 at 1:48 PM, Michael Jackson 
>>  wrote:
>> I have compiled the Protocol Buffer library on OS X and I am using the 
>> following CMake code to try and find the compiled libraries:
>> 
>> find_package(Protobuf REQUIRED)
>> 
>> 
>> but when configuring I get the usual
>> 
>> CMake Error: The following variables are used in this project, but they are 
>> set to NOTFOUND.
>> Please set them or make sure they are set and tested correctly in the CMake 
>> files:
>> PROTOBUF_LIBRARY (ADVANCED)
>> 
>> Looking at the FindProtobuf.cmake file that came with CMake 3.3.0 it looks 
>> like the module would ONLY work with MSVC built Protobuf libraries as the 
>> specific paths that are searched for are Visual Studio specific. Is this the 
>> correct behavior? Does anyone else use Protobuffers on OS X? I am thinking 
>> of rolling my on FindProtobuf.cmake file to have cmake look in more places.
>> 
>> ---
>> Mike Jackson
>> 
>> --
>> 
>> 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] Protobuf Libraries not found on OS X

2015-09-04 Thread Michael Jackson 
Odd, I built from source and there does not seem to be any way to add a custom 
search path (akin to QtDir or something like that) for the searching. I added a 
few lines to the FindProtobuf.cmake file to make it look for "Protobuf_DIR" as 
an environment variable. If I installed it into /usr/local I bit the default 
paths would find it.

I guess I could submit the patch as a bug report for the next version of CMake.

Thanks
Mike Jackson
On Sep 4, 2015, at 11:53 AM, Nils Guillermin  wrote:

> I'm on Mac OS X 10.10.4 and I use protobuf installed through homebrew.
> 
> Nils
> 
> On Thu, Sep 3, 2015 at 1:48 PM, Michael Jackson  
> wrote:
> I have compiled the Protocol Buffer library on OS X and I am using the 
> following CMake code to try and find the compiled libraries:
> 
> find_package(Protobuf REQUIRED)
> 
> 
> but when configuring I get the usual
> 
> CMake Error: The following variables are used in this project, but they are 
> set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake 
> files:
> PROTOBUF_LIBRARY (ADVANCED)
> 
> Looking at the FindProtobuf.cmake file that came with CMake 3.3.0 it looks 
> like the module would ONLY work with MSVC built Protobuf libraries as the 
> specific paths that are searched for are Visual Studio specific. Is this the 
> correct behavior? Does anyone else use Protobuffers on OS X? I am thinking of 
> rolling my on FindProtobuf.cmake file to have cmake look in more places.
> 
> ---
> Mike Jackson
> 
> --
> 
> 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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2768-gbb946e5

2015-09-04 Thread Rolf Eike Beer 
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, next has been updated
   via  bb946e544e4895670f946c252234c101c37443d0 (commit)
   via  ea080e3eb3f97679c959b8bf185e152e2d8f2db5 (commit)
   via  20f6007053f09e4c8ca9b8615f3c78ea726e2c3a (commit)
  from  8be433e2fbbab9a4b6634246d1b69c2d5fd27380 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb946e544e4895670f946c252234c101c37443d0
commit bb946e544e4895670f946c252234c101c37443d0
Merge: 8be433e ea080e3
Author: Rolf Eike Beer 
AuthorDate: Fri Sep 4 14:45:05 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Sep 4 14:45:05 2015 -0400

Merge topic 'wbpvf_no_deref' into next

ea080e3e write_basic_package_version_file: remove variable dereferences in 
templates
20f60070 CMake Nightly Date Stamp


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ea080e3eb3f97679c959b8bf185e152e2d8f2db5
commit ea080e3eb3f97679c959b8bf185e152e2d8f2db5
Author: Rolf Eike Beer 
AuthorDate: Fri Sep 4 20:40:08 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Fri Sep 4 20:44:24 2015 +0200

write_basic_package_version_file: remove variable dereferences in templates

Fixes some minor whitespace issues in the if()s.

diff --git a/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in 
b/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in
index b1c4fdf..bc78016 100644
--- a/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in
+++ b/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in
@@ -9,22 +9,22 @@
 
 set(PACKAGE_VERSION "@CVF_VERSION@")
 
-if("${PACKAGE_VERSION}" VERSION_LESS "${PACKAGE_FIND_VERSION}" )
+if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION)
   set(PACKAGE_VERSION_COMPATIBLE FALSE)
 else()
   set(PACKAGE_VERSION_COMPATIBLE TRUE)
-  if( "${PACKAGE_FIND_VERSION}" STREQUAL "${PACKAGE_VERSION}")
+  if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION)
 set(PACKAGE_VERSION_EXACT TRUE)
   endif()
 endif()
 
 # if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, 
ignore it:
-if("${CMAKE_SIZEOF_VOID_P}"  STREQUAL ""  OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL 
"")
+if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "")
return()
 endif()
 
 # check that the installed version has the same 32/64bit-ness as the one which 
is currently searching:
-if(NOT "${CMAKE_SIZEOF_VOID_P}"  STREQUAL  "@CMAKE_SIZEOF_VOID_P@")
+if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@")
math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8")
set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
set(PACKAGE_VERSION_UNSUITABLE TRUE)
diff --git a/Modules/BasicConfigVersion-ExactVersion.cmake.in 
b/Modules/BasicConfigVersion-ExactVersion.cmake.in
index 9fd0136..de4a23a 100644
--- a/Modules/BasicConfigVersion-ExactVersion.cmake.in
+++ b/Modules/BasicConfigVersion-ExactVersion.cmake.in
@@ -17,30 +17,30 @@ else()
   set(CVF_VERSION_NO_TWEAK "@CVF_VERSION@")
 endif()
 
-if("${PACKAGE_FIND_VERSION}" MATCHES "^([0-9]+\\.[0-9]+\\.[0-9]+)\\.") # strip 
the tweak version
+if(PACKAGE_FIND_VERSION MATCHES "^([0-9]+\\.[0-9]+\\.[0-9]+)\\.") # strip the 
tweak version
   set(REQUESTED_VERSION_NO_TWEAK "${CMAKE_MATCH_1}")
 else()
   set(REQUESTED_VERSION_NO_TWEAK "${PACKAGE_FIND_VERSION}")
 endif()
 
-if("${REQUESTED_VERSION_NO_TWEAK}" STREQUAL "${CVF_VERSION_NO_TWEAK}")
+if(REQUESTED_VERSION_NO_TWEAK STREQUAL CVF_VERSION_NO_TWEAK)
   set(PACKAGE_VERSION_COMPATIBLE TRUE)
 else()
   set(PACKAGE_VERSION_COMPATIBLE FALSE)
 endif()
 
-if( "${PACKAGE_FIND_VERSION}" STREQUAL "${PACKAGE_VERSION}")
+if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION)
   set(PACKAGE_VERSION_EXACT TRUE)
 endif()
 
 
 # if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, 
ignore it:
-if("${CMAKE_SIZEOF_VOID_P}"  STREQUAL ""  OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL 
"")
+if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "")
return()
 endif()
 
 # check that the installed version has the same 32/64bit-ness as the one which 
is currently searching:
-if(NOT "${CMAKE_SIZEOF_VOID_P}" STREQUAL "@CMAKE_SIZEOF_VOID_P@")
+if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@")
   math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8")
   set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
   set(PACKAGE_VERSION_UNSUITABLE TRUE)
diff --git a/Modules/BasicConfigVersion-SameMajorVersion.cmake.in 
b/Modules/BasicConfigVersion-SameMajorVersion.cmake.in
index 4acd9bb..a32245d 100644
--- a/Modules/BasicConfigVersion-SameMajorVersion.cmake.in
+++

[CMake] cmake uses -I instead -isystem when linking private against a library

2015-09-04 Thread Christian Ehrlicher 

Hi,

It looks like '-isystem' is replaced by '-i' from the compile line as 
soon as the library which defined the path as system include path is 
linked as 'PRIVATE'.

See this testcase:

project(isystem)
cmake_minimum_required(VERSION 3.0)

add_library(lib1 SHARED foo.cpp)
set_property(TARGET lib1 PROPERTY INTERFACE_INCLUDE_DIRECTORIES
${CMAKE_SOURCE_DIR}/include)
set_property(TARGET lib1 PROPERTY INTERFACE_SYSTEM_INCLUDE_DIRECTORIES 
${CMAKE_SOURCE_DIR}/include)


add_library(lib2 SHARED foo.cpp)
target_link_libraries(lib2
  PUBLIC
lib1
)
add_library(lib3 SHARED foo.cpp)
target_link_libraries(lib3
  PRIVATE
lib1
  PUBLIC
lib2
)
add_library(lib4 SHARED foo.cpp)
target_link_libraries(lib4
  PUBLIC
lib3
)

now lib4.cpp is compiled with -I ${CMAKE_SOURCE_DIR}/include ...

I'm not quite sure if the dependency chain is valid here and it can be 
easily fixed by moving lib1 from PRIVATE to PUBLIC in 
target_link_libraries(lib3) but since lib3 links public to lib2 and lib2 
public to lib1 I expected that lib4 should also use '-isystem'


Should I file a bug report on this?
Christian



--

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-developers] [PATCH] Don't generate erroneous outputs with -noproxy.

2015-09-04 Thread Ben Webb 
Generally for a module foo, SWIG generates (in Python mode)
an extension module _foo.so and a proxy Python module foo.py.
However, if -noproxy is specified, instead it builds only foo.so
(without the leading underscore). The custom command generated
by CMake correctly handles the removal of this underscore when
-noproxy is given; however, it still adds foo.py to the expected
outputs. This upsets build tools that expect foo.py to be generated
(for example, 'make' will run the SWIG command twice). Fix this
by removing foo.py from the set of extra generated files when
-noproxy is specified.
---
 Modules/UseSWIG.cmake | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/Modules/UseSWIG.cmake b/Modules/UseSWIG.cmake
index 96b0b35..d757f65 100644
--- a/Modules/UseSWIG.cmake
+++ b/Modules/UseSWIG.cmake
@@ -153,10 +153,12 @@ macro(SWIG_ADD_SOURCE_TO_MODULE name outfiles infile)
   else()
 set(swig_outdir ${CMAKE_CURRENT_BINARY_DIR})
   endif()
-  SWIG_GET_EXTRA_OUTPUT_FILES(${SWIG_MODULE_${name}_LANGUAGE}
-swig_extra_generated_files
-"${swig_outdir}"
-"${swig_source_file_fullname}")
+  if (NOT SWIG_MODULE_${name}_NOPROXY)
+SWIG_GET_EXTRA_OUTPUT_FILES(${SWIG_MODULE_${name}_LANGUAGE}
+  swig_extra_generated_files
+  "${swig_outdir}"
+  "${swig_source_file_fullname}")
+  endif()
   set(swig_generated_file_fullname
 "${swig_outdir}/${swig_source_file_name_we}")
   # add the language into the name of the file (i.e. TCL_wrap)
-- 
2.3.2 (Apple Git-55)

-- 

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] Idea: CMake IRC Bot

2015-09-04 Thread Gerhard Gappmeier 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi CMake Devs,

maybe this idea is not new or you even have something like that, so
please let me know.

Wouldn't it be cool to have an IRC bot for cmake which we could use to
control builds and get build notifications?

What I'm thinking of is this:
* for each project on CDash you can configure an IRC channel, by default
# or #-ci.
* you can trigger a build manually or periodically on a given branch.
  - build   []: one shot build if no inteval is
given, periodic otherwise
where type is: Continuous, Nightly, Experimental
  - list: lists all registered build configurations
  - remove : for removing a configured build config
* getting notifications posted in the project channel: FAILED (w=50)
, similar to emails
   a link for the CDash website can also be posted to view the results
in detail.

Of course many more commands would be possible.
The possibilities of using IRC are endless:
E.g. you could integrate a build-status script in TMUX statusbar to show
a nice icon for your project status.

I think the main things that are missing at the moment, except for the
obvious IRC code are:
* a communication channels between CDash and the build machines, so that
CDash can trigger the builds
  (I can remember a discussion that something like that was planned, but
I don't know the current status of this)
  Why not use also IRC commands between CDash (build-master) and the
build-slaves?
* a framework which does the initial cloning of configured projects,
checkout the right branch, submodule init/sync/update, and call cmake.
  This needs to be done before "make Continuous" works. We created some
BASH scripts for this in our company,
  but I feel this is something that needs a more generic solution and
almost everybody needs that.
  This should also be able to report some Git checkout errors, e.g. if a
Git submodule reference is invalid.

What do you think?

- -- 
mit freundlichen Grüßen / best regards

*Gerhard Gappmeier*
ascolab GmbH - automation systems communication laboratory
Tel.: +49 9131 691 123
Fax: +49 9131 691 128
Web: http://www.ascolab.com
GPG-KeyId: 5AAC50C4
GPG-Fingerprint: 967A 15F1 2788 164D CCA3 6C46 07CD 6F82 5AAC 50C4

- --
*ascolab GmbH*
Geschäftsführer: Gerhard Gappmeier, Matthias Damm, Uwe Steinkrauß
Sitz der Gesellschaft: Am Weichselgarten 7 • 91058 Erlangen • Germany
Registernummer: HRB 9360
Registergericht: Amtsgericht Fürth

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlXpTpgACgkQB81vglqsUMRDLgCfco6/hYYm/dYZYIoOBHN3asHr
sX8AmwdpCSk+sjrWd91n/h0+2tpqv3UY
=eYO/
-END PGP SIGNATURE-

-- 

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