[cmake-developers] [CMake 0016137]: ExternalProject_Add: Can't escape ; character in CMAKE_ARGS

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16137 
== 
Reported By:Andry81
Assigned To:
== 
Project:CMake
Issue ID:   16137
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-06-07 09:56 EDT
Last Modified:  2016-06-07 09:56 EDT
== 
Summary:ExternalProject_Add: Can't escape ; character in
CMAKE_ARGS
Description: 
Seems ExternalProject_Add became broken from some time ago. I could not figure
out when, but from version 3.5.2 (including 3.5.2-rc1) it does not work anymore.
All ";" characters does replace now by space whenever and not matter how you use
the expression.

Steps to Reproduce: 
ExternalProject_Add(MySubProject SOURCE_DIR ${SUBPROJECT_ROOT}
CMAKE_ARGS
-DMYPATH=c:/blabla1;c:/blabla1/blabla2;c:/blabla1/blabla3
INSTALL_COMMAND "" )

Additional Information: 
I Tried these to workaround it:
1. Quotes around the expression ("-DMYPATH=...")
2. Backlash escaping ("-DMYPATH=...\;...")
3. LIST APPEND instead SET
4. LIST_SEPARATOR in ExternalProject_Add
5. STRING REPLACE ^^ to ;

Nothing works.

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-06-07 09:56 Andry81New Issue
==

-- 

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] [CMake 0016136]: cmake --build can not build several targets

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16136 
== 
Reported By:Tobias Hunger
Assigned To:
== 
Project:CMake
Issue ID:   16136
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-06-06 08:29 EDT
Last Modified:  2016-06-06 08:29 EDT
== 
Summary:cmake --build can not build several targets
Description: 
I am using cmake --build in Qt Creator now and got feedback that all but the
last target passed to cmake --build . --target a --target b are ignored.

It would be really convenient to be able to build more than one target in one go
using cmake --build.

Steps to Reproduce: 
1) Generate any cmake project with two targets defined called A and B.
2) try to build both targets at once using cmake --build . --target A --target B
3) Watch as only target B is built.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-06-06 08:29 Tobias Hunger  New Issue
==

-- 

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] [CMake 0016135]: RPATH linker flags no longer set correctly for SunOS PathScale compiler since cmake 3.1

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16135 
== 
Reported By:Michał Górny
Assigned To:
== 
Project:CMake
Issue ID:   16135
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-06-03 12:47 EDT
Last Modified:  2016-06-03 12:47 EDT
== 
Summary:RPATH linker flags no longer set correctly for SunOS
PathScale compiler since cmake 3.1
Description: 
We've recently upgraded CMake and noticed that our project stopped building
correctly. After timesome debugging, I've found out that after CMake upgrade,
CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG is no longer set correctly. This happens on
SunOS-5 system with PathScale compiler in use, and it started to happen in
cmake-3.1.

It looks that the correct linker flags are being set in two modules:
Platform/SunOS.cmake and Platform/SunOS-GNU.cmake.

The former of the files does not apply the linker flags since it is restricted
to apply to SunOS-4 only.

The latter of the files used to apply before cmake-3.1. However, since cmake-3.1
it is no longer used when PathScale compiler is in use.

Steps to Reproduce: 
1. Download PathScale compiler
(http://www.pathscale.com/ekopath-compiler-suite),

2. echo 'message(FATAL_ERROR "${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG}")' >
CMakeLists.txt

3. cmake . -DCMAKE_C_COMPILER=/opt/ekopath/bin/pathcc

With cmake-3.0.2 and older, it will print: -Wl,-R

With cmake-3.1.3 and newer, it will print an empty string

Additional Information: 
This probably could be fixed two ways: either by applying the 'GNU' rules for
PathScale compiler, or by extending the SunOS rules to SunOS-5. I don't know
which one is more correct here.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-06-03 12:47 Michał Górny   New Issue
==

-- 

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] [CMake 0016134]: CMake crashes at generation stage

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16134 
== 
Reported By:Daniel Levin
Assigned To:
== 
Project:CMake
Issue ID:   16134
Category:   CMake
Reproducibility:always
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-06-01 23:58 EDT
Last Modified:  2016-06-01 23:58 EDT
== 
Summary:CMake crashes at generation stage
Description: 
Reproducibility 100% on my personal project using either Makefile or Ninja
generator. Affected all CMake version after 3.4, earlier versions might contains
this issue as well, did not check. Provided fixup patch is for CMake 3.4.0.
Versions 3.5+ have different implementation of the same code, but bug is still
there. Please see attached Git bundle with branch 'bug' inside that contains the
fix.

Copy of the patch message:

cmGeneratorTarget: Fix tracing dependencies in local generator

When looping over the generator targets they might become indirectly
invalidated and recreated from cmGlobalGenerator::CreateGenerationObjects().
Thus targets container cmGeneratorTarget pointers will be deleted,
dereferencing them leads to crashes at generation stage.

To avoid this loop should iterate over cmTarget keys and look for
cmGeneratorTarget pointers directly from Makefile instance each time.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-06-01 23:58 Daniel Levin   New Issue
2016-06-01 23:58 Daniel Levin   File Added: crash.bundle 
==

-- 

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] [CMake 0016133]: NO_DEFAULT_PATH is taken as a path when specified after the PATHS option.

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16133 
== 
Reported By:Alexis Wilke
Assigned To:
== 
Project:CMake
Issue ID:   16133
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-31 20:27 EDT
Last Modified:  2016-05-31 20:27 EDT
== 
Summary:NO_DEFAULT_PATH is taken as a path when specified
after the PATHS option.
Description: 
I wanted to make sure that I could get a header from my environment (i.e. source
tree) first, then from the system if no specific version in the environment was
defined there. For this purpose, I used the NO_DEFAULT_PATH option as defined in
the documentation:

https://cmake.org/cmake/help/v3.5/command/find_path.html

However, the code would always return path "/usr/include" when I expect (in my
specific case) to see path "...path-to-source.../contrib/catch"

I found that by putting the NO_DEFAULT_PATH before the PATHS option, it worked
as I first expected. It seems to me, though, that it is not correct. There
should be a check and if a path defined after the PATHS option looks like a
flag, it should be taken as such and see it as the end of the list of PATHS or
HINTS.

Steps to Reproduce: 
The failing search looks like this:

FIND_PATH(CATCH_INCLUDE_DIR
catch.hpp
PATHS
${CMAKE_SOURCE_DIR}/contrib/catch 
${CMAKE_SOURCE_DIR}/contrib
NO_DEFAULT_PATH
)

IF(NOT CATCH_INCLUDE_DIR)
# Try again with default paths as per cmake
FIND_PATH(CATCH_INCLUDE_DIR
catch.hpp
)
ENDIF()


My Ubuntu installation includes a catch.hpp under /usr/include. This is because
I have the catch package already installed:

apt-get install catch

My source directory includes a contrib/catch/catch.hpp file.

Adding a MESSAGE("Found Path? ")(${CATCH_INCLUDE_DIR}) before the IF() shows us
that the CATCH_INCLUDE_DIR is already set and it is "/usr/include" instead of
the expected "${CMAKE_SOURCE_DIR}/contrib/catch".



Additional Information: 
There is a work around, which makes me think that the problem is that PATHS (and
probably HINTS) does not properly recognize NO_DEFAULT_PATH as a flag and no see
it as a path...

All I have to do is to put the NO_DEFAULT_PATH ahead of the PATHS specification.

FIND_PATH(CATCH_INCLUDE_DIR
catch.hpp
NO_DEFAULT_PATH
PATHS
${CMAKE_SOURCE_DIR}/contrib/catch 
${CMAKE_SOURCE_DIR}/contrib
)

See also my Stackoverflow.com entry here:

http://stackoverflow.com/questions/37534142/how-do-i-get-cmake-to-choose-the-header-found-in-my-contrib-directory/37534160#37534160
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-31 20:27 Alexis Wilke   New Issue
==

-- 

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] [CMake 0016132]: Repeated lines in NSIS.template.in

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16132 
== 
Reported By:Craig Scott
Assigned To:
== 
Project:CMake
Issue ID:   16132
Category:   CMake
Reproducibility:N/A
Severity:   trivial
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-30 11:14 AEST
Last Modified:  2016-05-30 11:14 AEST
== 
Summary:Repeated lines in NSIS.template.in
Description: 
At around line 160 of NSIS.template.in, the block of code below appears to
repeat the same thing (probably the result of a bad merge at some point). Seems
like one of the two blocks should be removed?


;
; path functions

!verbose 3
!include "WinMessages.NSH"
!verbose 4

;
; based upon a script of "Written by KiCHiK 2003-01-18 05:57:02"
;
!verbose 3
!include "WinMessages.NSH"
!verbose 4
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-30 11:14 Craig ScottNew Issue
==

-- 

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] [CMake 0016131]: INTERNET EXPLORER +1800-385-4895 I Internet Explorer tech support phone number USA/Canada I remotely help by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16131 
== 
Reported By:websupport
Assigned To:
== 
Project:CMake
Issue ID:   16131
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:54 EDT
Last Modified:  2016-05-27 15:54 EDT
== 
Summary:INTERNET EXPLORER +1800-385-4895 I Internet Explorer
tech support phone number USA/Canada I remotely help by third party
Description: 
Technical Support For Internet Explorer Page Issue : 1800-385-4895
Internet Explorer +1800-385-4895 Customer Support  Number,  Internet Explorer
Technical Helpline Number  USA, Internet Explorer support phone number united
states +1800-385-4895
Internet Explorer +1800-385-4895 Customer Support ,  Internet Explorer technical
Support phone number USA, Internet Explorer support phone number united states
+1800-385-4895
Internet Explorer +1800-385-4895 Customer Support  Number Internet Explorer
technical Support phone number USA, Internet Explorer support phone number
united states +1800-385-4895
+1800-385-4895@@@ Internet Explorer tech support number , .Internet Explorer
technical support phone number
Internet Explorer Toll Free - 1800-385-4895 Internet Explorer Technical Support
Number, Internet Explorer help desk phone number  
Just Call, +1800-385-4895 for all type help related Internet Explorer Page Issue
support telephone number,Internet Explorer support phone number,Internet
Explorer support phone number,Internet Explorer help phone number, Internet
Explorer technical support number.Internet Explorer support number, Internet
Explorer phone number, Internet Explorer tech support number, Internet Explorer
customer support number, Internet Explorer customer support phone number,
Internet Explorer customer service phone number, Internet Explorer  customer
service phone number, Internet Explorer support phone number
Internet Explorer help number-Internet Explorer Helpline Number; Internet
Explorer help phone number-Internet Explorer Helpline Number, Internet Explorer
Tech Support Toll free Number, Internet Explorer Support Telephone Number,
Internet Explorer Tech Support Telephone number, Internet Explorer Tech Support
contact number, Internet Explorer support contact number, Internet Explorer
technical support contact number, Internet Explorer help desk phone
number.Internet Explorer password recovery support phone number.
Just Call-1800-385-4895-: Internet Explorer password recovery support phone
number.
Internet Explorer technical support, Internet Explorer Customer Service Phone
Number, Internet Explorer Customer Service Number, Internet Explorer Customer
Support Phone Number, Internet Explorer Customer Support Number, Internet
Explorer Customer Service Helpline Number, Internet Explorer Customer Care
Number, Internet Explorer support team phone number. Internet Explorer password
recovery support phone number.
Call,@(+1800-385-4895)@-: Internet Explorer help number-Internet Explorer
Helpline Number; Internet Explorer help phone number, Internet Explorer Helpline
Number, Internet Explorer Tech Support Toll free Number, Internet Explorer
Support Telephone Number, Internet Explorer Tech Support Telephone number,
Internet Explorer Tech Support contact number, Internet Explorer support contact
number, Internet Explorer technical support contact number, Internet Explorer
support phone number, Internet Explorer  support phone number. Internet Explorer
customer support phone number.. Internet Explorer password reset support phone
number.
Internet Explorer +1800-385-4895 Customer Support  Number Internet Explorer
technical Support phone number USA, Internet Explorer support phone number
united states +1800-385-4895
+1800-385-4895@@@ Internet Explorer tech support number , .Internet Explorer
technical support phone number
Internet Explorer Toll Free - 1800-385-4895 Internet Explorer Technical Support
Number, Internet Explorer help desk phone number  
Just Call, +1800-385-4895 for all type help related Internet Explorer Page Issue
support telephone number,Internet Explorer support phone number,Internet
Explorer support phone number,Internet Explorer help phone number, Internet
Explorer technical support number.Internet Explorer support number, Internet
Explorer phone number, Internet Explorer page tech support number, Internet
Explorer customer support number, Internet Explorer customer support phone
number, Internet 

[cmake-developers] [CMake 0016130]: OUTLOOK MAIL +1800-385-4895 I OUTLOOK tech support phone number USA/Canada I remotely help by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16130 
== 
Reported By:websupport
Assigned To:
== 
Project:CMake
Issue ID:   16130
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:51 EDT
Last Modified:  2016-05-27 15:51 EDT
== 
Summary:OUTLOOK MAIL +1800-385-4895 I OUTLOOK tech support
phone number USA/Canada I remotely help by third party
Description: 
Just Call +1800-385-4895 Outlook tech support number Outlook customer service
number USA CANADA here. Call Us +1800-385-4895 Outlook tech support number
Outlook customer service number USA CANADA+1800-385-4895 Outlook support number,
Outlook customer phone number helpline number, Outlook TECH SUPPORT PHONE NUMBER
Outlook CUSTOMER SERVICE PHONE NUMBER here.+1800-385-4895 Outlook TECH SUPPORT
PHONE NUMBER %Outlook CUSTOMER SERVICE PHONE NUMBER Outlook technical support
number Outlook helpdesk number Outlook helpdesk phone number Outlook Helpline
number, Outlook Phone number USA CANADA (((+1800-385-4895 ))).Outlook phone
number===Outlook tech support PHONE NUMBER Helpline toll free
===!!===+1800-385-4895 == Outlook tech support phone number ==!! Outlook
install TECH SUPPORT PHONE NUMBER USA CANADA+1800-385-4895 Outlook TECH SUPPORT
PHONE NUMBER %Outlook CUSTOMER SERVICE PHONE NUMBER ===!!! Outlook customer
service phone number!!! Outlook phone number Outlook telephone
number+1800-385-4895 ==Outlook PHONE NUMBER!!!TECH SUPPORT phone number ++
Outlook TOLL FREE PHONE NUMBER Phone Number +1800-385-4895 USA CANADA, Outlook
Support Phone Number, Outlook technical Support Phone Number here. toll free
Outlook Phone Number +1800-385-4895 USA CANADA, Outlook Support Phone Number,
Outlook technical Support Phone Number here.toll free Outlook Phone Number
+1800-385- Outlook technical Support Phone Number toll free Outlook Phone Number
+1800-385-4895 USA CANADA, Outlook Support Phone Number, Outlook technical
Support Phone Number, Outlook Customer Support Number?? This article is in need
of a technical review. This article is in need of an editorial review. Outlook
Phone Number +1800-385-4895 USA CANADA, Outlook Support Phone Number, Outlook
technical Support Phone Number, Outlook Customer Support Number?? Outlook
Support Phone Number +1800-385-4895 USA CANADA, Outlook Phone Number, Outlook
Technical Support Phone Number, Outlook Service Support Number Outlook Support
Phone Number +1800-385-4895 USA CANADA, Outlook Phone Number, Outlook Technical
Support Phone Number, Outlook Service Support Number?? Outlook Phone Number
+1800-385-4895 USA CANADA, Outlook Support Phone Number, Outlook technical
Support Phone Number, Outlook Customer Support Number?? Outlook Support Phone
Number +1800-385-4895 USA CANADA, Outlook Support Phone Number, Outlook
technical Support Phone Number, Outlook Customer Support Number?? Outlook phone
number #$#+1800-385-4895 ##$Outlook phone number Outlook security phone number
Outlook phone number #$#+1800-385-4895 ##$Outlook support phone number Outlook
phone number Outlook phone number customer service #$#+1800-385-4895 ##$Outlook
customer service phone number Outlook tech support phone number Outlook
technical support phone number Outlook phone numbers Outlook technical phone
number Outlook support phone number #$#+1800-385-4895 ##$Outlook phone support
Outlook technical phone number Outlook internet security phone number Outlook
support phone number Outlook phone AVG809 phone number phone number for Outlook
phone numbers Outlook customer service phone number Outlook customer support
phone number find a phone number Outlook CANADA phone number USA CANADA phone
number phone number for Outlook tech support phone number Outlook phone support
free phone numbers phone number Outlook phone number get human find phone number
phone number for Outlook security us phone number phone number USA CANADA
#$#+1800-385-4895 ##$Outlook contact phone number Outlook phone number for
support Outlook technical number phone number for Outlook USA CANADA phone
numbers phone number search us phone numbers find phone numbers Norton number
AVG809 number Outlook downloads Outlook free trial Outlook internet security 202
Outlook cancellation phone number Outlook updates phone b00k phone numbers in
USA CANADA telephone number Outlook helpline number phone directory contact
Outlook by phone Outlook subscription Outlook ghost download Outlook 

[cmake-developers] [CMake 0016129]: NORTON Antivirus +1800-385-4895 I NORTON antivirus helpdesk phone number USA/Canada I remotely help by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16129 
== 
Reported By:websupport
Assigned To:
== 
Project:CMake
Issue ID:   16129
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:45 EDT
Last Modified:  2016-05-27 15:45 EDT
== 
Summary:NORTON Antivirus +1800-385-4895 I NORTON antivirus
helpdesk phone number USA/Canada I remotely help by third party
Description: 
Call  +1800 385 4895 NORTON antivirus customer support number 
NORTON internet security phone number +1800 385 4895 
NORTON antivirus +1-800-385-4895 tech support phone number
 NORTON antivirus help +1800 385 4895 USA technical support phone number
Just Call +1800 385 4895 NORTON Antivirus customer Support Telephone Number
+1800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 800 385 4895 NORTON Antivirus customer Support
Telephone Number, NORTON technical support phone number 800 385 4895 NORTON
Antivirus customer Support Telephone Number, NORTON technical support phone
number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number +1800 385 4895 @ NORTON Antivirus customer
Support Telephone Number, NORTON technical support phone number 
+1800 385 4895 @NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
•   +1800 385 4895 NORTON Antivirus customer Support Telephone Number, 
NORTON
technical support phone number 
Dial +1800 385 4895 NORTON antivirus contact number, NORTON internet security
antivirus tech support phone number, NORTON internet security Dial +1800 385
4895 NORTON antivirus contact number, NORTON internet security antivirus tech
support phone number, NORTON internet security 
Dial +1800 385 4895 NORTON antivirus contact number, NORTON internet security
antivirus tech support phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
securityantivirus tech support phone number, NORTON internet security Dial +1800
385 4895 NORTON antivirus contact number, NORTON internet securityantivirus tech
support phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
security antivirus tech support phone number, NORTON internet security Now call
NORTON antivirus contact number, NORTON internet securityantivirus tech support
phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
securityantivirus tech support phone number, NORTON internet security 
•   +1800 385 4895 NORTON antivirus technical support number NORTON 
technical support phone number usa +1800 385 4895 NORTON antivirus technical
support number NORTON 
technical support phone number usa +1800 385 4895 NORTON technical 
support NORTON technical support number NORTON antivirus technical 
support number NORTON technical support phone number +1800 385 4895 
NORTON technical support NORTON technical support number NORTON 
antivirus technical support number NORTON technical support phone number 
•   +1800 385 4895 NORTON technical support NORTON technical support 
number NORTON antivirus technical support number NORTON technical 
support phone number NORTON technical support phone number usa NORTON 
antivirus technical support phone number NOW**/FIRST Tech CALL. 
NORTON antivirus customer support phone numberDial +1800 385 4895 
Dial +1800 385 4895 NORTON antivirus customer support phone number. 
NORTON antivirus phone number .NORTON antivirus support phone numbers 
FIRST Dial +1800 385 4895 NORTON antivirus customer support phone 
number. NORTON antivirus phone number .NORTON antivirus support phone 
numbers FIRST Dial +1800 385 4895 NORTON antivirus customer support 
phone number. NORTON antivirus phone number .NORTON antivirus support 

[cmake-developers] [CMake 0016128]: Get Fix AVG Antivirus +1800-385-4895 I AVG antivirus helpdesk phone number USA/Canada I remotely help by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16128 
== 
Reported By:websupport
Assigned To:
== 
Project:CMake
Issue ID:   16128
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:38 EDT
Last Modified:  2016-05-27 15:38 EDT
== 
Summary:Get Fix AVG Antivirus +1800-385-4895  I AVG
antivirus helpdesk phone number USA/Canada  I remotely help by third party
Description: 
avg antivirus not working. Dial 1800 385 4895 and get fix remotely by online
tech support
avg antivirus  antivirus tech support number 1800 385 4895  avg antivirus  tech
support number avg antivirus  internet security customer service phone number
1800 385 4895  avg antivirus   phone number usa
avg antivirus  antivirus tech support number 1800 385 4895  avg antivirus  tech
support number avg antivirus  internet security customer service phone number
1800 385 4895  avg antivirus   phone number usa
avg antivirus  internet security customer service phone number 1800 385 4895 
avg antivirus   phone number avg antivirus  Toll Free, 1800 385 4895  avg
antivirus  Tech Support Phone Number  online solution for all usa/canada 
clients. For any help of query call 1800 385 4895  to get all avg antivirus 
account solution. Call, 1800 385 4895  for all type help by avg antivirus  tech
support phone number, Intuit avg antivirus  Tech Support Phone Number, avg
antivirus  Help Desk Phone Number, avg antivirus  tech support number, avg
antivirus  technical support phone number, avg antivirus  phone number, avg
antivirus  technical support number, avg antivirus  support phone number, avg
antivirus  technical support, avg antivirus  Customer Service Phone Number, avg
antivirus  Customer Service Number, avg antivirus  Customer Support Phone
Number, avg antivirus  Customer Support Number,avg antivirus  Customer Service
Helpline Number, avg antivirus  Customer Care Number, avg antivirus  support
team phone number, avg antivirus  help number-avg antivirus  Helpline Number;
avg antivirus  help phone number-avg antivirus  Helpline Number, avg antivirus 
Tech Support Toll free Number, avg antivirus  Support Telephone Number, avg
antivirus  Tech Support Telephone number, avg antivirus  Tech Support contact
number, avg antivirus  support contact number, avg antivirus  technical support
contact number. Call, avg antivirus  tech support phone number, Intuit avg
antivirus  Tech Support Phone Number, avg antivirus  Help Desk Phone Number, avg
antivirus  tech support number, avg antivirus  technical support phone number,
avg antivirus  phone number, avg antivirus  technical support number, avg
antivirus  support phone number. It is very popular toll free number which  by
online technical support, avg antivirus  Customer Service Phone Number, avg
antivirus  Customer Service Number, avg antivirus  Customer Support Phone
Number, avg antivirus  Customer Support Number, avg antivirus  Customer Service
Helpline Number, avg antivirus  Customer Care Number, avg antivirus  support
team phone number. Call, avg antivirus  tech support phone number, Intuit avg
antivirus  Tech Support Phone Number, avg antivirus  Help Desk Phone Number, avg
antivirus  tech support number, avg antivirus  technical support phone number,
avg antivirus  phone number, avg antivirus  technical support number, avg
antivirus  support phone number, avg antivirus  technical support, avg antivirus
 Customer Service Phone Number, avg antivirus  Customer Service Number, avg
antivirus  Customer Support Phone Number, avg antivirus  Customer Support
Number, avg antivirus  Customer Service Helpline Number, avg antivirus  Customer
Care Number, avg antivirus  support team phone number, avg antivirus  help
number-avg antivirus  Helpline Number; avg antivirus  help phone number, avg
antivirus  Helpline Number, avg antivirus  Tech Support Toll free Number, avg
antivirus  Support Telephone Number, avg antivirus  Tech Support Telephone
number, avg antivirus  Tech Support contact number, avg antivirus  support
contact number, avg antivirus  technical support contact number, avg antivirus  
support phone number, avg antivirus  antivirus support phone number. avg
antivirus  antivirus customer support phone number avg antivirus  technical help
telephone number, avg antivirus  technical help contact number, avg antivirus 
technical support contact number, avg antivirus  contact number, avg antivirus 

[cmake-developers] [CMake 0016127]: CALL 1-800-253-0759 MS Office helpdesk phone number USA/Canada, call and get fix outlook mail issue remotely by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16127 
== 
Reported By:nellam
Assigned To:
== 
Project:CMake
Issue ID:   16127
Category:   CMake
Reproducibility:have not tried
Severity:   minor
Priority:   high
Status: new
== 
Date Submitted: 2016-05-27 15:13 EDT
Last Modified:  2016-05-27 15:13 EDT
== 
Summary:CALL 1-800-253-0759 MS Office helpdesk phone number
USA/Canada, call and get fix outlook mail issue remotely by third party
Description: 

ms office phone number,((1-8.00-253-0759))// ms
officehttps://wiki.qt.io/Q.u.i.c.k.b.o.o.k.s_P.R.O_T.e.c.h_s.u.p.p.o.r.t_N.u.m.b.e.r_Q.u.i.c.k.b.o.o.k.s__t.e.c.h_s.u.p.p.o.r.t_p.h.o.n.e_N.u.m.b.e.r
care number. ms office Toll Free, Intuit@(1-8.00.253-0759)@-: ms office
Technical s upport Number, ms office help desk phone number vides online
solution for all USA/CANADA clients. For any help of query call 1 8.00 253 0759
to get all ms office account solution. For any help of query call 1 8.00 253
0759 to get all ms office account solution. @@Call, (1-8.00-253-0759) for all
type help by ms office s upport number,ms office s upport number,ms office s
upport number,ms office help phone number, ms office technical s upport
number.ms office s upport number, ms office phone number, ms office tech s
upport number, ms office customer s upport number, ms office customer s upport
number, ms office customer service phone number, ms office payroll customer
service phone number, ms office s upport number ms office help number-ms office
Helpline Number; ms office help phone number-ms office Helpline Number, ms
office Tech s upport Toll free Number, ms office s upport number, ms office Tech
s upport number, ms office Tech s upport contact number, ms office s upport
contact number, ms office technical s upport contact number, ms office help desk
phone number. Call, @((1-8.00-253-0759))@-: It is very popular toll free number
which vide by ms office technical s upport, ms office Customer Service Phone
Number, ms office Customer Service Number, ms office Customer s upport number,
ms office Customer s upport Number, ms office Customer Service Helpline Number,
ms office Customer Care Number, ms office s upport team phone number.
Call,@((1-8.00-253-0759))@-: ms office help number-ms office Helpline Number; ms
office help phone number, ms office Helpline Number, ms office Tech s upport
Toll free Number, ms office s upport number, ms office Tech s upport number, ms
office Tech s upport contact number, ms office s upport contact number, ms
office technical s upport contact number, ms office  s upport number, ms office
payroll s upport number. ms office payroll customer s upport number for all type
help by ms office s upport number, ms office help phone number, ms office
technical s upport number.ms office s upport number, ms office phone number, ms
office tech s upport number, ms office customer s upport number, ms office
customer s upport number, ms office customer service phone number, ms office
payroll customer service phone number Intuit@((1-8.00-253-0759))ms officeTech s
upport number vides online solution for all USA/CANADA clients. For any help of
query call 1 8.00 253 0759 to get all ms officeaccount solution. @@Call,
(1-8.00-253-0759) for all type help by ms officetech s upport number, Intuit ms
officeTech s upport number, ms officeHelp Desk Phone Number, ms officetech s
upport number, ms officetechnical s upport number,@@@ ms officephone number, ms
officetechnical s upport number, ms offices upport number, ms officetechnical s
upport, ms officeCustomer Service Phone Number, ms officeCustomer Service
Number, ms officeCustomer s upport number, ms officeCustomer s upport
Number, ms officeCustomer Service Helpline Number, ms officeCustomer Care
Number, ms offices upport team phone number, @ ms officehelp number-ms
officeHelpline Number;
https://wiki.qt.io/Q.u.i.c.k.b.o.o.k.s_P.R.O_T.e.c.h_s.u.p.p.o.r.t_N.u.m.b.e.r_Q.u.i.c.k.b.o.o.k.s__t.e.c.h_s.u.p.p.o.r.t_p.h.o.n.e_N.u.m.b.e.r
phone number-ms officeHelpline Number, ms officeTech s upport Toll free Number,
ms offices upport number, ms officeTech s upport number, ms officeTech s upport
contact number, ms offices upport contact number, ms officetechnical s upport
contact number. Call, ms officetech s upport number, Intuit ms officeTech s
upport number, ms officeHelp Desk Phone Number, ms officetech s upport number,
ms officetechnical s upport number, ms officephone 

[cmake-developers] [CMake 0016126]: DIAL 1-800-385-4895 AVG Antivirus helpdesk phone number USA/Canada, call and get fix remotely by third party J

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16126 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16126
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:07 EDT
Last Modified:  2016-05-27 15:07 EDT
== 
Summary:DIAL 1-800-385-4895 AVG Antivirus helpdesk phone
number USA/Canada, call and get fix remotely by third party J
Description: 
Call  +1800 385 4895 AVG antivirus customer support number 
AVG internet security phone number +1800 385 4895 
AVG antivirus +1-800-385-4895 tech support phone number
 AVG antivirus help +1800 385 4895 USA technical support phone number
Just Call +1800 385 4895 AVG Antivirus customer Support Telephone Number +1800
385 4895 AVG Antivirus customer Support Telephone Number, AVG technical support
phone number 800 385 4895 AVG Antivirus customer Support Telephone Number, AVG
technical support phone number 800 385 4895 AVG Antivirus customer Support
Telephone Number, AVG technical support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number +1800 385 4895 @ AVG Antivirus customer Support Telephone
Number, AVG technical support phone number 
+1800 385 4895 @AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
•   +1800 385 4895 AVG Antivirus customer Support Telephone Number, AVG
technical support phone number 
Dial +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security Dial +1800 385 4895
AVG antivirus contact number, AVG internet security antivirus tech support phone
number, AVG internet security 
Dial +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet
securityantivirus tech support phone number, AVG internet security Dial +1800
385 4895 AVG antivirus contact number, AVG internet securityantivirus tech
support phone number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security Now call AVG
antivirus contact number, AVG internet securityantivirus tech support phone
number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet
securityantivirus tech support phone number, AVG internet security 
•   +1800 385 4895 AVG antivirus technical support number AVG 
technical support phone number usa +1800 385 4895 AVG antivirus technical
support number AVG 
technical support phone number usa +1800 385 4895 AVG technical 
support AVG technical support number AVG antivirus technical 
support number AVG technical support phone number +1800 385 4895 
AVG technical support AVG technical support number AVG 
antivirus technical support number AVG technical support phone number 
•   +1800 385 4895 AVG technical support AVG technical support 
number AVG antivirus technical support number AVG technical 
support phone number AVG technical support phone number usa AVG 
antivirus technical support phone number NOW**/FIRST Tech CALL. 
AVG antivirus customer support phone numberDial +1800 385 4895 
Dial +1800 385 4895 AVG antivirus customer support phone number. 
AVG antivirus phone number .AVG antivirus support phone numbers 
FIRST Dial +1800 385 4895 AVG antivirus customer support phone 
number. AVG antivirus phone number .AVG antivirus support phone 
numbers FIRST Dial +1800 385 4895 AVG antivirus customer support 
phone number. AVG antivirus phone number .AVG antivirus support 
phone number Dial +1800 385 4895 AVG antivirus customer support 
phone number. AVG antivirus phone number .AVG antivirus support 
phone number +1800 385 4895 AVG antivirus support phone 
number, AVG antivirus phone number .AVG antivirus support phone 

[cmake-developers] [CMake 0016124]: DIAL ~1-800-385-4895 AVG Antivirus helpdesk phone number USA/Canada, call and get fix remotely by third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16124 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16124
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 15:04 EDT
Last Modified:  2016-05-27 15:04 EDT
== 
Summary:DIAL
https://cmake.org/Bug/view.php?id=41#c1-800-385-4895 AVG Antivirus helpdesk
phone number USA/Canada, call and get fix remotely by third party
Description: 
Call  +1800 385 4895 AVG antivirus customer support number 
AVG internet security phone number +1800 385 4895 
AVG antivirus +1-800-385-4895 tech support phone number
 AVG antivirus help +1800 385 4895 USA technical support phone number
Just Call +1800 385 4895 AVG Antivirus customer Support Telephone Number +1800
385 4895 AVG Antivirus customer Support Telephone Number, AVG technical support
phone number 800 385 4895 AVG Antivirus customer Support Telephone Number, AVG
technical support phone number 800 385 4895 AVG Antivirus customer Support
Telephone Number, AVG technical support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
800 385 4895 AVG Antivirus customer Support Telephone Number, AVG technical
support phone number +1800 385 4895 @ AVG Antivirus customer Support Telephone
Number, AVG technical support phone number 
+1800 385 4895 @AVG Antivirus customer Support Telephone Number, AVG technical
support phone number 
•   +1800 385 4895 AVG Antivirus customer Support Telephone Number, AVG
technical support phone number 
Dial +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security Dial +1800 385 4895
AVG antivirus contact number, AVG internet security antivirus tech support phone
number, AVG internet security 
Dial +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet
securityantivirus tech support phone number, AVG internet security Dial +1800
385 4895 AVG antivirus contact number, AVG internet securityantivirus tech
support phone number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet security
antivirus tech support phone number, AVG internet security Now call AVG
antivirus contact number, AVG internet securityantivirus tech support phone
number, AVG internet security 
Now call +1800 385 4895 AVG antivirus contact number, AVG internet
securityantivirus tech support phone number, AVG internet security 
•   +1800 385 4895 AVG antivirus technical support number AVG 
technical support phone number usa +1800 385 4895 AVG antivirus technical
support number AVG 
technical support phone number usa +1800 385 4895 AVG technical 
support AVG technical support number AVG antivirus technical 
support number AVG technical support phone number +1800 385 4895 
AVG technical support AVG technical support number AVG 
antivirus technical support number AVG technical support phone number 
•   +1800 385 4895 AVG technical support AVG technical support 
number AVG antivirus technical support number AVG technical 
support phone number AVG technical support phone number usa AVG 
antivirus technical support phone number NOW**/FIRST Tech CALL. 
AVG antivirus customer support phone numberDial +1800 385 4895 
Dial +1800 385 4895 AVG antivirus customer support phone number. 
AVG antivirus phone number .AVG antivirus support phone numbers 
FIRST Dial +1800 385 4895 AVG antivirus customer support phone 
number. AVG antivirus phone number .AVG antivirus support phone 
numbers FIRST Dial +1800 385 4895 AVG antivirus customer support 
phone number. AVG antivirus phone number .AVG antivirus support 
phone number Dial +1800 385 4895 AVG antivirus customer support 
phone number. AVG antivirus phone number .AVG antivirus support 
phone number +1800 385 4895 AVG antivirus support phone 
number, AVG antivirus phone 

[cmake-developers] [CMake 0016122]: DIAL 1-800-385-4895 NORTON Antivirus helpdesk phone number USA/Canada, call and get fix remotely by third party J

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16122 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16122
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 14:57 EDT
Last Modified:  2016-05-27 14:57 EDT
== 
Summary:DIAL 1-800-385-4895 NORTON Antivirus helpdesk phone
number USA/Canada, call and get fix remotely by third party J
Description: 
Call  +1800 385 4895 norton antivirus customer support number 
norton internet security phone number +1800 385 4895 
norton antivirus +1-800-385-4895 tech support phone number
 norton antivirus help +1800 385 4895 USA technical support phone number
Just Call +1800 385 4895 Norton Antivirus customer Support Telephone Number
+1800 385 4895 Norton Antivirus customer Support Telephone Number, NORTON
technical support phone number 800 385 4895 NORTON Antivirus customer Support
Telephone Number, NORTON technical support phone number 800 385 4895 NORTON
Antivirus customer Support Telephone Number, NORTON technical support phone
number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
800 385 4895 NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number +1800 385 4895 @ NORTON Antivirus customer
Support Telephone Number, NORTON technical support phone number 
+1800 385 4895 @NORTON Antivirus customer Support Telephone Number, NORTON
technical support phone number 
•   +1800 385 4895 NORTON Antivirus customer Support Telephone Number, 
NORTON
technical support phone number 
Dial +1800 385 4895 NORTON antivirus contact number, NORTON internet security
antivirus tech support phone number, NORTON internet security Dial +1800 385
4895 NORTON antivirus contact number, NORTON internet security antivirus tech
support phone number, NORTON internet security 
Dial +1800 385 4895 NORTON antivirus contact number, NORTON internet security
antivirus tech support phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
securityantivirus tech support phone number, NORTON internet security Dial +1800
385 4895 NORTON antivirus contact number, NORTON internet securityantivirus tech
support phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
security antivirus tech support phone number, NORTON internet security Now call
NORTON antivirus contact number, NORTON internet securityantivirus tech support
phone number, NORTON internet security 
Now call +1800 385 4895 NORTON antivirus contact number, NORTON internet
securityantivirus tech support phone number, NORTON internet security 
•   +1800 385 4895 NORTON antivirus technical support number NORTON 
technical support phone number usa +1800 385 4895 NORTON antivirus technical
support number NORTON 
technical support phone number usa +1800 385 4895 NORTON technical 
support NORTON technical support number NORTON antivirus technical 
support number NORTON technical support phone number +1800 385 4895 
NORTON technical support NORTON technical support number NORTON 
antivirus technical support number NORTON technical support phone number 
•   +1800 385 4895 NORTON technical support NORTON technical support 
number NORTON antivirus technical support number NORTON technical 
support phone number NORTON technical support phone number usa NORTON 
antivirus technical support phone number NOW**/FIRST Tech CALL. 
NORTON antivirus customer support phone numberDial +1800 385 4895 
Dial +1800 385 4895 NORTON antivirus customer support phone number. 
NORTON antivirus phone number .NORTON antivirus support phone numbers 
FIRST Dial +1800 385 4895 NORTON antivirus customer support phone 
number. NORTON antivirus phone number .NORTON antivirus support phone 
numbers FIRST Dial +1800 385 4895 NORTON antivirus customer support 
phone number. NORTON antivirus phone number .NORTON antivirus support 

[cmake-developers] [CMake 0016121]: CALL 1-800-385-4895 MS Office helpdesk phone number USA/Canada, call and get fix outlook mail issue remotely by third party J

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16121 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16121
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 14:52 EDT
Last Modified:  2016-05-27 14:52 EDT
== 
Summary:CALL 1-800-385-4895 MS Office helpdesk phone number
USA/Canada, call and get fix outlook mail issue remotely by third party J
Description: 
MS Office~Call (1800-385-4895) MS Office technical support phone number
microsoft Office helpline telephone number MS Office issue customer care phone
number HElp Call (1800-385-4895) MS Office technical support phone number +1800
385 4895 microsoft Office helpline telephone number MS Office issue customer
care phone number
MS Office issue customer care phone number microsoft Office 365 support number
microsoft Office 2010 support phone number microsoft Office 2010 technical
support microsoft Office 2010 technical support phone number microsoft Office
2013 technical support number microsoft Office 365 technical support phone
number microsoft Office contact number microsoft Office customer service
microsoft Office customer service number microsoft Office customer service phone
number microsoft Office customer support microsoft Office customer support
number microsoft Office customer support phone number microsoft Office issue
sign in support number microsoft Office issue signature support number microsoft
Office issue support number microsoft Office issue support phone number
microsoft Office issue technical support number microsoft Office express tech
support phone number microsoft Office exprss technical support phone number
microsoft Office contact number microsoft Office customer service microsoft
Office customer service number microsoft Office customer service phone number
microsoft Office customer support microsoft Office customer support number
microsoft Office customer support phone number microsoft Office issue sign in
support number microsoft Office issue signature support number microsoft Office
issue support number microsoft Office issue support phone number microsoft
Office issue technical support number microsoft Office express tech support
phone number microsoft Office exprss technical support phone number microsoft
Office help desk phone number microsoft Office help phone number microsoft
Office help support microsoft Office phone number support microsoft Office phone
support microsoft Office support contact phone number microsoft Office support
number microsoft Office support phone microsoft Office support phone number
microsoft Office support telephone number microsoft Office tech support number
microsoft Office tech support phone number microsoft Office technical support
microsoft Office technical support number microsoft Office technical support
phone number microsoft Office customer service contact number microsoft Office
customer service contact number microsoft Office customer service phone number
microsoft Office customer service toll free microsoft Office customer service
toll free number
microsoft office 2011 technical support microsoft office 2011 technical number
microsoft office 2011 technical phone microsoft office 2011 technical telephone
microsoft office 2011 technical calls microsoft office 2011 technical calls usa
microsoft office 2011 technical contact microsoft office 2011 technical contact
usa microsoft office 2011 technical help microsoft office 2011 technical help
usa microsoft office 2011 technical help desk microsoft office 2011 technical
helpline microsoft office 2011 technical helpline usa microsoft office 2011
technical toll free microsoft office 2011 technical toll free usa microsoft
office 2011 tech support microsoft office 2011 tech number microsoft office 2011
tech phone microsoft office 2011 tech telephone office 365 technical support
number office 365 technical support phone office 365 technical support phone
number office 365 technical support telephone office 365 technical support
telephone number office 365 technical support contact office 365 technical
support contact number office 365 technical support help office 365 technical
support help number office 365 technical support helpline office 365 technical
support helpline number office 365 technical support helpline phone office 365
technical support helpline phone number office 365 technical support 

[cmake-developers] [CMake 0016120]: CALL 1800-385-4895 Outlook helpdesk phone number USA/Canada, I online remote support third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16120 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16120
Category:   Documentation
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 14:45 EDT
Last Modified:  2016-05-27 14:45 EDT
== 
Summary:CALL 1800-385-4895 Outlook helpdesk phone number
USA/Canada, I online remote support third party
Description: 
+1800 385 4895 USA/Canada 
Dial 1800 385 4895 if you having problem with outlook email and get fix by
remotely. We provide support for all version of microsoft outlook issue.
microsoft outlook Tech support +1800 385 4895  ,microsoft outlook tech support
phone +1800 385 4895 ,microsoft outlook technical support phone +1800 385 4895 ,
microsoft outlook help desk +1800 385 4895  here.microsoft outlook Tech support
+1800 385 4895  ,microsoft outlook tech support phone +1800 385 4895 ,microsoft
outlook technical support phone +1800 385 4895 , microsoft outlookhelp desk
+1800 385 4895  Support Usa/Canada microsoft outlookTech support +1800 385 4895 
,microsoft outlookhelp desk phone +1800 385 4895 ,microsoft outlookCustomer care
phone +1800 385 4895  Usa/Canada  microsoft outlook tech support +1800 385 4895 
microsoft outlook help desk phone +1800 385 4895  microsoft outlook tech support
+1800 385 4895  1800 385 4895 microsoft outlook Tech Support +1800 385 4895 
microsoft outlook Tech Support +1800 385 4895  1800 385 4895 @microsoft outlook
Tech Support Phone +1800 385 4895  vides online solution for all Usa/Canada
clients. For any help of query call 1800 385 4895 to get all microsoft outlook
account solution. Call, 1800 385 4895for all type help by microsoft outlook tech
support phone +1800 385 4895 , 1800 385 4895  microsoft outlook Tech Support
Phone +1800 385 4895 , microsoft outlook Help Desk Phone +1800 385 4895 ,
microsoft outlook tech support +1800 385 4895 , microsoft outlook technical
support phone +1800 385 4895 ,@ microsoft outlook phone +1800 385 4895 ,
microsoft outlook technical support +1800 385 4895 , microsoft outlook support
phone +1800 385 4895 , microsoft outlook technical support, microsoft outlook
Customer Service Phone +1800 385 4895 , microsoft outlook Customer Service +1800
385 4895 , microsoft outlook Customer Support Phone +1800 385 4895 , microsoft
outlook Customer Support +1800 385 4895 microsoft outlook Customer Service
Usa/Canada +1800 385 4895 , microsoft outlook Customer Care +1800 385 4895 ,
microsoft outlook support team phone +1800 385 4895 , @microsoft outlook help
+1800 385 4895 -microsoft outlook Usa/Canada +1800 385 4895 ; microsoft outlook
help phone +1800 385 4895 -microsoft outlook Usa/Canada +1800 385 4895 ,
microsoft outlook Tech Support Toll free +1800 385 4895 , microsoft outlook
Support Telephone +1800 385 4895 , microsoft outlook Tech Support Telephone
+1800 385 4895 , microsoft outlook Tech Support contact +1800 385 4895 ,
microsoft outlook support contact +1800 385 4895 , microsoft outlook technical
support contact +1800 385 4895 . Call, microsoft outlook tech support phone
+1800 385 4895 , 1800 385 4895  microsoft outlook Tech Support Phone +1800 385
4895 , microsoft outlook Help Desk Phone +1800 385 4895 , microsoft outlook tech
support +1800 385 4895 , microsoft outlook technical support phone +1800 385
4895 , microsoft outlook phone +1800 385 4895 , microsoft outlook technical
support +1800 385 4895 , microsoft outlook support phone +1800 385 4895 . It is
very popular toll free +1800 385 4895  which vide by microsoft outlook technical
support, microsoft outlook Customer Service Phone +1800 385 4895 , microsoft
outlook Customer Service +1800 385 4895 , microsoft outlook Customer Support
Phone +1800 385 4895 , microsoft outlook Customer Support +1800 385 4895 ,
microsoft outlook Customer Service Usa/Canada +1800 385 4895 , microsoft outlook
Customer Care +1800 385 4895 , microsoft outlook support team phone +1800 385
4895 . Call, microsoft outlook tech support phone +1800 385 4895 , 1800 385 4895
 microsoft outlook Tech Support Phone +1800 385 4895 , microsoft outlook Help
Desk Phone +1800 385 4895 , microsoft outlook tech support +1800 385 4895 ,
microsoft outlook technical support phone +1800 385 4895 , microsoft outlook
phone +1800 385 4895 , microsoft outlook technical support +1800 385 4895 ,
microsoft outlook support phone +1800 385 4895 , microsoft outlook technical
support, 

[cmake-developers] [CMake 0016119]: Helpdesk 1800-385-4895 Outlook mail technical support phone number USA/Canada, I online remote support third party

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16119 
== 
Reported By:tec support
Assigned To:
== 
Project:CMake
Issue ID:   16119
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-27 14:41 EDT
Last Modified:  2016-05-27 14:41 EDT
== 
Summary:Helpdesk 1800-385-4895 Outlook mail technical
support phone number USA/Canada, I online remote support third party
Description: 
+1800 385 4895 USA/Canada
Get instant technical help for outlook +1800 385 4895 by online independent
technical support
help desk toll free number +1800 385 4895 Outlook help desk 24/7 hours number
+1800 385 4895 Outlook issues technical support available for online help.
Outlook is one one the popular email client,it does't need to introduce, every
body know about it. it is popular Microsoft outlook Email used for personal
information manager, Mostly used in Organizational work. So if you want to use
the outlook.com features you must have your outlook account. But if you have
already an outlook account or new outlook member needs online technical support
help for outlook.com issues including : Outlook Email Sending / Email Receiving
write a new email reply and forward email print email change outlook.com inbox
look change outlook.com password Outlook Password Recovery Recovery Hacked
Outlook Account backup and Recovery Outlook Contacts and Calendar attach file or
photo on outlook turn off outlook messages grouping Change Outlook Settings
Fetch Calendar, Contacts, One drive, etc. Call to USA Top Best Outlook customer
service number +1800 385 4895 +1800 385 4895(Toll Free, Who Provide Highly
experienced, skilled technician who receive your call while you are calling to
outlook.com customer service phone number +1800 385 4895, and after analysing
your problem, outlook technical support experts provide instant help for all
your worries. So if you want to get solution of your outlook.com problem call
24/7/365 days to outlook customer service phone number +1800 385 4895 from
Alabama Montgomery Birmingham Alaska Juneau Anchorage Arizona Phoenix Arkansas
Little Rock California Sacramento Los Angeles Colorado Denver Connecticut
Hartford Delaware Dover Wilmington Florida Tallahassee Jacksonville Georgia
Atlanta Hawaii Honolulu Idaho Boise Illinois Springfield Indiana Indianapolis
Iowa Des Moines Kansas Topeka Wichita Kentucky Frankfort Louisville Louisiana
Baton Rouge New Orleans Maine Augusta Portland Maryland Annapolis Baltimore
Massachusetts Boston Michigan Lansing Minnesota St. Paul Minneapolis Mississippi
Jackson Missouri Jefferson City Kansas City Montana Helena +1800 385 4895s
Nebraska Lincoln Omaha Nevada Carson City Las Vegas New Hampshire Concord
Manchester New Jersey Trenton 
Newark New Mexico Santa Fe Albuquerque New York Albany New York North Carolina
Raleigh Charlotte North Dakota Bismarck Fargo Ohio Columbus Oklahoma Oregon
Salem Portland Pennsylvania Rhode Island Providence South Carolina Columbia
South Dakota Pierre Sioux Falls Tennessee Nashville Texas Austin Houston Utah
Salt Lake Cit Vermont Montpelier Burlington Virginia Richmond Virginia Beach
Washington Olympia Seattle West Virginia Charleston Wisconsin Madison Milwaukee
Wyoming Cheyenne Outlook Customer Service and get instant solution for all
worries. 
Contact Details : Contact Details 
Outlook Customer Service Number +1800 385 4895 
Outlook Customer Service Phone Number +1800 385 4895 Outlook Customer Service
Contact Number +1800 385 4895 Outlook Customer Service Telephone Number +1800
385 4895 Outlook Customer Service Helpline Number +1800 385 4895 Outlook
Customer Service Toll Free Number +1800 385 4895 Phone Number +1800 385 4895 For
Outlook Outlook Customer Support Phone Number +1800 385 4895 Outlook Customer
Service Help Desk Number +1800 385 4895 Outlook Customer Service Landline Number
+1800 385 4895 Outlook Customer Service 24/7 Number +1800 385 4895 Outlook
Customer Service Number +1800 385 4895 USA Outlook Customer Service Number +1800
385 4895 Canada Outlook tech support number +1800 385 4895 Outlook tech support
phone number +1800 385 4895 Outlook tech support contact number +1800 385 4895
Outlook tech support helpline number +1800 385 4895 Outlook tech support help
Outlook tech support help desk number +1800 385 4895 Outlook tech support
telephone number +1800 385 4895 Outlook tech support mobile number +1800 385
4895 Outlook tech support 

[cmake-developers] [CMake 0016112]: "uname -p" is a very poor choice to evaluate the CMAKE_*SYSTEM_PROCESSOR and may even be wrong

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16112 
== 
Reported By:Gert Wollny
Assigned To:
== 
Project:CMake
Issue ID:   16112
Category:   CMake
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-26 05:03 EDT
Last Modified:  2016-05-26 05:03 EDT
== 
Summary:"uname -p" is a very poor choice to evaluate the
CMAKE_*SYSTEM_PROCESSOR and may even be wrong
Description: 
When running cmake in a i386 user space on top of an amd64 kernel the reported
processor type may be X86_64 instead of i386, as it so happens with DCMTK as
shown by the reproducible build effort: 

https://tests.reproducible-builds.org/rb-pkg/testing/i386/dcmtk.html

In the case of DCMTK this is of no serious consequence, but other projects might
use this value for compile time decisions that could result in code that can not
actually be run on the selected target architecture. 

Additional Information: 
For a further discussion see also: 

https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake

There is also a link to code that might be used to estimate the host arch based
on try_compile.

best, 
Gert 
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-26 05:03 Gert WollnyNew Issue
==

-- 

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] [CMake 0016111]: Memory leak during function call

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16111 
== 
Reported By:Sergey
Assigned To:
== 
Project:CMake
Issue ID:   16111
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-26 02:39 EDT
Last Modified:  2016-05-26 02:39 EDT
== 
Summary:Memory leak during function call
Description: 
There is a memory leak during function call if function contains any
if/else/endif statement.

Steps to Reproduce: 
• Create simple CMakeLists.txt with next content:

cmake_minimum_required(VERSION 3.5)

project (MyTestProject)

function (test_memory_leak)
  if(ON)
  endif()
endfunction()

while(ON)
  test_memory_leak()
endwhile()

• Run cmake-gui.exe
• Try to configure the project

Result: cmake-gui.exe will crash with out of memory (can be seen in Task
Manager)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-26 02:39 Sergey New Issue
==

-- 

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] [CMake 0016110]: LINK_LIBRARIES contains both libraries and flags, separate variables required

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16110 
== 
Reported By:Roman Popov
Assigned To:
== 
Project:CMake
Issue ID:   16110
Category:   CMake
Reproducibility:always
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-25 18:46 EDT
Last Modified:  2016-05-25 18:46 EDT
== 
Summary:LINK_LIBRARIES contains both libraries and flags, 
separate variables required
Description: 
For example, if I write my own link rule:
set(CMAKE_CXX_LINK_EXECUTABLE "echo \"  \" ")  LINK_LIBRARIES
will evaluate to : 
- flags (like: -rdynamic -Wl,-rpath,rpath1:rpath2 ...)
- static libraries (like: lib1.a -lthreads ...) 
- dynamic libraries (like: libdlib.so )

To support new gcc-compatible linking tools (for example  Synopsys VCS or
Cadence NCSIM ) flags and libs need to be separated: for example into some new
variables: LINK_LIBRARIES_FLAGS , LINK_LIBRARIES_STATIC, LINK_LIBRARIES_SHARED.

In that case user can simply define new linking rules, for example:
(CMAKE_CXX_LINK_EXECUTABLE "vcs -sysc -LDFLAGS \"  \"
   ")
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-25 18:46 Roman PopovNew Issue
==

-- 

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] [CMake 0016109]: Downloading of a file may hang indefinitely with ExternalProject

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16109 
== 
Reported By:Ilya
Assigned To:
== 
Project:CMake
Issue ID:   16109
Category:   CMake
Reproducibility:sometimes
Severity:   tweak
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-25 16:08 EDT
Last Modified:  2016-05-25 16:08 EDT
== 
Summary:Downloading of a file may hang indefinitely with
ExternalProject
Description: 
The `file(DOWNLOAD` command used by ExternalProject is not limited by any
timeouts.

It should, instead, automatically retry (and possibly continue) to download the
file.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-25 16:08 Ilya   New Issue
==

-- 

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] [CMake 0016108]: get_prerequisites failed to locate installed Microsoft Visual Studio if installed into not default location

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16108 
== 
Reported By:Andry81
Assigned To:
== 
Project:CMake
Issue ID:   16108
Category:   CPack
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-25 08:22 EDT
Last Modified:  2016-05-25 08:22 EDT
== 
Summary:get_prerequisites failed to locate installed
Microsoft Visual Studio if installed into not default location
Description: 
get_prerequisites could not find dumpbin.exe and has tried to use unexisted
objdump.exe

Reason: get_prerequisites (share/cmake-3.5/Modules/GetPrerequisites.cmake) does
search Microsoft Visual Studio incorrectly

Steps to Reproduce: 
1. make sure that all versions of Microsoft Visual Studio has installed into not
default locations

2. run cpack after cmake in the cmake build directory:
>cmake .
>cmake --build . --config release
>cpack -V --config CPackConfig.cmake .

3. observe messages "CPack Verbose: warning: could not find 'objdump' - cannot
analyze prerequisites..."

Additional Information: 
To fix it replace this in the "share/cmake-3.5/Modules/GetPrerequisites.cmake"
file:
  set(gp_cmd_paths ${gp_cmd_paths}
"C:/Program Files/Microsoft Visual Studio 9.0/VC/bin"
"C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin"
"C:/Program Files/Microsoft Visual Studio 8/VC/BIN"
"C:/Program Files (x86)/Microsoft Visual Studio 8/VC/BIN"
"C:/Program Files/Microsoft Visual Studio .NET 2003/VC7/BIN"
"C:/Program Files (x86)/Microsoft Visual Studio .NET 2003/VC7/BIN"
"/usr/local/bin"
"/usr/bin"
)

To something like this:
  set(gp_cmd_paths ${gp_cmd_paths}
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\14.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\12.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\11.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\9.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\7.1;InstallDir]/../../VC7/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\14.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\12.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\11.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\10.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\9.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\8.0;InstallDir]/../../VC/bin
   
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\7.1;InstallDir]/../../VC7/bin
"C:/Program Files/Microsoft Visual Studio 9.0/VC/bin"
"C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin"
"C:/Program Files/Microsoft Visual Studio 8/VC/BIN"
"C:/Program Files (x86)/Microsoft Visual Studio 8/VC/BIN"
"C:/Program Files/Microsoft Visual Studio .NET 2003/VC7/BIN"
"C:/Program Files (x86)/Microsoft Visual Studio .NET 2003/VC7/BIN"
"/usr/local/bin"
"/usr/bin"
)

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-25 08:22 Andry81New Issue
==

-- 

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] [CMake 0016107]: please allow for hyphens in function and macro names

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16107 
== 
Reported By:Stanislaw Halik
Assigned To:
== 
Project:CMake
Issue ID:   16107
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-22 03:58 EDT
Last Modified:  2016-05-22 03:58 EDT
== 
Summary:please allow for hyphens in function and macro names
Description: 
Given that cmake only allows for function invocation and not arithmetic, you can
support hyphens without an issue for functions also, in addition to existing
support in variable names.

Hyphens are easier on the eyes, fingers, and promote more descriptive names.
Camel case is even worse than underscores, make eyes bleed.

Steps to Reproduce: 
define and try to invoke a function with a hyphen in it.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-22 03:58 Stanislaw HalikNew Issue
==

-- 

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] [CMake 0016106]: Error generating UWP project with latest Visual Studio 2015

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16106 
== 
Reported By:Merlin1st
Assigned To:
== 
Project:CMake
Issue ID:   16106
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-19 09:03 EDT
Last Modified:  2016-05-19 09:03 EDT
== 
Summary:Error generating UWP project with latest Visual
Studio 2015
Description: 
Command

cmake -G "Visual Studio 14 2015" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0

Always fails.

Steps to Reproduce: 
Create cmake project file CMakeLists.txt with content:

project(test)
add_library(${PROJECT_NAME} STATIC test.cpp)

then run command
cmake -G "Visual Studio 14 2015" -DCMAKE_SYSTEM_NAME=WindowsStore
-DCMAKE_SYSTEM_VERSION=10.0

Generating fails.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-19 09:03 Merlin1st  New Issue
2016-05-19 09:03 Merlin1st  File Added: CMakeError.log
==

-- 

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] [CMake 0016105]: Address "RegularExpression::compile(): Expression too big."

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16105 
== 
Reported By:Roscoe A. Bartlett
Assigned To:
== 
Project:CMake
Issue ID:   16105
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-18 20:13 EDT
Last Modified:  2016-05-18 20:13 EDT
== 
Summary:Address "RegularExpression::compile(): Expression
too big."
Description: 
For large, complex CMake projects, we are getting the error
"RegularExpression::compile(): Expression too big.".  This occurs when we can't
control the build directory path to make it short (i.e. $HOME/BUILD).  The below
email chain describes a situation where they are basically stuck.



From: Bartlett, Roscoe A 
Sent: Wednesday, May 18, 2016 7:52 PM
To: 'Johnson, Seth R.'
Cc: Evans, Thomas M.; Lefebvre, Robert A.
Subject: RE: [EXTERNAL] "RegularExpression::compile(): Expression too big."

Seth,

Yes, this is a CMake thing.  For CASL VERA, as you have said, we have gotten
away with a very shallow directory.  See:

https://tribits.org/doc/TribitsBuildReference.html#installing 

But you can also avoid this by disabling RPATH or going with static libraries
(both are bad options obviously).

I have it in the Kitware backlog to resolve this somehow:

   
https://docs.google.com/document/d/1TLHRp8eTNKw7udOhwIxrOYShXQUbxAzsXeOq5cwWnKM/edit#bookmark=id.a9drhmfrc9i1

but there are several higher priority things to do first (at least for CASL
VERA).

There was a PR for TriBITS a while back that was supposed to help this in some
situations:

   https://github.com/TriBITSPub/TriBITS/pull/79

but I don’t know if there is any more that can be done in TriBITS (do you see
any duplicate libraries?).

Looking at the CMake source code, it looks like they it hard-coded a 32 bit
integer range in a long (32767L) at:

  
https://github.com/Kitware/CMake/blob/master/Source/kwsys/RegularExpression.cxx#L372

You might see if that can be expanded to a 64 bit integer (which would remove
any limitation).

Cheers,

-Ross

P.S. How is Scale/Exnihilo connected to Spack?  I someone creating a package
install script for Scale/Exnihilo for Spack?


From: Johnson, Seth R. [mailto:johnso...@ornl.gov] 
Sent: Wednesday, May 18, 2016 4:00 PM
To: Bartlett, Roscoe A
Cc: Evans, Thomas M.; Lefebvre, Robert A.
Subject: [EXTERNAL] "RegularExpression::compile(): Expression too big."

Ross, 

I'm hitting the dreaded 

RegularExpression::compile(): Expression too big.
CMake Error at packages/ScalePrograms/cmake_install.cmake:45 (file):
  file RPATH_CHANGE could not write new RPATH:

error when compiling the full Exnihilo+SCALE on the new CADES machine.  I have
little control over the compile directory; I have no control over the wacky
Spack directories; and the number of libraries required to build SCALE is huge
because of the number of subpackages in Trilinos/Exnihilo/SCALE (49 Trilinos, 46
Exnihilo, 120 SCALE, 7 system/TPL).

Is there any solution aside from "try building with a shorter directory name and
hope that it's enough and hope that the number of packages doesn't grow"?

Thanks,
Seth

P.S.
The failing regex (with colons replaced by newlines) is:
/software/tools/spack/opt/spack/linux-x86_64/gcc-4.8.5/gcc-5.3.0-5hy3c4b3xqemygnfwyl5dsc753gbvzrc/lib
/software/tools/spack/opt/spack/linux-x86_64/gcc-4.8.5/gcc-5.3.0-5hy3c4b3xqemygnfwyl5dsc753gbvzrc/lib64
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/ScaleDriver
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Origen/origami
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Origen/arp
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Origen/couple
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Origen/origen
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Origen/SONInputLib
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/CsasShift
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/TKeno
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/PolarisWrapper
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/External
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/TNewt
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Tsunami3D
/localscratch/compile/s3j-gcc5/Exnihilo-and-scale/packages/Sequence/Tsunami1D

[cmake-developers] [CMake 0016104]: The extra escape sequence \${...} in the generated export file

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16104 
== 
Reported By:Vladislav K.
Assigned To:
== 
Project:CMake
Issue ID:   16104
Category:   CMake
Reproducibility:always
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-05-15 06:35 EDT
Last Modified:  2016-05-15 06:35 EDT
== 
Summary:The extra escape sequence \${...} in the generated
export file
Description: 
The extra escape sequence \${} in the generated export file

# 
   if (UNIX)
  set(_build_type ${CMAKE_BUILD_TYPE} )
   else()
 set(_build_type \${BUILD_TYPE} ) #previously \@BUILD_TYPE@
   endif()

  install( TARGETS ${TARGETNAME}
   EXPORT  ${EXPORT_NAME}
   RUNTIME DESTINATION ${_build_type}/bin
   LIBRARY DESTINATION ${_build_type}/lib
   ARCHIVE DESTINATION ${_build_type}/lib
 )
...In cmake 3.5.2 in the performance of the export file, an error occurs


Ok.   
# in cmake_install.cmake 3.0.0 or 3.5.2 ---> ${BUILD_TYPE} 
file(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/Win64/VC12/${BUILD_TYPE}/lib"
TYPE STATIC_LIBRARY OPTIONAL FILES
"X:/CTVMO/bm/build_cm-vc12-win64/Win64/VC12/Debug/lib/bm-system-mem-debug.lib")

Ok.
 # in bm-export-debug.cmake 3.0.0 ---> ${BUILD_TYPE} 
# Import target "bm-system-mem" for configuration "Debug"
set_property(TARGET bm-system-mem APPEND PROPERTY IMPORTED_CONFIGURATIONS DEBUG)
set_target_properties(bm-system-mem PROPERTIES
  IMPORTED_IMPLIB_DEBUG
"${_IMPORT_PREFIX}/Win64/VC12/${BUILD_TYPE}/lib/bm-system-mem-debug.lib"

IMPORTED_LINK_INTERFACE_LIBRARIES_DEBUG
"Psapi;Winmm;rpcrt4;X:/CTVMO/ext_sdk/sdk/libs/win64/VC12/zlib1d.lib;X:/CTVMO/ext_sdk/sdk/libs/win64/VC12/libbz2d.lib"
  IMPORTED_LOCATION_DEBUG
"${_IMPORT_PREFIX}/Win64/VC12/${BUILD_TYPE}/bin/bm-system-mem-debug.dll"
  )

Error.  
   
 # in bm-export-debug.cmake 3.5.2 > \${_BUILD_TYPE}.
# Import target "bm-system-mem" for configuration "Debug"
set_property(TARGET bm-system-mem APPEND PROPERTY IMPORTED_CONFIGURATIONS DEBUG)
set_target_properties(bm-system-mem PROPERTIES
  IMPORTED_IMPLIB_DEBUG
"${_IMPORT_PREFIX}/Win32/VC12/\${_BUILD_TYPE}/lib/bm-system-mem-debug.lib"
  IMPORTED_LINK_INTERFACE_LIBRARIES_DEBUG
"Psapi;Winmm;rpcrt4;X:/CTVMO/ext_sdk/sdk/libs/Win32/VC12/zlib1d.lib;X:/CTVMO/ext_sdk/sdk/libs/Win32/VC12/libbz2d.lib"
  IMPORTED_LOCATION_DEBUG
"${_IMPORT_PREFIX}/Win32/VC12/\${_BUILD_TYPE}/bin/bm-system-mem-debug.dll"
  )

cmake 3.5.2 Beat changes in cmExportFileGenerator.cxx:
cmExportFileGenerator::GenerateImportPropertyCode(...
1152 os << "  " << pi->first << " "
1153   << cmExportFileGeneratorEscape(pi->second) << "\n";

previously in cmake 3.0.0 cmExportFileGenerator.cxx:
cmExportFileGenerator::GenerateImportPropertyCode(...
1026  os << "  " << pi->first << " \"" << pi->second << "\"\n";


As a special case the error is eliminated by changing in
//
static std::string cmExportFileGeneratorEscape(std::string const& str)
{
  // Escape a property value for writing into a .cmake file.
  std::string result = cmOutputConverter::EscapeForCMake(str);
  // Un-escape variable references generated by our own export code.
  cmSystemTools::ReplaceString(result,
   "\\${_IMPORT_PREFIX}",
   "${_IMPORT_PREFIX}");
  cmSystemTools::ReplaceString(result,
   "\\${CMAKE_IMPORT_LIBRARY_SUFFIX}",
   "${CMAKE_IMPORT_LIBRARY_SUFFIX}");

// My insert vv
  cmSystemTools::ReplaceString(result,
   "\\${BUILD_TYPE}",
   "${BUILD_TYPE}");
//End my insert
///
  return result;
}

P.S.
Use \@BUILD_TYPE@ in cmake 3.0.0 Ok.
Warning in cmake 3.5.2:
 To many warning of use @BUILD_TYPE@ instead @BUILD_TYPE@ by run
cmake_install.cmake 
 No way to set cmake policy CMP0053 in cmake_install.cmake

== 

Issue History 
Date ModifiedUsername   Field  

[cmake-developers] [CMake 0016103]: AUTORCC will not regenerate qrc when a resource changes

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16103 
== 
Reported By:OregonGhost
Assigned To:
== 
Project:CMake
Issue ID:   16103
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-13 06:36 EDT
Last Modified:  2016-05-13 06:36 EDT
== 
Summary:AUTORCC will not regenerate qrc when a resource
changes
Description: 
I am using CMake with Visual C++ (2010 & 2013) and Qt 5.4. My primary target has
a qrc file listed as source. AUTOMOC, AUTORCC and AUTOUIC are ON.

When the qrc file itself is changed, rcc is called.
When a resource the qrc file links to is changed, rcc is not called.

As a result, CMake happily builds an executable with old resources, unless the
qrc has been changed.

According to https://cmake.org/Bug/view.php?id=15074, this should work for some
time now. It did not for me with CMake 3.2, which I was using until recently,
nor with 3.5.2, which I have currently installed.

Steps to Reproduce: 
Relevant portions of CMakeLists.txt:

set(CMAKE_AUTORCC ON)
...
find_package(Qt5Core REQUIRED)
...
set( my_sources ... my.qrc )
...
add_executable( my WIN32 ... ${my_sources} )

Example from my.qrc:



Resources/Tags/BulletBlue.png



=> Change BulletBlue.png and qrc_my.cpp is NOT regenerated, nor recompiled.

Additional Information: 
Running on Windows 10, currently with Visual C++ 2013, but the problem also
happens on Windows 7 and with Visual C++ 2010.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-13 06:36 OregonGhostNew Issue
==

-- 

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] [CMake 0016101]: ADD_SUBDIRECTORY with EXCLUDE_FROM_ALL fails to include target dependencies(XCode Generator)

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16101 
== 
Reported By:Robert Bielik
Assigned To:
== 
Project:CMake
Issue ID:   16101
Category:   CMake
Reproducibility:always
Severity:   block
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-12 04:07 EDT
Last Modified:  2016-05-12 04:07 EDT
== 
Summary:ADD_SUBDIRECTORY with EXCLUDE_FROM_ALL fails to
include target dependencies(XCode Generator)
Description: 
If the main target executable depends on targets that are in a subdirectory,
using EXCLUDE_FROM_ALL in ADD_SUBDIRECTORY fails to include the target
dependencies, leading to linking errors.

>From documentation: 
"Note that inter-target dependencies supercede this exclusion. If a target built
by the parent project depends on a target in the subdirectory, the dependee
target will be included in the parent project build system to satisfy the
dependency"

This works fine for MSYS, Unix and Visual Studio generators, but NOT XCode.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-12 04:07 Robert Bielik  New Issue
==

-- 

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] [CMake 0016100]: Implicit link information parsing reads the wrong line from 'pathcc -v' output

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16100 
== 
Reported By:Michał Górny
Assigned To:
== 
Project:CMake
Issue ID:   16100
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-11 03:22 EDT
Last Modified:  2016-05-11 03:22 EDT
== 
Summary:Implicit link information parsing reads the wrong
line from 'pathcc -v' output
Description: 
$ pathcc --version
PathScale EKOPath(tm) Compiler Suite: Version 6.0.779
Built on: 
Thread model: posix
GNU gcc compatible version 4.2.1
[...]

When CMake attempts to get ABI info from the compiler, it gets the following
output:

[2/2] Linking C executable cmTC_cfda2   

PathScale EKOPath(tm) Compiler Suite: Version 6.0.570   

Built on:   

Thread model: posix 

GNU gcc compatible version 4.2.1

/opt/ekopath/lib/6.0.570/x8664/ldfe -v -TARG:isa=x86_64
-TARG:processor=barcelona -TARG:sse=on -TARG:sse2=on -TARG:sse3=on
-TARG:ssse3=off -TARG:sse4a=off -TARG:sse4_1=off -TARG:sse4_2=off -TARG:avx=off
-TARG:avx2=off -TARG:avx512dq=off -TARG:avx512vl=off -TARG:avx512bw=off
-TARG:avx512er=off -TARG:avx512f=off -TARG:fma=off -TARG:fma4=off -TARG:xop=off
-TARG:aes=off -TARG:pclmul=off -TARG:3dnow=off -o cmTC_cfda2 -show
CMakeFiles/cmTC_cfda2.dir/CMakeCCompilerABI.c.o --as-needed -lgcc -lc -lmv
-lmpath -lm --no-as-needed -lpscrt -lc
/opt/ekopath/lib/6.0.570/x8664/../../../x8664/bin/ld
-L/opt/ekopath/lib/6.0.570/x8664/64/system-provided/
-L/opt/ekopath/lib/6.0.570/x8664/64/ -rpath=/opt/ekopath/lib/6.0.570/x8664/64/
--dynamic-linker=/lib64/ld-linux-x86-64.so.2 -melf_x86_64 --eh-frame-hdr -v -o
cmTC_cfda2 /opt/ekopath/lib/6.0.570/x8664/64/system-provided/crt1.o
/opt/ekopath/lib/6.0.570/x8664/64/system-provided/crti.o
/opt/ekopath/lib/6.0.570/x8664/64/crtbegin.o
CMakeFiles/cmTC_cfda2.dir/CMakeCCompilerABI.c.o --as-needed
-L/opt/ekopath/lib/6.0.570/x8664/64/ -lgcc /lib64/libc.so.6
/usr/lib64/libc_nonshared.a /lib64/ld-linux-x86-64.so.2
-L/opt/ekopath/lib/6.0.570/x8664/64/ -lmv -L/opt/ekopath/lib/6.0.570/x8664/64/
-lmpath /lib64/libm.so.6 /lib64/libmvec.so.1 --no-as-needed
/opt/ekopath/lib/6.0.570/x8664/64//libpscrt.a /lib64/libc.so.6
/usr/lib64/libc_nonshared.a /lib64/ld-linux-x86-64.so.2
/opt/ekopath/lib/6.0.570/x8664/64/crtend.o
/opt/ekopath/lib/6.0.570/x8664/64/system-provided/crtn.o
GNU ld (GNU Binutils) 2.25


Parsed C implicit link information from above output:   

  link line regex: [^( *|.*[/\])(ld|([^/\]+-)?ld|collect2)[^/\]*( |$)]
[...]
  link line: [/opt/ekopath/lib/6.0.570/x8664/ldfe -v -TARG:isa=x86_64
-TARG:processor=barcelona -TARG:sse=on -TARG:sse2=on -TARG:sse3=on
-TARG:ssse3=off -TARG:sse4a=off -TARG:sse4_1=off -TARG:sse4_2=off -TARG:avx=off
-TARG:avx2=off -TARG:avx512dq=off -TARG:avx512vl=off -TARG:avx512bw=off
-TARG:avx512er=off -TARG:avx512f=off -TARG:fma=off -TARG:fma4=off -TARG:xop=off
-TARG:aes=off -TARG:pclmul=off -TARG:3dnow=off -o cmTC_cfda2 -show
CMakeFiles/cmTC_cfda2.dir/CMakeCCompilerABI.c.o --as-needed -lgcc -lc -lmv
-lmpath -lm --no-as-needed -lpscrt -lc ]
[...]


However, this is not the correct line. ldfe is an internal helper, and it is
immediately followed by a call to 'ld' which has all the correct -L flags. As a
result, pathcc doesn't parse the correct data and doesn't determine multiarch
tuple on Debian.

Maybe it would be appropriate to not stop at the first line matching the regular
expression, and parse the last line matching it instead? This would prevent
CMake from parsing the wrapper when it's followed by an actual ld call.

Steps to Reproduce: 
1. install ekopath nightly (e.g.
http://c591116.r16.cf2.rackcdn.com/ekopath/nightly/Linux/ekopath-2016-04-28-installer.run),

2. attempt to build any CMake project.

On multiarch systems, find_library() won't be able to find any libraries. On
other systems, you can also see the problem when looking at CMakeOutput.log.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-11 03:22 Michał Górny   New Issue

[cmake-developers] [CMake 0016098]: CMake fails to read its own cache after writing a variable with a carriage return.

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16098 
== 
Reported By:tibur
Assigned To:
== 
Project:CMake
Issue ID:   16098
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-10 10:41 EDT
Last Modified:  2016-05-10 10:41 EDT
== 
Summary:CMake fails to read its own cache after writing a
variable with a carriage return.
Description: 
I let cmake read a version number from a file, and then store a variable made
from this version number string.

{{{
cmake_minimum_required(VERSION 2.8.9)

file(READ "version.txt" API_VERSION)
string(REPLACE "." ";" API_VERSION_LIST ${API_VERSION})
list(GET API_VERSION_LIST 0 API_VERSION_MAJOR)
list(GET API_VERSION_LIST 1 API_VERSION_MINOR)
list(GET API_VERSION_LIST 2 API_VERSION_PATCH)

#string(STRIP ${API_VERSION_PATCH} API_VERSION_PATCH)

set(TEST "${API_VERSION_PATCH}_TEST" CACHE STRING "Offending entry")
}}}

If the version.txt file contains a newline at the end, then the corresponding
variable is broken within cmake cache. CMake then complains:

CMake Error: Parse error in cache file [...]/cmake_bug/build/CMakeCache.txt.
Offending entry: _TEST

If we look at CMakeCache.txt we can see the following lines:

TEST:STRING=4
_TEST

Steps to Reproduce: 
Get both files.
Use cmake first to create the build directory, then a second time on that build
folder.

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-10 10:41 tibur  New Issue
2016-05-10 10:41 tibur  File Added: version.txt  
==

-- 

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] [CMake 0016099]: cmake and cmake-gui don

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16099 
== 
Reported By:Stefan Zink
Assigned To:
== 
Project:CMake
Issue ID:   16099
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-10 10:45 EDT
Last Modified:  2016-05-10 10:45 EDT
== 
Summary:cmake and cmake-gui don
Description: 

cmake-gui:
3.5 !> 3.0
3.5 > 3.0
Configuring done

cmake:
3.5 > 3.0
3.5 > 3.0
-- Configuring done


== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-10 10:45 Stefan ZinkNew Issue
2016-05-10 10:45 Stefan ZinkFile Added: CMakeLists.txt
==

-- 

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] [CMake 0016097]: FindCUDA.cmake implicit target_link_libraries() can not be mixed with new signature

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16097 
== 
Reported By:Nils Gladitz
Assigned To:
== 
Project:CMake
Issue ID:   16097
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-09 10:31 EDT
Last Modified:  2016-05-09 10:31 EDT
== 
Summary:FindCUDA.cmake implicit target_link_libraries() can
not be mixed with new signature
Description: 
e.g. CUDA_ADD_LIBRARY currently implicitly links to the CUDA libraries with:
  target_link_libraries(${cuda_target} ${CUDA_LIBRARIES})

Afterwards additional libraries can not be linked with the newer
PRIVATE|PUBLIC|INTERFACE signature (since signatures can not be mixed).

It would be nice if one of these keywords could be added to the implicit
target_link_libraries() calls upon user request.

Steps to Reproduce: 
cmake_minimum_required(VERSION 3.5.1)

find_package(CUDA REQUIRED)

file(WRITE my_cuda_lib.cpp "")
cuda_add_library(my_cuda_lib SHARED my_cuda_lib.cpp)

file(WRITE some_other_lib.cpp "")
add_library(some_other_lib SHARED some_other_lib.cpp)

# The plain signature for target_link_libraries has already been used with
# the target "my_cuda_lib".  All uses of target_link_libraries with a target
# must be either all-keyword or all-plain.

target_link_libraries(my_cuda_lib PRIVATE some_other_lib)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-09 10:31 Nils Gladitz   New Issue
==

-- 

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] [CMake 0016096]: FindCUDA requires dynamic runtime even if building statically

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16096 
== 
Reported By:Ryan Desmond
Assigned To:
== 
Project:CMake
Issue ID:   16096
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-06 15:03 EDT
Last Modified:  2016-05-06 15:03 EDT
== 
Summary:FindCUDA requires dynamic runtime even if building
statically
Description: 
In
https://gitlab.kitware.com/cmake/cmake/commit/7fea2b77df2d70283f4918a8ff52836dbc68db6b,
support was added to use the static CUDA libraries.  The script still checks for
and requires that the dynamic libraries are installed in order to build
successfully, though they are not needed for a static build.

Steps to Reproduce: 
 - Setup a machine on which to use build CUDA, which has the static libraries
available
 - Remove or delete cudart.so
 - Create a cmake script with `find_package(CUDA REQUIRED)`
 - When run, the script will fail with:

CMake Error at
/usr/local/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
  Could NOT find CUDA (missing: CUDA_CUDART_LIBRARY) (found version "7.5")
Call Stack (most recent call first):
  /usr/local/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388
(_FPHSA_FAILURE_MESSAGE)
  /usr/local/share/cmake-3.5/Modules/FindCUDA.cmake:949
(find_package_handle_standard_args)
  imagery/CMakeLists.txt:43 (find_package)


Additional Information: 

The dynamic library is located at:

 725 cuda_find_library_local_first(CUDA_CUDART_LIBRARY cudart "\"cudart\"
library")

The static library is located at:

 734   cuda_find_library_local_first(CUDA_cudart_static_LIBRARY cudart_static
"static CUDA runtime library")

Later in the script, the variable for the dynamic library is required, even if
the library itself is not required for a successful build.

 950 find_package_handle_standard_args(CUDA
 951   REQUIRED_VARS
 952 CUDA_TOOLKIT_ROOT_DIR
 953 CUDA_NVCC_EXECUTABLE
 954 CUDA_INCLUDE_DIRS
 955 CUDA_CUDART_LIBRARY
 956   VERSION_VAR
 957 CUDA_VERSION
 958   )
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-06 15:03 Ryan Desmond   New Issue
==

-- 

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] [CMake 0016095]: Latest CMake bundles insecure copy of Expat

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16095 
== 
Reported By:Sebastian Pipping
Assigned To:
== 
Project:CMake
Issue ID:   16095
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-05 12:36 EDT
Last Modified:  2016-05-05 12:36 EDT
== 
Summary:Latest CMake bundles insecure copy of Expat
Description: 
I found that even recent CMake bundles a copy of libexpat in folder
"Utilities/cmexpat" [1] that is 12 years old (version 1.95.2 [2]) and has known
security issues. Due to the auto-detection of Expat at [3], I do not worry about
users of Linux or OS X too much. How about Windows?

Please consider resolving the bundled copy or update to the latest release of
Expat. Thank you!

Best, Sebastian


[1]
https://github.com/Kitware/CMake/tree/1d4ab06a7045edf366c689ba5e29bbc35d08718e/Utilities/cmexpat
[2]
https://github.com/Kitware/CMake/blob/1d4ab06a7045edf366c689ba5e29bbc35d08718e/Utilities/cmexpat/expat.h#L732
[3]
https://github.com/Kitware/CMake/blob/1d4ab06a7045edf366c689ba5e29bbc35d08718e/CMakeLists.txt#L417
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-05 12:36 Sebastian PippingNew Issue
==

-- 

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] [CMake 0016093]: Order of --build and --target "cmake" command options matters

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16093 
== 
Reported By:Andreas Schuh
Assigned To:
== 
Project:CMake
Issue ID:   16093
Category:   CMake
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-04 10:21 EDT
Last Modified:  2016-05-04 10:21 EDT
== 
Summary:Order of --build and --target "cmake" command
options matters
Description: 
The following results in an error as if I'd specified a subdirectory underneath
the current build directory. Changing the order of --build and --target options
works as expected, though. Just "--build ." followed directly by "--target"
gives this error.

cmake --config Release --build . --target apidoc
CMake Error: The source directory "/Users/as12312/Software/BASIS/Xcode/apidoc"
does not exist.
Specify --help for usage, or press the help button on the CMake GUI.


cmake --config Release --target apidoc --build .
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-04 10:21 Andreas Schuh  New Issue
==

-- 

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] [CMake 0016092]: Module CheckIncludeFile should notify in case of compiler flag errors

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16092 
== 
Reported By:Antonio
Assigned To:
== 
Project:CMake
Issue ID:   16092
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-03 05:10 EDT
Last Modified:  2016-05-03 05:10 EDT
== 
Summary:Module CheckIncludeFile should notify in case of
compiler flag errors
Description: 
(Problem was first mentioned in mailing list 2 weeks ago, although there was no
feedback)

CheckIncludeFile will return "header not found" if some wrong compiler flags is
set (not accepted by the compiler).

I noticed the problem when having a "check include" failure even if I was
certain the include file should be found in the include paths I had set.
When I hacked into:
CheckIncludeFile.cmake
this line:
message(STATUS "OUTPUT=${OUTPUT}")
it turned out the problem was not in including file, but in the flags that
were passed to the compiler, causing a failure that the module interprets as
"the header could not be found".

I think an error message should be printed instead in this case.
This could be handled in 2 ways:
a) Either checking first of all if, with the given flags, the compiler will
succeed in compiling a source file containing JUST an empty main function.
For efficiency, this check might even be done AFTER the first try_compile
fails.
b) Or, in case of failure, checking that the error returned is JUST the
cannot find error message.

Option a) seems to have the advantage of being extremely easy to implement,
although might introduce some overhead.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-03 05:10 AntonioNew Issue
==

-- 

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] [CMake 0016091]: RelWithDebInfo links Boost debug libraries

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16091 
== 
Reported By:LCID Fire
Assigned To:
== 
Project:CMake
Issue ID:   16091
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-03 02:38 EDT
Last Modified:  2016-05-03 02:38 EDT
== 
Summary:RelWithDebInfo links Boost debug libraries
Description: 
Since switching to 3.5, Boost is trying to link against 
e.g. libboost_system-vc140-mt-gd-1_60.lib for RelWithDebInfo.
This of course fails because iterator level and other symbols differ.

Linker errors:
error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't
match value '0' in files.obj
error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MDd_DynamicDebug'
doesn't match value 'MD_DynamicRelease' in files.obj
fatal error LNK1104: cannot open file 'libboost_filesystem-vc140-mt-1_60.lib'

Steps to Reproduce: 
Boost_DEBUG prints:
_boost_TEST_VERSIONS =
1.61.0;1.61;1.60.0;1.60;1.59.0;1.59;1.58.0;1.58;1.57.0;1.57;1.56.0;1.56;1.55.0;1.55;1.54.0;1.54;1.53.0;1.53;1.52.0;1.52;1.51.0;1.51;1.50.0;1.50;1.49.0;1.49;1.48.0;1.48;1.47.0;1.47;1.46.1;1.46.0;1.46;1.45.0;1.45;1.44.0;1.44;1.43.0;1.43;1.42.0;1.42;1.41.0;1.41;1.40.0;1.40;1.39.0;1.39;1.38.0;1.38;1.37.0;1.37;1.36.1;1.36.0;1.36;1.35.1;1.35.0;1.35;1.34.1;1.34.0;1.34;1.33.1;1.33.0;1.33
Boost_USE_MULTITHREADED = ON
Boost_USE_STATIC_LIBS = ON
Boost_USE_STATIC_RUNTIME = OFF
Boost_ADDITIONAL_VERSIONS =
Boost_NO_SYSTEM_PATHS = ON
Declared as CMake or Environmental Variables:
  BOOST_ROOT =
  BOOST_INCLUDEDIR = C:/boost/lib
  BOOST_LIBRARYDIR = C:/boost/lib/lib64-msvc-14.0
_boost_TEST_VERSIONS =
1.61.0;1.61;1.60.0;1.60;1.59.0;1.59;1.58.0;1.58;1.57.0;1.57;1.56.0;1.56;1.55.0;1.55;1.54.0;1.54;1.53.0;1.53;1.52.0;1.52;1.51.0;1.51;1.50.0;1.50;1.49.0;1.49;1.48.0;1.48;1.47.0;1.47;1.46.1;1.46.0;1.46;1.45.0;1.45;1.44.0;1.44;1.43.0;1.43;1.42.0;1.42;1.41.0;1.41;1.40.0;1.40;1.39.0;1.39;1.38.0;1.38;1.37.0;1.37;1.36.1;1.36.0;1.36;1.35.1;1.35.0;1.35;1.34.1;1.34.0;1.34;1.33.1;1.33.0;1.33
location of version.hpp: C:/boost/lib/boost/version.hpp
version.hpp reveals boost 1.60.0
guessed _boost_COMPILER = -vc140
_boost_MULTITHREADED = -mt
_boost_RELEASE_ABI_TAG = -
_boost_DEBUG_ABI_TAG = -gd
_boost_LIBRARY_SEARCH_DIRS_RELEASE =
C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH_boost_LIBRARY_SEARCH_DIRS_DEBUG
  = C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH
Searching for FILESYSTEM_LIBRARY_RELEASE:
libboost_filesystem-vc140-mt-1_60;libboost_filesystem-vc140-mt;libboost_filesystem-mt-1_60;libboost_filesystem-mt;libboost_filesystem
 Boost_LIBRARY_DIR_RELEASE = C:/boost/lib/lib64-msvc-14.0
_boost_LIBRARY_SEARCH_DIRS_RELEASE =
C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH
Searching for FILESYSTEM_LIBRARY_DEBUG:
libboost_filesystem-vc140-mt-gd-1_60;libboost_filesystem-vc140-mt-gd;libboost_filesystem-mt-gd-1_60;libboost_filesystem-mt-gd;libboost_filesystem-mt;libboost_filesystem
 Boost_LIBRARY_DIR_DEBUG = C:/boost/lib/lib64-msvc-14.0
_boost_LIBRARY_SEARCH_DIRS_DEBUG =
C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH
Searching for SYSTEM_LIBRARY_RELEASE:
libboost_system-vc140-mt-1_60;libboost_system-vc140-mt;libboost_system-mt-1_60;libboost_system-mt;libboost_system
 Boost_LIBRARY_DIR_RELEASE = C:/boost/lib/lib64-msvc-14.0
_boost_LIBRARY_SEARCH_DIRS_RELEASE =
C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH
Searching for SYSTEM_LIBRARY_DEBUG:
libboost_system-vc140-mt-gd-1_60;libboost_system-vc140-mt-gd;libboost_system-mt-gd-1_60;libboost_system-mt-gd;libboost_system-mt;libboost_system
 Boost_LIBRARY_DIR_DEBUG = C:/boost/lib/lib64-msvc-14.0
_boost_LIBRARY_SEARCH_DIRS_DEBUG =
C:/boost/lib/lib64-msvc-14.0;NO_DEFAULT_PATH;NO_CMAKE_FIND_ROOT_PATH
Boost_FOUND = 1
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-03 02:38 LCID Fire  New Issue
==

-- 

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 

[cmake-developers] [CMake 0016090]: FindwxWidgets looks in /usr/include/wx-2.8/ for wxWidgets 3.0

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16090 
== 
Reported By:Jason Yundt
Assigned To:
== 
Project:CMake
Issue ID:   16090
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-02 19:34 EDT
Last Modified:  2016-05-02 19:34 EDT
== 
Summary:FindwxWidgets looks in /usr/include/wx-2.8/ for
wxWidgets 3.0
Description: 
I was trying to build SLADE v3.1.1.1 (slade.mancubus.net), but when cmake got to
the following line in src/CMakeLists.txt,

find_package(wxWidgets 3.0 COMPONENTS std aui gl stc richtext propgrid media
webview REQUIRED)

it crashes with the following:

jayman@computer-4:~/src/doom/tools/slade/slade-stable/dist> cmake ..
CMake Error at /usr/share/cmake/Modules/FindwxWidgets.cmake:861 (file):
  file failed to open for reading (No such file or directory):

/usr/include/wx-2.8/wx/version.h
Call Stack (most recent call first):
  src/CMakeLists.txt:5 (find_package)


CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
  Could NOT find wxWidgets: Found unsuitable version "..", but required is at
  least "3.0" (found
 
-L/usr/lib64;-pthread;;;-lwx_gtk3u_aui-3.0;-lwx_gtk3u_gl-3.0;-lwx_gtk3u_stc-3.0;-lwx_gtk3u_richtext-3.0;-lwx_gtk3u_propgrid-3.0;-lwx_gtk3u_media-3.0;-lwx_gtk3u_xrc-3.0;-lwx_gtk3u_webview-3.0;-lwx_gtk3u_html-3.0;-lwx_gtk3u_qa-3.0;-lwx_gtk3u_adv-3.0;-lwx_gtk3u_core-3.0;-lwx_baseu_xml-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0)
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:386
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake/Modules/FindwxWidgets.cmake:887
(find_package_handle_standard_args)
  src/CMakeLists.txt:5 (find_package)


-- Configuring incomplete, errors occurred!
See also
"/home/jayman/src/doom/tools/slade/slade-stable/dist/CMakeFiles/CMakeOutput.log".
jayman@computer-4:~/src/doom/tools/slade/slade-stable/dist> 


Steps to Reproduce: 
1. Install wxWidgets 3.0 GTK3 (sudo zypper install wxGTK3-3_0-devel)
2. Get SLADE stable sources:
   a. git clone https://github.com/sirjuddington/SLADE.git slade
   b. git checkout stable
3. cd slade/dist
4. cmake ..
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-02 19:34 Jason YundtNew Issue
==

-- 

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] [CMake 0016089]: Overriding subdir options no longer works

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16089 
== 
Reported By:LCID Fire
Assigned To:
== 
Project:CMake
Issue ID:   16089
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-02 12:37 EDT
Last Modified:  2016-05-02 12:37 EDT
== 
Summary:Overriding subdir options no longer works
Description: 
Setting options for subdirectory no longer seems to work.



Steps to Reproduce: 
# CMakeLists.txt content
set( myoption ON )

add_subdirectory( test )

# test/CMakeLists.txt content
option( myoption "A test" OFF )
message( "TEST_VALUE ${myoption}" )

Additional Information: 
Output is:
TEST_VALUE OFF
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-02 12:37 LCID Fire  New Issue
==

-- 

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] [CMake 0016088]: How to add CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS for cuda files ?

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16088 
== 
Reported By:hevy
Assigned To:
== 
Project:CMake
Issue ID:   16088
Category:   CMake
Reproducibility:always
Severity:   block
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-02 10:32 EDT
Last Modified:  2016-05-02 10:32 EDT
== 
Summary:How to add CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS for cuda
files ?
Description: 
Hi,

I am currently using CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS to compile some 3rdParty
but  it does not seems to work with cuda files.

1. Is it normal ?
2. if yes, how could I add this feature to cmake ?

Thanks,

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-02 10:32 hevy   New Issue
==

-- 

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] [CMake 0016087]: get_filename_component has incomplete documentation

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16087 
== 
Reported By:regnirpsj
Assigned To:
== 
Project:CMake
Issue ID:   16087
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-05-01 12:36 EDT
Last Modified:  2016-05-01 12:36 EDT
== 
Summary:get_filename_component has incomplete documentation
Description: 
documentation for 'get_filename_component' does not mention that absolute paths
are build with respect to 'CMAKE_SOURCE_DIR'. that is rather inconvenient when
trying to create an absolute path with respect to, say, 'CMAKE_BINARY_DIR' in an
out-of-tree build.

Additional Information: 
the dependency of 'get_filename_component' to 'CMAKE_SOURCE_DIR' was mentioned
in issue https://cmake.org/Bug/view.php?id=2797.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-05-01 12:36 regnirpsj  New Issue
==

-- 

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] [CMake 0016086]: Ninja generator doesn't handle multiple Mac apps using the same plist file with MACOSX_BUNDLE_INFO_PLIST

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16086 
== 
Reported By:Florent Castelli
Assigned To:
== 
Project:CMake
Issue ID:   16086
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-28 05:37 EDT
Last Modified:  2016-04-28 05:37 EDT
== 
Summary:Ninja generator doesn't handle multiple Mac apps
using the same plist file with MACOSX_BUNDLE_INFO_PLIST
Description: 
If an app is using the same plist file using the target property
MACOSX_BUNDLE_INFO_PLIST, CMake will add a dependency on that plist file as it
is a template with variables that needs processing at generation time.

But if multiple apps are using the same plist template, CMake will add multiple
dependencies to the same file on the Re-Run target and Ninja will then warn:
ninja: warning: multiple rules generate ../Info.plist.in. builds involving this
target will not be correct; continuing anyway [-w dupbuild=warn]

A fix would probably be to deduplicate the dependencies for rerunning CMake.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-28 05:37 Florent CastelliNew Issue
==

-- 

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] [CMake 0016085]: No Android Studio Generator

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16085 
== 
Reported By:nguillot
Assigned To:
== 
Project:CMake
Issue ID:   16085
Category:   Modules
Reproducibility:always
Severity:   feature
Priority:   high
Status: new
== 
Date Submitted: 2016-04-27 08:02 EDT
Last Modified:  2016-04-27 08:02 EDT
== 
Summary:No Android Studio Generator
Description: 
With the Android Experimental Gradle plugin
(http://tools.android.com/tech-docs/new-build-system/gradle-experimental) you
enable the Android Studio C/C++ debug support. You can use either the
"com.android.model.application" (Android application with Java and C/C++ sources
code) , either "com.android.model.library" (Android Library with java and C/C++
sources) or "com.android.model.native" (only C/C++ sources) plugin to do that.
As explain in the "Other Build Options" section the Gradle "ndk" section
describe the compilation and linking options. The "NDK Dependencies" section of
this page explain how to manage the dependency between the libraries. 

Additional Information: 
You can start with project that I published on Github to make your own
experiment: https://github.com/nguillot/HelloCPP. Or use the official samples:
https://github.com/googlesamples/android-ndk.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-27 08:02 nguillot   New Issue
==

-- 

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] [CMake 0016084]: try_compile incorrect behavior for iOS universal build (device + simulator) with CMAKE_IOS_INSTALL_COMBINED

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16084 
== 
Reported By:ranjak
Assigned To:
== 
Project:CMake
Issue ID:   16084
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-27 06:41 EDT
Last Modified:  2016-04-27 06:41 EDT
== 
Summary:try_compile incorrect behavior for iOS universal
build (device + simulator) with CMAKE_IOS_INSTALL_COMBINED
Description: 
When configuring an iOS Xcode project using CMAKE_IOS_INSTALL_COMBINED
(introduced in CMake 3.5) to produce universal binaries that contain code for
both iPhone (ARM) and simulator (x86) code, I would like try_compile to compile
for both the device and the simulator. However, currently, try_compile only
compiles for the device.

This causes projects that rely on try_compile to be possibly misconfigured for
the simulator build (which can obviously lead to build failures and/or
incorrect/non-existent values for architecture-dependent parameters set at
configuration time).

This problem also arises without CMAKE_IOS_INSTALL_COMBINED, if you want to use
Xcode to build for both device(s) and simulator(s) without re-running CMake
every time you switch between the two.

Try_compile should instead call xcodebuild twice, one time with -sdk iphoneos
and the other with -sdk iphonesimulator.


Steps to Reproduce: 
Configure a project with IOS_INSTALL_COMBINED set to TRUE, and use try_compile
in this project.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-27 06:41 ranjak New Issue
==

-- 

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] [CMake 0016083]: ExternalProject with empty GIT_SUBMODULES does not initialize submodules of submodules

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16083 
== 
Reported By:Ilya
Assigned To:
== 
Project:CMake
Issue ID:   16083
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-26 17:13 EDT
Last Modified:  2016-04-26 17:13 EDT
== 
Summary:ExternalProject with empty GIT_SUBMODULES does not
initialize submodules of submodules
Description: 
Current implementation uses the following command to get submodules:

1. `git submodule init`
2. `submodule update --recursive`

This is enough to initialize direct submodules of the repo, however it leaves
submodules of submodules uninitialized.

To address this, [2] (and possibly [1]) must be changed to `submodule update
--recursive --init`

Steps to Reproduce: 
1. Add an external project that has submodule which has its own submodule
2. Try to pull sources of this project
3. Check that submodule of submodule was not initialized
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-26 17:13 Ilya   New Issue
==

-- 

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] [CMake 0016082]: Support alternative download URL in ExternalProject_Add

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16082 
== 
Reported By:A. Klitzing
Assigned To:
== 
Project:CMake
Issue ID:   16082
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-26 09:04 EDT
Last Modified:  2016-04-26 09:04 EDT
== 
Summary:Support alternative download URL in
ExternalProject_Add
Description: 
We use a script with a lot of ExternalProject_Add to generate our dependencies.
But some project moves their files to different destination after some time. For
example: openssl

It would be very helpful if ExternalProject_Add could support alternative
download URLs as a list. So cmake could try the next URL if a connection error
occurs.

ExternalProject_Add(dummy
URL "${FIRST_URL}" "${SECOND_URL}" "${THIRD_URL}"
)


Additional Information: 
OpenSSL:

Current version:
ftp://ftp.openssl.org/source/

If a new version arrives the old one will be moved to:
ftp://ftp.openssl.org/source/old/

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-26 09:04 A. KlitzingNew Issue
==

-- 

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] [CMake 0016079]: Unknown extension ".c" for file

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16079 
== 
Reported By:rtsisyk
Assigned To:
== 
Project:CMake
Issue ID:   16079
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-24 06:39 EDT
Last Modified:  2016-04-24 06:39 EDT
== 
Summary:Unknown extension ".c" for file
Description: 
Ubuntu 14.04 inside Windows 10 LXSS.



```

-- The C compiler identification is unknown
CMake Error at Modules/CMakeDetermineCCompiler.cmake:181 (configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:19 (project)


-- The CXX compiler identification is unknown
CMake Error at Modules/CMakeDetermineCXXCompiler.cmake:179 (configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:19 (project)


-- Check for working C compiler: /usr/bin/gcc
CMake Error at Modules/CMakeTestCCompiler.cmake:47 (try_compile):
  Unknown extension ".c" for file

/home/roman/cmake-3.5.2/CMakeFiles/CMakeTmp/testCCompiler.c

  try_compile() works only for enabled languages.  Currently these are:

C CXX

  See project() command to enable other languages.
Call Stack (most recent call first):
  CMakeLists.txt:19 (project)


-- Check for working C compiler: /usr/bin/gcc -- broken
CMake Error at Modules/CMakeTestCCompiler.cmake:61 (message):
  The C compiler "/usr/bin/gcc" is not able to compile a simple test program.

  It fails with the following output:





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:19 (project)


-- Configuring incomplete, errors occurred!
See also "/home/roman/cmake-3.5.2/CMakeFiles/CMakeOutput.log".
See also "/home/roman/cmake-3.5.2/CMakeFiles/CMakeError.log".
-
Error when bootstrapping CMake:
Problem while running initial CMake
-
```

Steps to Reproduce: 
1. Install Windows Subsystem for Linux on Windows 10 
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/
2. Install cmake (any version)
apt-get install build-essential cmake
3. Try to build a simple C or CXX project
cmake .

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-24 06:39 rtsisykNew Issue
2016-04-24 06:39 rtsisykFile Added: 7.png
==

-- 

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] [CMake 0016078]: CMake on Cygwin with clang not creating expected dll.a

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16078 
== 
Reported By:Thomas Nilsson
Assigned To:
== 
Project:CMake
Issue ID:   16078
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-24 04:28 EDT
Last Modified:  2016-04-24 04:28 EDT
== 
Summary:CMake on Cygwin with clang not creating expected
dll.a
Description: 
I'm building a shared library and an application using that lib on Cygwin. With
GCC CMake creates a .dll.a to use when linking. Switching to clang I get

[ 34%] Built target xyz_shared
make[2]: *** No rule to make target 'src/libxyz_shared.dll.a', needed by
'xyz.exe'.  Stop.


Steps to Reproduce: 
On Cygwin, use the attached CMakeLists.txt and see it produce
'cygxyz_shared.dll' and 'libxyz_shared.dll.a'.

Clear the build directory and do

  $ CC=clang cmake ..; make

and it will not create 'libxyz_shared.dll.a'.

Additional Information: 
As described in this Stackoverflow question
(http://stackoverflow.com/questions/36294199) the culprit seems to be the lack
of the flags '-Wl,--enable-auto-import' when using clang.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-24 04:28 Thomas Nilsson New Issue
2016-04-24 04:28 Thomas Nilsson File Added: CMakeLists.txt
==

-- 

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] [CMake 0016077]: FindProtobuf.cmake doesn't have required flexibility to configure protoc usage for all use cases

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16077 
== 
Reported By:skebanga
Assigned To:
== 
Project:CMake
Issue ID:   16077
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-22 17:09 EDT
Last Modified:  2016-04-22 17:09 EDT
== 
Summary:FindProtobuf.cmake doesn't have required flexibility
to configure protoc usage for all use cases
Description: 
I have here a very simple test project which has 2 protobuf files, one of which
is included in the other.

Using cmake, I will create a static library for each generated protobuf message.

##Protobuf files:

**`src/foo/message.proto`:**

package test.foo;

message FooMsg
{
required string s = 1;
}

**`src/bar/message.proto`:**

package test.bar;
import "foo/message.proto";

message BarMsg
{
optional foo.FooMsg f = 1;
}

##CMake files:

I build `lib_foo` from generated `foo/message.proto` files.

**`src/foo/CMakeLists.txt`:**

protobuf_generate_cpp(PROTO_SRCS PROTO_HDRS message.proto)

add_library(lib_foo STATIC ${PROTO_SRCS})

I build `lib_bar` from the generated `bar/message.proto` files, and link in
`lib_foo`:

**`src/bar/CMakeLists.txt`:**

protobuf_generate_cpp(PROTO_SRCS PROTO_HDRS message.proto )

add_library(lib_bar STATIC ${PROTO_SRCS})

target_link_libraries(lib_bar lib_foo)

**`src/CMakeLists.txt`:**

cmake_minimum_required (VERSION 3.5)
project (cmake_proto_test CXX)

find_package(Protobuf REQUIRED)

# proto files import from the source root directory, so add the required -I
flag
set(PROTOBUF_IMPORT_DIRS ${CMAKE_SOURCE_DIR})

# genererated proto files go into the CMake binary output dir
include_directories("${CMAKE_BINARY_DIR}")

add_subdirectory(foo)
add_subdirectory(bar)

##Build error:

When I try to build this, I get the following error:

$ make .. VERBOSE=1
cd src/cmake_proto/build/bar && /usr/bin/c++
-I src/cmake_proto/build   
-o CMakeFiles/lib_bar.dir/message.pb.cc.o 
-c src/cmake_proto/build/bar/message.pb.cc

In file included from src/cmake_proto/build/bar/message.pb.cc:5:0:

src/cmake_proto/build/bar/message.pb.h:99:24: 
error: ‘foo’ in namespace ‘test’ does not name a type

   inline const ::test::foo::FooMsg& f() const;
^

##Reason:

The error is due to the header guard created by `protoc` being the same for the
2 generated files:

#ifndef PROTOBUF_message_2eproto__INCLUDED
#define PROTOBUF_message_2eproto__INCLUDED

...

#endif

The reason is that the header guard is derived from a combination of the output
directory and the generated file's path.

The current command issued by `FindProtobuf.cmake` results in the header guard
only using the filename:

cd src/cmake_proto/build/foo && /usr/local/bin/protoc --cpp_out
src/cmake_proto/build/foo -I src/cmake_proto/foo -I src/cmake_proto
src/cmake_proto/foo/message.proto
cd src/cmake_proto/build/bar && /usr/local/bin/protoc --cpp_out
src/cmake_proto/build/bar -I src/cmake_proto/bar -I src/cmake_proto
src/cmake_proto/bar/message.proto

This command, however, will result in the files being generated in the same
location, but with a different header guard:

cd src/cmake_proto/build && /usr/local/bin/protoc --cpp_out
src/cmake_proto/build -I src/cmake_proto src/cmake_proto/foo/message.proto
cd src/cmake_proto/build && /usr/local/bin/protoc --cpp_out
src/cmake_proto/build -I src/cmake_proto src/cmake_proto/bar/message.proto

Header guards:

PROTOBUF_foo_2fmessage_2eproto__INCLUDED
PROTOBUF_bar_2fmessage_2eproto__INCLUDED

There are three key differences here:

- The `WORKING_DIRECTORY` from which `protoc` is run from is
`${CMAKE_BINARY_DIR}`
- The `--cpp_out` directory passed to `protoc` is `${CMAKE_BINARY_DIR}`
- The `-I` include path passed to `protoc` does **not** include the folder where
the proto file is found

Being able to control these 3 items would give the flexibility required to use
this tool in the above setup.


== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-22 17:09 skebanga   New Issue  

[cmake-developers] [CMake 0016076]: bin install directory configuration

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16076 
== 
Reported By:blackstar
Assigned To:
== 
Project:CMake
Issue ID:   16076
Category:   CMakeSetup
Reproducibility:always
Severity:   block
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-22 10:39 EDT
Last Modified:  2016-04-22 10:39 EDT
== 
Summary:bin install directory configuration
Description: 
It is impossible to set the CMake bin install directory with bootstrap options.
The bin install directory is always /bin.
If cmake binary is moved to other location, The CMAKE_ROOT could not be find,
because the unique search directory of /Modules/CMake.cmake file is at the same
level of bin directory.

CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in

So it is impossible to have in the same install directory, several CMake binary
of different OS.
For example :
   cmake-3.5.2/bin/centos6.2/cmake
   cmake-3.5.2/bin/ubuntu14.04/cmake

Is it possible to add an option in bootstrap, like --docdir, to set the binary
install directory relative to  ?

Steps to Reproduce: 
do a cmake installation
move the cmake binary
run cmake
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-22 10:39 blackstar  New Issue
==

-- 

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] [CMake 0016075]: Play jeopardy theme during compilation

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16075 
== 
Reported By:Richard Wiedenhöft
Assigned To:
== 
Project:CMake
Issue ID:   16075
Category:   CMake
Reproducibility:N/A
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-22 03:53 EDT
Last Modified:  2016-04-22 03:53 EDT
== 
Summary:Play jeopardy theme during compilation
Description: 
I'd like to request the addition of a command line flag that enables playback of
the Jeopardy theme while a compilation is running.

This should be trivially possible using mplayer (on Linux at least).

Reasons:
- It would be awesome
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-22 03:53 Richard WiedenhöftNew Issue   

==

-- 

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] [CMake 0016074]: Setting link_directories in toolchain file is only used for compiler tests, and inhibits effect of repeating the command

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16074 
== 
Reported By:Antonio
Assigned To:
== 
Project:CMake
Issue ID:   16074
Category:   (No Category)
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-21 09:58 EDT
Last Modified:  2016-04-21 09:58 EDT
== 
Summary:Setting link_directories in toolchain file is only
used for compiler tests, and inhibits effect of repeating the command
Description: 
In the attached example,
TOOLCHAIN FILE:
link_directories("D:/abcd")

CMAKELISTS.TXT:
project(dummyProject)
cmake_minimum_required(VERSION 3.4)
link_directories("D:/abcd")
link_directories("D:/efgh")
add_library(dummyTarget SHARED dummy.cpp)

At linking stage, only the "-LD:/efgh" will be there:
cmd.exe /C "cd . &&  -shared -o libdummyTarget.dll
-Wl,--out-implib,libdummyTarget.dll.a
-Wl,--major-image-version,0,--minor-image-version,0
CMakeFiles/dummyTarget.dir/dummy.cpp.obj -LD:/efgh -lkernel32 -luser32 -lgdi32
-lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."

Note: In the CMakeOutput.log file is possible to see that -LD:/abcd is used in
the preliminary compiler tests.

Use case:
I am dealing with a toolchain where the std library is in a specific location,
and to pass the preliminary cmake compiler tests I must set the std library
location with a link_directories command. Since it is toolchain specific, it
makes sense to set in the toolchain file. I can pass the compiler tests if I
call `link_directories` in the toolchain file.

The only workaround I could find so far was to directly set the flag (still in
the toolchain file):

# SET(CMAKE_EXE_LINKER_FLAGS "-LD:/abcd")
# SET(CMAKE_SHARED_LINKER_FLAGS "-LD:/abcd")
# SET(CMAKE_MODULE_LINKER_FLAGS "-LD:/abcd")

Steps to Reproduce: 
1) Take the project in attachment
2) Configure with the attached toolchain, for example using ninja generator
3a) With ninja, run ninja -v to see the command line
3b) With make, run make.exe VERBOSE=1 to see the command line
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-21 09:58 AntonioNew Issue
2016-04-21 09:58 AntonioFile Added: CMakeBugProject.zip 
  
==

-- 

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] [CMake 0016073]: InstallRequiredSystemLibraries needs updating for MSVS2015

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16073 
== 
Reported By:Lewoco
Assigned To:
== 
Project:CMake
Issue ID:   16073
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-21 03:38 EDT
Last Modified:  2016-04-21 03:38 EDT
== 
Summary:InstallRequiredSystemLibraries needs updating for
MSVS2015
Description: 
Many system DLL's required by MSVS2015 are not identified by
InstallRequiredSystemLibraries.


Steps to Reproduce: 
- add_executable a simple hello world
- Use InstallRequiredSystemLibraries to install the required libraries
- Build an installer using WiX (or whatever)
- Install it on Windows 7 (no updates)

BUG: executable cannot be run because of missing DLL's.

Note:
- Updates might have helped but I didn't try it.
- Probably also affects Windows 8/8.1.
- Might not affect Windows 10? (see link)

https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/


Additional Information: 
Right now I'm using the following code to select the additional required
libraries. Please integrate something similar into
InstallRequiredSystemLibraries:

# InstallRequiredSystemLibraries does not properly support MSVS 14 yet, so do it
manually.
unset(CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_DEBUG)
unset(CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_RELEASE)
if(DEFINED MSVC_VERSION AND NOT MSVC_VERSION LESS 1900)
# Internal: Architecture-appropriate library directory names.
if("${CMAKE_VS_PLATFORM_NAME}" STREQUAL "ARM")
set(_winsdk_arch8 arm) # what the WDK for Win8+ calls this architecture
else()
if(CMAKE_SIZEOF_VOID_P MATCHES "8")
set(_winsdk_arch8 x64) # what the WDK for Win8+ calls this
architecture
else()
set(_winsdk_arch8 x86) # what the WDK for Win8+ calls this
architecture
endif()
endif()

# The CRT is distributed with MSVS.
get_filename_component(MSVS_DIR
   
"[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\14.0;ShellFolder]"
ABSOLUTE)

# As of MSVC 19 the CRT depends on the 'univeral' CRT (which is part of
Windows development kit 10 and above).
#
http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx
get_filename_component(WINDOWS_KIT_DIR
"[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Kits\\Installed
Roots;KitsRoot10]" ABSOLUTE)

file(GLOB CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_DEBUG
   
"${MSVS_DIR}/VC/redist/debug_nonredist/${_winsdk_arch8}/Microsoft.VC140.DebugCRT/*.dll"
"${WINDOWS_KIT_DIR}/Redist/ucrt/DLLs/${_winsdk_arch8}/api-ms-win-*.dll"
"${WINDOWS_KIT_DIR}/bin/${_winsdk_arch8}/ucrt/*.dll"
)
file(GLOB CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_RELEASE
"${MSVS_DIR}/VC/redist/${_winsdk_arch8}/Microsoft.VC140.CRT/*.dll"
"${WINDOWS_KIT_DIR}/Redist/ucrt/DLLs/${_winsdk_arch8}/*.dll"
)
endif()

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-21 03:38 Lewoco New Issue
==

-- 

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] [CMake 0016072]: flex macro can't handle parenthesis in path

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=16072 
== 
Reported By:Raymond Langer
Assigned To:
== 
Project:CMake
Issue ID:   16072
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-20 12:43 EDT
Last Modified:  2016-04-20 12:43 EDT
== 
Summary:flex macro can't handle parenthesis in path
Description: 
The FLEX_TARGET macro doesn't escape parenthesis in the output argument for
flex.

Steps to Reproduce: 
In a project that uses flex I used the build directory 'Build 123()'.

Additional Information: 
Maybe it's possible to use double quotes.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-20 12:43 Raymond Langer New Issue
==

-- 

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] [CMake 0016071]: CMake should map /Fd to COMPILE_PDB_NAME for static libraries

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16071 
== 
Reported By:Itai Seggev
Assigned To:
== 
Project:CMake
Issue ID:   16071
Category:   CMake
Reproducibility:always
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-19 13:02 EDT
Last Modified:  2016-04-19 13:02 EDT
== 
Summary:CMake should map /Fd to COMPILE_PDB_NAME for static
libraries
Description: 
This is a follow up to https://cmake.org/Bug/view.php?id=14763 and its
predecessors https://cmake.org/Bug/view.php?id=14060 /
https://cmake.org/Bug/view.php?id=14062

/Fd was separated from PDB_NAME, because normally what we want is the linker
pdb.  However, if our final product is the static library, then we do want to
the compiler PDB file, so COMPILE_PDB_NAME was added.  Yet, a mapping was not
added between COMPILE_PDB_NAME and /Fd.  The result is /Fd is added to compile
flags but COMPILE_PDB_NAME remains at its default value, and an inconsistency is
created between Visual Studio and NMake generators.  For the former, the flag is
honored, but for the latter it is overridden by the NMake file's own
specification of /Fd.  Thus, for dlls and exes, you can simply add /PDB to the
link flags, but for static libraries you must manually manipulate the
COMPILE_PDB_NAME property for the target.  I think that /Fd, certainly for
static libraries which have no link step, should be mapped to COMPILE_PDB_NAME.

Steps to Reproduce: 
Create a minimal CMakeLists.txt like the following:

project(foo)
add_library(myLib STATIC myLib.c)
target_compile_options(myLib PUBLIC $<$:/Zi /FdmyLib.pdb>)

Generate a NMake Makefiles build system and build.  You will see

cl : Command line warning D9025 : overriding '/FdmyLib.pdb' with
'/FdCMakeFiles\myLib.dir/' 

and the PDB file is indeed CMakeFiles\myLib.dir\vc120.pdb.  If you generate a
Visual Studio project and build, there is no warning and the pdb file is
.\myLib.pdb.

And indeed the pdb file will be 
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-19 13:02 Itai SeggevNew Issue
==

-- 

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] [CMake 0016070]: Malformed newline sequences from externally executed processes

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=16070 
== 
Reported By:Nils Gladitz
Assigned To:
== 
Project:CMake
Issue ID:   16070
Category:   (No Category)
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-17 17:52 EDT
Last Modified:  2016-04-17 17:52 EDT
== 
Summary:Malformed newline sequences from externally executed
processes
Description: 
When running ctest in script mode verbosely e.g. the executed build command
produces "\r\n" newlines. When ctest forwards that output to stdout/stderr these
"\r\n" newlines turn into "\r\r\n".

The same happens when using execute_process() without the OUTPUT_/ERROR_
options.

When using the OUTPUT_/ERROR_ VARIABLE/FILE options "\r" newlines are explicitly
stripped resulting in correct/expected output.

While the windows console and e.g. notepad interpret these "\r\r\n" newline
sequences as a single newline other tools (e.g. buildbot) interpret such a
sequence as two newlines.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-17 17:52 Nils Gladitz   New Issue
==

-- 

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] [CMake 0016069]: Behaviour does not match documentation for policy CMP0048

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16069 
== 
Reported By:Craig Scott
Assigned To:
== 
Project:CMake
Issue ID:   16069
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-16 17:49 AEST
Last Modified:  2016-04-16 17:49 AEST
== 
Summary:Behaviour does not match documentation for policy
CMP0048
Description: 
The policy documentation for CMP0048 says this:

"This policy was introduced in CMake version 3.0. CMake version 3.5.2 warns when
the policy is not set and uses OLD behavior. Use the cmake_policy command to set
it to OLD or NEW explicitly."

In my testing, however, no such warning is issued and the default appears to be
NEW, not OLD.

Steps to Reproduce: 
The following minimal CMakeLists.txt demonstrates the problem:

cmake_minimum_required(VERSION 3.5.2)
cmake_policy(GET CMP0048 isOn)
message("isOn = ${isOn}")
project(proj VERSION 1.2.3)

Changing the minimum required version doesn't seem to make any difference.

Additional Information: 
If you explicitly set the policy for CMP0048 to OLD, then the expected error
does occur when the project() command includes a VERSION specification.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-16 17:49 Craig ScottNew Issue
==

-- 

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] [CMake 0016068]: qt5 autorcc uses wrong output folder

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16068 
== 
Reported By:Martin Haaß
Assigned To:
== 
Project:CMake
Issue ID:   16068
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-15 10:56 EDT
Last Modified:  2016-04-15 10:56 EDT
== 
Summary:qt5 autorcc uses wrong output folder
Description: 
The file qrc_Editor.cpp generated by the qt5 rcc compile step from Editor.qrc is
put into CMAKE_BINARY_DIR/CMakeFiles/${target}.dir
where it cannot be found/referenced.
Files generated by automoc and autoui are put in CMAKE_BINARY_DIR, where they
can be found. 
Inside CMAKE_BINARY_DIR/CMakeFiles/${target}.dir there is another folder
${target}.dir/CMakeFiles/${target}.dir which contains qrc_Editor.cpp.o.
To me it looks like cmake start the rcc step with the wrong folder
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-15 10:56 Martin HaaßNew Issue
==

-- 

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] [CMake 0016067]: $<TARGET_POLICY:*> generator expression evaluates to NEW instead of 1

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16067 
== 
Reported By:Johannes S. Mueller-Roemer
Assigned To:
== 
Project:CMake
Issue ID:   16067
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-15 10:20 EDT
Last Modified:  2016-04-15 10:20 EDT
== 
Summary:$ generator expression evaluates to
NEW instead of 1
Description: 
When the $ generator expression is used, it should evaluate to
1 if the given policy is new and 0 if it is old, as documented here:
https://cmake.org/cmake/help/v3.5/manual/cmake-generator-expressions.7.html

However, with the current version of CMake it evaluates to NEW in the true case.
I did not test the false case, which probably evaluates to OLD.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-15 10:20 Johannes S. Mueller-RoemerNew Issue
   
==

-- 

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] [CMake 0016066]: Compilation error on ./bootstrap

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16066 
== 
Reported By:alexfc
Assigned To:
== 
Project:CMake
Issue ID:   16066
Category:   CMakeSetup
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-15 09:45 EDT
Last Modified:  2016-04-15 09:45 EDT
== 
Summary:Compilation error on ./bootstrap
Description: 
While compiling file cmake-3.5.1/Source/cmPolicies.cxx when launching
./bootstrap.error is :
isdigit not declared in this scope

Steps to Reproduce: 
Download and extract cmake-3.5.1
cd cmake-3.5.1
./boostrap

Additional Information: 
Compilation successful when adding 
#include 
in the file cmake-3.5.1/Source/cmPolicies.cxx
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-15 09:45 alexfc New Issue
==

-- 

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] [CMake 0016065]: Building CUDA files fails when compile definitions contains parenthesis

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16065 
== 
Reported By:Guillaume Dumont
Assigned To:
== 
Project:CMake
Issue ID:   16065
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-14 19:57 EDT
Last Modified:  2016-04-14 19:57 EDT
== 
Summary:Building CUDA files fails when compile definitions
contains parenthesis
Description: 
When calling cuda_wrap_srcs with the OPTIONS argument or when adding compile
definitions via add_definitions the build fails when the definitions contain
parentheses. For example,

add_definitions("-DFOO_BAR_EXPORT=declspec\(dllimport\)")

generates:

set(nvcc_flags -DFOO_BAR_EXPORT=declspec(dllimport))

which makes the build fail. When the parentheses are escaped like so:

add_definitions("-DFOO_BAR_EXPORT=declspec\\\(dllimport\\\)")

we get:

set(nvcc_flags -DFOO_BAR_EXPORT=declspec\(dllimport\))

and everything is fine.

This is similar to issue: https://cmake.org/Bug/view.php?id=15919

Maybe a similar fix can be applied?
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-14 19:57 Guillaume DumontNew Issue
==

-- 

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] [CMake 0016064]: Missing /usr/local/bin causes --install script to fail.

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16064 
== 
Reported By:Ho Cheung
Assigned To:
== 
Project:CMake
Issue ID:   16064
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-14 12:45 EDT
Last Modified:  2016-04-14 12:45 EDT
== 
Summary:Missing /usr/local/bin causes --install script to
fail.
Description: 
On a clean install of OSX 10.11.4, I discovered the install script fails to
create the symlinks:

Work-iMac:~ hocheung20$ sudo "/Applications/CMake.app/Contents/bin/cmake-gui"
--install
Failed: '/usr/local/bin/cmake' -> '/Applications/CMake.app/Contents/bin/cmake':
No such file or directory

This is because in a clean install of OSX, only /usr/local exists. When I mkdir
/usr/local/bin, the script succeeds.

Steps to Reproduce: 
Clean install OSX.
Copy CMake app to /Applications
sudo "/Applications/CMake.app/Contents/bin/cmake-gui" --install
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-14 12:45 Ho Cheung  New Issue
==

-- 

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] [CMake 0016063]: Wrong protobuf search logic

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=16063 
== 
Reported By:xseven
Assigned To:
== 
Project:CMake
Issue ID:   16063
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-14 04:40 EDT
Last Modified:  2016-04-14 04:40 EDT
== 
Summary:Wrong protobuf search logic
Description: 
I faced a problem with using find_package(Protobuf).

I'm using protobuf-3.0.0-beta-2

I built it and installed via MSVC 2015 but module looks for 
${PROTOBUF_SRC_ROOT_FOLDER}/vsprojects/${_PROTOBUF_ARCH_DIR}Debug)and Release
which seem missing in contemporary MSVC build anymore

Could be more reasonable to use PROTOBUF_SRC_ROOT_FOLDER as a path to installed
protobuf files after build?

Steps to Reproduce: 
Build protobuf-3.0.0-beta-2
Set PROTOBUF_SRC_ROOT_FOLDER run CMake 3.5.1
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-14 04:40 xseven New Issue
==

-- 

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] [CMake 0016062]: Policy CMP0037 should only warn about "test" and "package" being reserved if CTest and CPack are being used

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16062 
== 
Reported By:Ben Boeckel
Assigned To:
== 
Project:CMake
Issue ID:   16062
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-13 15:37 EDT
Last Modified:  2016-04-13 15:37 EDT
== 
Summary:Policy CMP0037 should only warn about "test" and
"package" being reserved if CTest and CPack are being used
Description: 
Common complaint among those not using CTest for testing, but want "make test"
to use their test running infrastructure.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-13 15:37 Ben BoeckelNew Issue
==

-- 

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] [CMake 0016061]: define SOLARIS and CMAKE_HOST_SOLARIS as a cmake built-in

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16061 
== 
Reported By:Stefan Teleman
Assigned To:
== 
Project:CMake
Issue ID:   16061
Category:   CMake
Reproducibility:always
Severity:   trivial
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-13 11:02 EDT
Last Modified:  2016-04-13 11:02 EDT
== 
Summary:define SOLARIS and CMAKE_HOST_SOLARIS as a cmake
built-in
Description: 
in ${top_srcdir}/Source/cmState.cxx:

void cmState::Snapshot::SetDefaultDefinitions()

several builtins are defined: WIN32/CMAKE_HOST_WIN32, APPLE/CMAKE_HOST_APPLE,
etc.

We would like to submit this patch to add corresponding definitions
for Solaris: SOLARIS/CMAKE_HOST_SOLARIS

Proposed patch - cmState.cxx-solaris.patch - attached.

The patch is based on cmake 3.5.0.


Steps to Reproduce: 
Always - the SOLARIS/CMAKE_HOST_SOLARIS definition is not present
in cmake.

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-13 11:02 Stefan Teleman New Issue
2016-04-13 11:02 Stefan Teleman File Added: cmState.cxx-solaris.patch   

==

-- 

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] [CMake 0016060]: Chrome warns cmake installer is harmful program

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16060 
== 
Reported By:raysatiro
Assigned To:
== 
Project:CMake
Issue ID:   16060
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-12 17:52 EDT
Last Modified:  2016-04-12 17:52 EDT
== 
Summary:Chrome warns cmake installer is harmful program
Description: 
Using Chrome Version 49.0.2623.112 m I'm trying to download the cmake installer:

"The site ahead contains harmful programs

Attackers on cmake.org might attempt to trick you into installing programs that
harm your browsing experience (for example, by changing your homepage or showing
extra ads on sites you visit)."



Steps to Reproduce: 
https://cmake.org/download/ and click on cmake-3.5.1-win32-x86.msi

Additional Information: 
https://www.google.com/transparencyreport/safebrowsing/diagnostic/index.html?hl=en-US#url=https://cmake.org/files/v3.5/cmake-3.5.1-win32-x86.msi
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-12 17:52 raysatiro  New Issue
2016-04-12 17:52 raysatiro  File Added: cmake chrome says harmful
programs.PNG
==

-- 

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] [CMake 0016059]: It is not possible to specify a linker different from the compiler to link a shared library

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16059 
== 
Reported By:Antonio
Assigned To:
== 
Project:CMake
Issue ID:   16059
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-12 12:00 EDT
Last Modified:  2016-04-12 12:00 EDT
== 
Summary:It is not possible to specify a linker different
from the compiler to link a shared library
Description: 
In some situations, it might be convenient to specify a different linker than
the compiler. For example, for llvm combined with mingw, compiling with clang
and linking with gcc would work. The workaround proposed here
https://cmake.org/pipermail/cmake/2014-August/058268.html does not seem to work.

Steps to Reproduce: 
Requires 2 compilers to be there. In the attached project,
Configuring with 
D:\dummyProj\build> cmake ..\src -G "Eclipse CDT4 - Ninja"
-DCMAKE_TOOLCHAIN_FILE=..\src\Toolchain-LLVM.cmake 
-DCMAKE_LINKER=C:/Programs/mingw32_493_posix_dwarf/bin/g++.exe
-DCMAKE_CXX_LINK_EXECUTABLE="  
  -o  " 
-DCMAKE_CXX_CREATE_SHARED_LIBRARY="
  
  -o 
 "

Building will anyway lead to the following commands to be generated:
[1/2] C:\Programs\LLVM\bin\clang++.exe   -Ddummy_EXPORTS   -MMD -MT
CMakeFiles/dummy.dir/dummy.cpp.obj -MF CMakeFiles/dummy.dir/dummy.cpp.obj.d -o
CMakeFiles/dummy.dir/dummy.cpp.obj -c D:/dummyProj/src/dummy.cpp
[2/2] cmd.exe /C "cd . && C:\Programs\LLVM\bin\clang++.exe  -shared -o
libdummy.dll -Wl,--out-implib,libdummy.dll.a
-Wl,--major-image-version,0,--minor-image-version,0
CMakeFiles/dummy.dir/dummy.cpp.obj  -lkernel32 -luser32 -lgdi32 -lwinspool
-lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."
FAILED: cmd.exe /C "cd . && C:\Programs\LLVM\bin\clang++.exe  -shared -o
libdummy.dll -Wl,--out-implib,libdummy.dll.a
-Wl,--major-image-version,0,--minor-image-version,0
CMakeFiles/dummy.dir/dummy.cpp.obj  -lkernel32 -luser32 -lgdi32 -lwinspool
-lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."
C:\Programs\mingw32_493_posix_dwarf\i686-w64-mingw32\lib/libmingw32.a(lib32_libmingw32_a-pseudo-reloc.o):pseudo-reloc.c:(.text+0x1d6):
undefined reference to `__chkstk_ms'

clang++.exe: error: linker command failed with exit code 1 (use -v to see
invocation)

ninja: build stopped: subcommand failed.

The first command is correct, the second doesn't use g++ to link as desired.
Linking succeeds if g++ is replaced in the command line.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-12 12:00 AntonioNew Issue
2016-04-12 12:00 AntonioFile Added: dummyProj.zip
==

-- 

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] [CMake 0016058]: ImageMagick found from Command line but not from CMake GUI

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16058 
== 
Reported By:Alex Ferrier
Assigned To:
== 
Project:CMake
Issue ID:   16058
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-11 15:24 EDT
Last Modified:  2016-04-11 15:24 EDT
== 
Summary:ImageMagick found from Command line but not from
CMake GUI
Description: 
I am trying to configure the project Theia-SfM to compile with XCode on a Mac.

https://github.com/sweeneychris/TheiaSfM

Using CMake 3.5.1 installed via Macports via XCode the package configures and
builds fine once the appropriate dependencies are installed, e.g.

mkdir Build
cmake -G XCode ..

-- Generating done
-- Build files have been written to: /Users/alex/src/TheiaSfM/build
If using CMake GUI 3.5.1 downloaded from KitWare, and installed via
applications, the same build fails to find ImageMagick. Output ends:

-- Found SuiteSparse 4.2.1
-- Check for ImageMagick
ImageMagick_EXECUTABLE_DIRImageMagick_EXECUTABLE_DIR-NOTFOUND
CMake Error at
/Applications/CMake.app/Contents/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
  Could NOT find ImageMagick (missing: ImageMagick_convert_EXECUTABLE
  ImageMagick_mogrify_EXECUTABLE ImageMagick_convert_EXECUTABLE
  ImageMagick_mogrify_EXECUTABLE)
ImageMagick is demonstrably installed (via macports) in /opt/local/bin.

Alexs-MacBook-Pro:TheiaSfM alex$ type -a mogrify
mogrify is /opt/local/bin/mogrify
Is there any obvious reason why identical versions of CMake would fail to find
the same package? I'm assuming /opt/local is in my CMake GUI paths search paths,
because further up it finds other dependencies there.

-- Found Google Flags: /opt/local/include in namespace: google
-- Check for Google Log
-- Found Google Logging: /opt/local/include
-- Check for Ceres

Steps to Reproduce: 
See description, download package and configure with command line (successful)
and GUI (unsuccessful.) Presumably reproducible with other builds using
imagemagick? 
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-11 15:24 Alex Ferrier   New Issue
==

-- 

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] [CMake 0016057]: FindBoost: No imported target when components not specified

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16057 
== 
Reported By:Tatsuyuki Ishi
Assigned To:
== 
Project:CMake
Issue ID:   16057
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-09 09:58 EDT
Last Modified:  2016-04-09 09:58 EDT
== 
Summary:FindBoost: No imported target when components not
specified
Description: 
Here's an example:
=
project(...)
find_package(Boost REQUIRED)
add_executable(...)
target_link_libraries(... Boost::Boost)
*BOOM*
=

But this works:
=
find_package(Boost COMPONENTS system REQUIRED)
target_link_libraries(... Boost::Boost)
=

This is hard to use, and should be considered as bug and fixed.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-09 09:58 Tatsuyuki Ishi New Issue
==

-- 

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] [CMake 0016056]: file(GENERATE) not processing variables from INPUT file

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16056 
== 
Reported By:johnnyzz
Assigned To:
== 
Project:CMake
Issue ID:   16056
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-08 19:18 CEST
Last Modified:  2016-04-08 19:18 CEST
== 
Summary:file(GENERATE) not processing variables from INPUT
file
Description: 
There is a bug when generating a file with:

file(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/output1.txt" 
  INPUT ${CMAKE_SOURCE_DIR}/input.txt
)

file(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/output2.txt" 
  CONTENT "SOURCE DIR = '${CMAKE_SOURCE_DIR}'"
)

- Using "INPUT filename", variables are not processed, but "CONTENT text" with
the same content works properly

Steps to Reproduce: 
1) cmake .
2) cat output1.txt
3) cat output2.txt

-> The variable in output1.txt is not replaced by its value
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-08 19:18 johnnyzz   New Issue
2016-04-08 19:18 johnnyzz   File Added: CMakeLists.txt
==

-- 

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] [CMake 0016055]: "nmake" program is not found using MAKE environment variable

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16055 
== 
Reported By:Daniel Richard G.
Assigned To:
== 
Project:CMake
Issue ID:   16055
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-07 16:58 EDT
Last Modified:  2016-04-07 16:58 EDT
== 
Summary:"nmake" program is not found using MAKE environment
variable
Description: 
If you set MAKE=C:\path\to\nmake.exe in your environment, but nmake is not in
your PATH, then the NMake generator will fail.

Looking for nmake in the current PATH is reasonable, but if MAKE is defined,
then that should be used instead.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-07 16:58 Daniel Richard G.New Issue
==

-- 

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] [CMake 0016054]: Cannot override CMAKE_{C, CXX}_FLAGS* to allow compiler check to succeed

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16054 
== 
Reported By:Daniel Richard G.
Assigned To:
== 
Project:CMake
Issue ID:   16054
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-07 16:53 EDT
Last Modified:  2016-04-07 16:53 EDT
== 
Summary:Cannot override CMAKE_{C,CXX}_FLAGS* to allow
compiler check to succeed
Description: 
I am attempting to build a project on a Windows system.

The development tools on this system are set up a little differently from the
norm: Because my company always builds against the static C runtime library
(i.e. using the /MT flag), the dynamic C runtime (/MD) stub library is not
present at all. Any attempt to link an executable/DLL that was built with /MD
will fail.

Now, CMake ships with /MD or /MDd in the default flags. I set my desired flags
(including /MT) in CFLAGS/CXXFLAGS in the environment, start up cmake-gui, and
hit "Configure".

"Error in configuration process, project files may be invalid"

The log window shows

CMake Error at C:/.../Modules/CMakeTestCCompiler.cmake:61 (message):
  The C compiler "C:/.../icl.exe" is
  not able to compile a simple test program.

Lower down, after the compiler invocation, I see

icl: command line warning https://public.kitware.com/Bug/view.php?id=10121:
overriding '/MT' with '/MDd'

CMake's flags are concatenated to my own, and /MDd wins out. Thus the linker
fails to link the program, due to that missing stub library, and CMake reports
the compiler as non-functional.

Okay, so I edit the CMAKE_{C,CXX}_FLAGS* variables to remove all the /MD and
/MDd flags. Then I configure again. Same error. It's _still_ passing /MDd to the
compiler!

At this point, I don't know where that flag is coming from. I grep through the
nascent build tree to see if there are any instances of it still kicking around;
the only hit is in CMakeError.log. I double-check that the project source isn't
at fault: nope, the flag is nowhere to be found there either.

Turns out, the place where that flag is coming from is CMake's own
Modules/Platform/Windows-MSVC.cmake file. If I edit the _INIT variable in there
(e.g. add /Dhi_mom), then I see the result reflected in the compiler test.

The bug, then, is that I have no good way of overriding those flag variables in
order to allow the compiler check to succeed. (Note that
CMAKE_USER_MAKE_RULES_OVERRIDE is not applicable here, because I want to
override those flags as a user, not modify the project to get the same effect.)

Perhaps the edited variables are used later on, when building the project, but
they are certainly not used when checking the compiler. I believe this bug has
gone unnoticed for so long due to this specific scenario (missing dynamic CRT
stub library) being uncommon.

Note that this issue is reproducible with a trivial CMake project---I used one
as described at cmake.org/examples---so the original project that exhibited this
bug is not at issue.

Additional Information: 
Because I need to use my company's exact compiler/linker flags, and will be
given grief by my release-engineering group if I use anything else, it would be
nice to be able to set some environment variable or the like that will tell
CMake not to "help" with any default flags.

While I can always edit the Windows-MSVC.cmake file, that then imposes the
ongoing burden of maintaining that file, merging in upstream changes, etc. My
goal is to just set CFLAGS/LDFLAGS/etc. in the environment and have the tools
work with that, as is the case in Unix. (Setting a CMAKE_NO_DEFAULT_FLAGS
variable or the like would be a reasonable solution.)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-07 16:53 Daniel Richard G.New Issue
==

-- 

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 

[cmake-developers] [CMake 0016053]: $ should return a short path on Windows when containing spaces

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16053 
== 
Reported By:Guillaume Dumont
Assigned To:
== 
Project:CMake
Issue ID:   16053
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-07 11:26 EDT
Last Modified:  2016-04-07 11:26 EDT
== 
Summary:$ should return a short path on
Windows when containing spaces
Description: 
I am trying to build OpenCV from sources using MSVC and the Ninja Generator and
I have a failing build because of linker flags added to the
target_link_libraries. OpenCV's CMakeLists.txt uses this line of CMake code:

set(OPENCV_LINKER_LIBS ${OPENCV_LINKER_LIBS} -L${p})

OPENCV_LINKER_LIBS is passed to target_link_libraries afterwards. The problem
with this line is that it does not work on Windows with the Ninja generator. I
tried:

set(OPENCV_LINKER_LIBS ${OPENCV_LINKER_LIBS}
${CMAKE_LIBRARY_PATH_FLAG}$)

but that does not work either because the even though we end up using /LIBPATH:
instead of /L and backslashes instead of forward slashes the path contains
spaces and ninja throws a link error. 

Shouldn't SHELL_PATH return a short path, or a path between quotes when the path
contains spaces on Windows?


Steps to Reproduce: 
Try to build OpenCV 3.1.0 on Windows with Ninja.

Additional Information: 
See OpenCV issue: https://github.com/Itseez/opencv/issues/6372
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-07 11:26 Guillaume DumontNew Issue
==

-- 

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] [CMake 0016052]: Extra space on NDEBUG in release builds causes flag to be ignored

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://kwwidgets.org/Bug/view.php?id=16052 
== 
Reported By:Stephen Dunn
Assigned To:
== 
Project:CMake
Issue ID:   16052
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-07 10:36 EDT
Last Modified:  2016-04-07 10:36 EDT
== 
Summary:Extra space on NDEBUG in release builds causes flag
to be ignored
Description: 
This bug was previously reported, but incorrectly marked as resolved here:
http://kwwidgets.org/Bug/view.php?id=1749

All Release mode configs accidentally append a space after /D in Visual Studio
2015 (14) which causes the flag NDEBUG to be ignored. It should be: /DNDEBUG,
not /D NDEBUG which is invalid syntax. Other /D flags are defined correctly.

I check for the presence of this var, and its absence in Release mode causes
undefined behavior.

Steps to Reproduce: 
Generate any project with Release mode builds.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-07 10:36 Stephen Dunn   New Issue
2016-04-07 10:36 Stephen Dunn   File Added: cmake-bug.png
==

-- 

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] [CMake 0016051]: Incorrect archive generated with CPACK_ARCHIVE_COMPONENT_INSTALL=ON with non-empty directory behind a symlink

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16051 
== 
Reported By:benoit.barbier
Assigned To:
== 
Project:CMake
Issue ID:   16051
Category:   CPack
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2016-04-06 09:46 EDT
Last Modified:  2016-04-06 09:46 EDT
== 
Summary:Incorrect archive generated with
CPACK_ARCHIVE_COMPONENT_INSTALL=ON with non-empty directory behind a symlink
Description: 
cmake_minimum_required(VERSION 3.0.0)

# generate files & folders
make_directory(${CMAKE_CURRENT_BINARY_DIR}/sample)
FILE(WRITE ${CMAKE_CURRENT_BINARY_DIR}/sample/dummy.txt "")
execute_process(
COMMAND mkdir folder
COMMAND ln -s folder alias
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/sample)

FILE(WRITE ${CMAKE_CURRENT_BINARY_DIR}/sample/folder/file.txt "")

# install 2 different components
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/sample/dummy.txt DESTINATION "."
COMPONENT cmp1)

install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/sample/alias DESTINATION "."
COMPONENT cmp2)
install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/sample/folder DESTINATION "."
COMPONENT cmp2)

set(CPACK_ARCHIVE_COMPONENT_INSTALL ON)

include(cpack)

===

Run cmake, then cpack -G TGZ or ZIP. Open the archive of the second component
(cmp2), and you get an error:

 >> unzip Project-0.1.1-Darwin-cmp2.zip 
"
Archive:  Project-0.1.1-Darwin-cmp2.zip
linking: alias   -> folder 
checkdir error:  alias exists but is not directory
 unable to process alias/dummy.txt.
   creating: folder/
  inflating: folder/dummy.txt
finishing deferred symbolic links:
  alias  -> folder
"
===

This append only if you specify CPACK_ARCHIVE_COMPONENT_INSTALL= ON and there is
a file created into the folder (folder/file.txt). If the folder is empty, no
error are generated by the unzip.

Seems to be appear when this feature have been introduced in CPack (cmake 3.4
release notes) :
The CPack module learned to package empty directories.

Often append if you package a bundle with frameworks...
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-06 09:46 benoit.barbier New Issue
==

-- 

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] [CMake 0016050]: Missing source files generate broken Makefiles (NMake)

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16050 
== 
Reported By:Lluís Batlle
Assigned To:
== 
Project:CMake
Issue ID:   16050
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-06 03:41 EDT
Last Modified:  2016-04-06 03:41 EDT
== 
Summary:Missing source files generate broken Makefiles
(NMake)
Description: 
Using the "NMake Makefiles" and "NMake Makefiles JOM" generate broken makefiles,
in case that one source file of ADD_EXECUTABLE is missing.



Steps to Reproduce: 
In my case, I have something like:

ADD_EXECUTABLE(program WIN32 src1.cpp src1.hpp help.h)
TARGET_LINK_LIBRARIES(program lib1 lib2)

Running "cmake -G 'NMake Makefiles'" (or JOM) it reports properly:
CMake Error at CMakeLists.txt:57 (ADD_EXECUTABLE):
  Cannot find source file:

F:/projects/prog/build/help.h

But then I can type "nmake program", and it goes on building lib1 and lib2, and
then it tries to link program with the libs without any object files. It does
not compile any "program" source files. Of course the linker reports missing
_WinMainCRTStartup.



Additional Information: 
If I use the ninja generator, it works fine. When trying to run "ninja program",
it tries to run cmake again, and it fails because of the missing source file.

NMake should also do the same: run cmake again, to see if the CMakeLists.txt has
been fixed and all sources are found.

I had missed the "CMake Error" line when using NMake, and I spent time trying to
find out the sudden miss of the _WinMainCRTStartup symbol.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-06 03:41 Lluís Batlle   New Issue
==

-- 

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] [CMake 0016049]: Resources generated with autorcc are always rebuilt using ninja

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16049 
== 
Reported By:Vidar Meland Ødegård
Assigned To:
== 
Project:CMake
Issue ID:   16049
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   high
Status: new
== 
Date Submitted: 2016-04-05 14:49 EDT
Last Modified:  2016-04-05 14:49 EDT
== 
Summary:Resources generated with autorcc are always rebuilt
using ninja
Description: 
By using ninja and autorcc the resources are always rebuilt on CMake >= 3.5.
CMake 3.4.3 does not have this issue.

Steps to Reproduce: 
cmake  -GNinja
ninja -v
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-05 14:49 Vidar Meland ØdegårdNew Issue
   
2016-04-05 14:49 Vidar Meland ØdegårdFile Added: bug.tar.gz   
   
==

-- 

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] [CMake 0016048]: Segfault on target_link_libraries() with aliased target from another subdirectory

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16048 
== 
Reported By:arlbranch
Assigned To:
== 
Project:CMake
Issue ID:   16048
Category:   CMake
Reproducibility:always
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-04-01 15:22 EDT
Last Modified:  2016-04-01 15:22 EDT
== 
Summary:Segfault on target_link_libraries() with aliased
target from another subdirectory
Description: 
CMake crashes with a segfault when target_link_libraries is used to add a
dependency on an alias of a target that was added in a different subdirectory.

Complete Example

[branch@fortuna on /dev/pts/1] 1150 ~/repositories/test/cmake_segfault
$ cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).
[branch@fortuna on /dev/pts/1] 1151 ~/repositories/test/cmake_segfault
$ ls -lR
.:
total 12
drwxr-xr-x 2 branch atlsdd 4096 Apr  1 13:37 alib/
drwxr-xr-x 2 branch atlsdd 4096 Apr  1 14:14 blib/
-rw-r--r-- 1 branch atlsdd   98 Apr  1 13:18 CMakeLists.txt

./alib:
total 4
-rw-r--r-- 1 branch atlsdd 87 Apr  1 13:24 CMakeLists.txt

./blib:
total 4
-rw-r--r-- 1 branch atlsdd 162 Apr  1 13:38 CMakeLists.txt
[branch@fortuna on /dev/pts/1] 1152 ~/repositories/test/cmake_segfault
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8.11)
project(top)
add_subdirectory(alib)
add_subdirectory(blib)
[branch@fortuna on /dev/pts/1] 1153 ~/repositories/test/cmake_segfault
$ cat alib/CMakeLists.txt
add_library(alib alib.c)
set_source_files_properties(alib.c PROPERTIES GENERATED TRUE)
[branch@fortuna on /dev/pts/1] 1154 ~/repositories/test/cmake_segfault
$ cat blib/CMakeLists.txt
add_library(blib blib.c)
set_source_files_properties(blib.c PROPERTIES GENERATED TRUE)

add_library(alib::alib ALIAS alib)
target_link_libraries(blib alib::alib)
[branch@fortuna on /dev/pts/1] 1155 ~/repositories/test/cmake_segfault
$ mkdir build && cd build
[branch@fortuna on /dev/pts/1] 1156 ~/repositories/test/cmake_segfault/build
$ cmake ..
-- The C compiler identification is GNU 5.3.0
-- The CXX compiler identification is GNU 5.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Segmentation fault (core dumped)


Steps to Reproduce: 
1) create the project in the Description
2) run cmake against it

Additional Information: 
Also seen on MacOS.

This is a regression, cmake 3.4 does not crash.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 15:22 arlbranch  New Issue
==

-- 

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] [CMake 0016047]: automoc generates wrong #includes for projects in a symlinked path

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16047 
== 
Reported By:Maurizio Paolini
Assigned To:
== 
Project:CMake
Issue ID:   16047
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-01 13:36 EDT
Last Modified:  2016-04-01 13:36 EDT
== 
Summary:automoc generates wrong #includes for projects in a
symlinked path
Description: 
project "kig" uses cmake and automoc.
My local copy of the git sources are located in a folder that I reach following
a symlink
(it resides in a local partition whereas my home is on an NFS-mounted
filesystem).
after a cmake and then a "make", the generated "moc*" files contain
an "#include" like this:

#include
"../../../../../misc/euclide/paolini/Git/kdeedu/kig/modes/popup/popup.h"

There is a wrong number of ".." and the path does not work.
using "make VERBOSE=1 kigpart_automoc" it turns out that the following command
is issued:

/usr/lib/qt5/bin/moc -I/home/matem/paolini/Git/kdeedu/kig/modes [...] -o
/home/matem/paolini/Git/kdeedu/kig/moc_popup.cpp
/home/misc/euclide/paolini/Git/kdeedu/kig/modes/popup/popup.h

where the [...] part contains many more -I and various options. Notice that
"/home/matem/paolini/Git/" and "/home/misc/euclide/paolini/Git/" point to the
same place, the first through the symlink "Git", the second is the physical
path.
I guess that then "moc" tries hard to walk (with a relative path) from
one path to the other, but there is no way to successfully climb up
a path with a symlink in it using the ".." directory.

This problem was previously reported in the QT bug tracker
https://bugreports.qt.io/browse/QTBUG-51964



Steps to Reproduce: 
$ mkdir -p a/b
$ ln -s a/b a.lnk
$ cd a.lnk
$ 
$ cd 
$ cmake . [...]
$ make

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 13:36 Maurizio PaoliniNew Issue
==

-- 

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] [CMake 0016046]: GHS Multi Generator: duplicate object file names

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16046 
== 
Reported By:stw_sesa
Assigned To:
== 
Project:CMake
Issue ID:   16046
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-01 08:56 EDT
Last Modified:  2016-04-01 08:56 EDT
== 
Summary:GHS Multi Generator: duplicate object file names
Description: 
When a target contains multiple files with the same name (in different
(sub)folders) the generated object files will have the same names too. Normally
this isn't a problem at all, but for GHS MULTI it is as the duplicates are
ignored.

Steps to Reproduce: 
Create a project with a target containing at least two files with the same name
like this:
add_library(libdemo test.c subfolder/test.c )

Expected result:
The library contains both test.o and subfolder/test.o

Actual result:
Only one of these source files is compiled and archived in the library due to
their name equality.


A sample project is attached, that will build successfully using other C project
generators (e.g Makefile), but won't when using GHS MULTI toolchain.

Additional Information: 
This could also be either a bug in MULTI Project Manager or intended behaviour.
However, from the CMake perspective the results are unexpected.

A workaround for the generator would be to rename the generated object file by
emitting a unique object file name with the option "-o .o" in the
generated project files (.gpj).

Is there any CMake workaround? (which doesn't require changing CMake itself)
Maybe there is an project file option that changes that behaviour?

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 08:56 stw_sesa   New Issue
2016-04-01 08:56 stw_sesa   File Added: dup_objname_test.zip
   
==

-- 

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] [CMake 0016044]: cmake crashed with SIGSEGV in cmTarget::GetProperty()

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16044 
== 
Reported By:Gianfranco
Assigned To:
== 
Project:CMake
Issue ID:   16044
Category:   CMake
Reproducibility:have not tried
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-04-01 05:57 EDT
Last Modified:  2016-04-01 05:57 EDT
== 
Summary:cmake crashed with SIGSEGV in
cmTarget::GetProperty()
Description: 
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1564741

As reported on the Ubuntu bug, the culprit seems to be commit
a67231ac114235f0af4673235c4c07fa896c8ab6.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 05:57 Gianfranco New Issue
==

-- 

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] [CMake 0016043]: Support natvis source file type in the MSVC Project Generator

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16043 
== 
Reported By:Zachary Turner
Assigned To:
== 
Project:CMake
Issue ID:   16043
Category:   CMake
Reproducibility:N/A
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-31 15:12 EDT
Last Modified:  2016-03-31 15:12 EDT
== 
Summary:Support natvis source file type in the MSVC Project
Generator
Description: 
Starting with Visual Studio 14 2015, vcxproj files can contain references to
natvis files which enable custom debug visualizers for project specific types.

You specify these in the vcxproj file by including them in a  tag. 
Currently the MSVC project generator has no support for these.  Through some
hackery, it is still possible to get these files to appear in the vcxproj file
with a  tag, and testing shows that it will work as long as the file has a
.natvis extension, but a) this is undocumented / unsupported reliance on an
implementation detail, b) it doesn't work if your file does not have a .natvis
extension, and c) there could be some issues with doing this which we are
unaware of.

It would be nice if you could write some CMake code like this:

`set_source_files_properties(foo.natvis LANGUAGE natvis)`

and this would cause the vcxproj generator to use a  tag instead of a
 or  tag, and this seems to fit well within CMake's language /
generation model anyway.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-31 15:12 Zachary Turner New Issue
==

-- 

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] [CMake 0016041]: Add support for $ in add_custom_command()

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16041 
== 
Reported By:keksa
Assigned To:
== 
Project:CMake
Issue ID:   16041
Category:   CMake
Reproducibility:N/A
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-31 03:23 EDT
Last Modified:  2016-03-31 03:23 EDT
== 
Summary:Add support for $ in
add_custom_command()
Description: 
It would be useful to support the TARGET_OBJECTS generator expression also in 
the add_custom_command() context (COMMAND and DEPENDS options).

It is useful for building list of objects and than process them by custom 
command (e.g. linker, archiver etc.).
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-31 03:23 keksa  New Issue
==

-- 

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] [CMake 0016040]: Generated Xcode Projects Have Wrong Paths to Object Library Dependencies

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16040 
== 
Reported By:Colin Cornaby
Assigned To:
== 
Project:CMake
Issue ID:   16040
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2016-03-30 16:57 EDT
Last Modified:  2016-03-30 16:57 EDT
== 
Summary:Generated Xcode Projects Have Wrong Paths to Object
Library Dependencies
Description: 
We have a CMake project that has object libraries, and then a parent build
target that wraps those object libraries into a static library. When I generate
the Xcode output, the parent build target is referencing different paths than
what the .o's were outputted to.

I have a patch that fixes the issue, but I wanted to open a bug first,
especially if I'm duplicating something (apologies, this is my first CMake bug.)

The section of code that seems to be the issue in the Xcode generator is here:
cmGlobalXCodeGenerator::GetObjectsNormalDirectory(
  const std::string ,
  const std::string ,
  const cmGeneratorTarget *t) const
{
  std::string dir =
t->GetLocalGenerator()->GetCurrentBinaryDirectory();
  dir += "/";
  dir += projName;
  dir += ".build/";
  dir += configName;
  dir += "/";
  dir += t->GetName();
  dir += ".build/Objects-normal/";

  return dir;
}

There are a few things wrong here:
- The configuration name should be part of this path. Specifically the section
of that path that is "foo.build/release" should be "foo.build/release-iphoneos".
This behavior could be different for Mac targets, but I'm pretty sure it isn't.
One reason I'm not straight submitting the patch yet.
- The .o files get written to the temporary objects directory, not the binary
output directory. I've wrapped this in a new function:
std::string
cmGlobalXCodeGenerator::GetTemporaryFilesDirectory(
  const std::string ,
  const std::string ,
  const cmGeneratorTarget *t)
const
{
std::string dir =
t->GetLocalGenerator()->GetCurrentBinaryDirectory();
dir += "/";
dir += projName;
dir += ".build/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/";

return dir;
}

I've then altered a few functions. GetObjectsNormalDirectory becomes:
//
std::string
cmGlobalXCodeGenerator::GetObjectsNormalDirectory(
  const std::string ,
  const std::string ,
  const cmGeneratorTarget *t) const
{
std::string dir = GetTemporaryFilesDirectory(projName, configName, t);
  dir += t->GetName();
  dir += ".build/Objects-normal/";

  return dir;
}

The build setting creation gets altered a bit a well with:
if(this->XcodeVersion >= 21)
  {
  std::string pncdir = this->GetObjectsNormalDirectory(
   this->CurrentProject,
configName, gtgt);
  std::string tempdir = this->GetTemporaryFilesDirectory(
   this->CurrentProject,
configName, gtgt);
  buildSettings->AddAttribute("CONFIGURATION_BUILD_DIR",
  this->CreateString(pncdir.c_str()));
  buildSettings->AddAttribute("CONFIGURATION_TEMP_DIR",
  this->CreateString(tempdir.c_str()));
  }
else
  {
  buildSettings->AddAttribute("OBJROOT",
  this->CreateString(pndir.c_str()));
  pndir = this->GetObjectsNormalDirectory(
this->CurrentProject, configName, gtgt);
  }
}

Again, mostly submitting this bug because I'm new to Cmake and I don't know if
this is patching on top of behavior that is platform dependent. Please let me
know if there is something I am missing here, or if I'm breaking something else
with these patches!

(I'm attaching a Git patch as well)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-30 16:57 Colin Cornaby  New Issue
2016-03-30 16:57 Colin Cornaby  File Added: 0001-Fixes-for-.o-generation.patch  
 
==

-- 

Powered by www.kitware.com

[cmake-developers] [CMake 0016038]: CHECK_COMPILER_FLAG_COMMON_PATTERNS doesn't match clang-cl's unknown argument warning

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16038 
== 
Reported By:Reid Kleckner
Assigned To:
== 
Project:CMake
Issue ID:   16038
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-30 14:51 EDT
Last Modified:  2016-03-30 14:51 EDT
== 
Summary:CHECK_COMPILER_FLAG_COMMON_PATTERNS doesn't match
clang-cl's unknown argument warning
Description: 
These are the patterns that cmake appears to be looking for to spot unsupported
options:
 FAIL_REGEX "unknown .*option"  # Clang
 FAIL_REGEX "optimization flag .* not supported"# Clang

But we actually have two other diagnostics, one of which needs to be matched:
def err_drv_unknown_argument : Error<"unknown argument: '%0'">;
def warn_drv_unknown_argument_clang_cl : Warning<
  "unknown argument ignored in clang-cl: '%0'">,
  InGroup;

The first is an error diagnostic, so you don't need to match it. We added the
second because MSVC ignores unknown flags, and clang-cl needs to do the same. We
chose the text for consistency with the error diagnostic.

Steps to Reproduce: 
Have this in a cmake project:
check_cxx_compiler_flag(-not-a-real-flag IS_REAL_FLAG)

Configure the project with clang-cl as the compiler.

Observe that IS_REAL_FLAG is ON.

Additional Information: 
This came up while I was trying to build asan with clang-cl.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-30 14:51 Reid Kleckner  New Issue
==

-- 

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] [CMake 0016037]: Various typos

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16037 
== 
Reported By:Felix Geyer
Assigned To:
== 
Project:CMake
Issue ID:   16037
Category:   CMake
Reproducibility:have not tried
Severity:   minor
Priority:   low
Status: new
== 
Date Submitted: 2016-03-29 14:06 EDT
Last Modified:  2016-03-29 14:06 EDT
== 
Summary:Various typos
Description: 
The Debian package checker tool (lintian) detected several typos in CMake
(mostly documentation).
Attached is a patch against git master.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-29 14:06 Felix GeyerNew Issue
2016-03-29 14:06 Felix GeyerFile Added: cmake-spelling.patch
   
==

-- 

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] [CMake 0016035]: Would like support for --remote option with git submodules

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16035 
== 
Reported By:Clinton Stimpson
Assigned To:
== 
Project:CMake
Issue ID:   16035
Category:   CTest
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-28 11:55 EDT
Last Modified:  2016-03-28 11:55 EDT
== 
Summary:Would like support for --remote option with git
submodules
Description: 
CTest supports --init and --recursive options for git submodules, but not the
--remote option.

The --remote option is for submodules that track branches instead of commits.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-28 11:55 Clinton StimpsonNew Issue
==

-- 

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] [CMake 0016034]: Completely wrong FindGettext documentation

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16034 
== 
Reported By:Tatsuyuki Ishi
Assigned To:
== 
Project:CMake
Issue ID:   16034
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2016-03-25 00:42 EDT
Last Modified:  2016-03-25 00:42 EDT
== 
Summary:Completely wrong FindGettext documentation
Description: 
I found out that FindGettext module's document is not only confusing but
completely wrong.

The documentation says:
# GETTEXT_CREATE_TRANSLATIONS ( outputFile [ALL] file1 ...  fileN )
#
# ::
#
# This will create a target "translations" which will convert the
# given input po files into the binary output mo file. If the
# ALL option is used, the translations will also be created when
# building the default target.

What it does:
Process given po files, one by one, expected usage is one po per language.
The outputFile parameter is actually for the gettext package name, internal
codes expects package.pot passed.
And also it implicitly creates install target, without any description.

Other functions' documentation are also confusing, I hope you rewrite these.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-25 00:42 Tatsuyuki Ishi New Issue
==

-- 

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] [CMake 0016033]: WiX 4.x might require new XML namespace

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=16033 
== 
Reported By:Nils Gladitz
Assigned To:Nils Gladitz
== 
Project:CMake
Issue ID:   16033
Category:   (No Category)
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: assigned
== 
Date Submitted: 2016-03-23 11:52 EDT
Last Modified:  2016-03-23 11:52 EDT
== 
Summary:WiX 4.x might require new XML namespace
Description: 
Someone who just tried WiX 4.0 reported that he got the following error:

error CNDL0199 : The Wix element has an incorrect namespace of
'http://schemas.microsoft.com/wix/2006/wi'.  Please make the Wix element look
like the following: http://wixtoolset.org
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-23 11:52 Nils Gladitz   New Issue
2016-03-23 11:52 Nils Gladitz   Status   new => assigned 
2016-03-23 11:52 Nils Gladitz   Assigned To   => Nils Gladitz
==

-- 

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] [CMake 0016032]: CMake doesn't escape # properly in add_compile_options with Makefile generator

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16032 
== 
Reported By:Braden McDaniel
Assigned To:
== 
Project:CMake
Issue ID:   16032
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-22 15:06 EDT
Last Modified:  2016-03-22 15:06 EDT
== 
Summary:CMake doesn't escape # properly in
add_compile_options with Makefile generator
Description: 
This appears to have regressed in 3.5. If I do:

  add_compile_options(-Wno-#pragma-messages)

I get

  -Wno-

...on the command line.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-22 15:06 Braden McDanielNew Issue
==

-- 

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] [CMake 0016031]: FindCUDA.cmake - CUDA_SEPARABLE_COMPILATION fails because of escape character

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16031 
== 
Reported By:Thibault Notargiacomo
Assigned To:
== 
Project:CMake
Issue ID:   16031
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2016-03-22 13:09 EDT
Last Modified:  2016-03-22 13:09 EDT
== 
Summary:FindCUDA.cmake - CUDA_SEPARABLE_COMPILATION fails
because of escape character
Description: 
When using
set( CUDA_SEPARABLE_COMPILATION ON )
in cunjunction with
find_package(CUDA 7.5 REQUIRED)

I get a problem in the make command generated for the link with the intermediate
object file, especially, the "-ccbin" option that should give to the cuda
command line the $CXX variable (in my case).




Steps to Reproduce: 
Try to setup in a directory the following files:

===
test.cu:
#include "test.cu.h"
#include "thrust/device_vector.h"

void A::doIt()
{
thrust::device_vector a(10,10);
std::cout <<"A = "<

[cmake-developers] [CMake 0016029]: GHS Generator does not support LINK_FLAGS property

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16029 
== 
Reported By:stw_sesa
Assigned To:
== 
Project:CMake
Issue ID:   16029
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-22 10:29 EDT
Last Modified:  2016-03-22 10:29 EDT
== 
Summary:GHS Generator does not support LINK_FLAGS property
Description: 
The GHS Generator ignores the LINK_FLAGS property of targets.

It can be set with:
set_target_properties( PROPERTIES LINK_FLAGS )


I did not test it, but other target properties are probably ignored as well. See
https://cmake.org/cmake/help/v3.5/manual/cmake-properties.7.html#target-properties
for a complete list (for all Generators).

Steps to Reproduce: 
add_executable(MyExampleApp main.cpp)
set_target_properties(MyExampleApp PROPERTIES LINK_FLAGS "--myflag")

The option "--myflag" is ignored and not added in the project file
(MyExampleApp.gpj).


Additional Information: 
I've attached a patch that implements the functionality, but I'm sure it needs
some generalization and optimization to integrate it.

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-22 10:29 stw_sesa   New Issue
2016-03-22 10:29 stw_sesa   File Added:
0001-LINK_FLAGS-property-implementation.patch
==

-- 

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] [CMake 0016028]: find_dependency not looking for the correct FOUND variable

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16028 
== 
Reported By:David Wagner
Assigned To:
== 
Project:CMake
Issue ID:   16028
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-22 06:54 EDT
Last Modified:  2016-03-22 06:54 EDT
== 
Summary:find_dependency not looking for the correct FOUND
variable
Description: 
find_package(Xyz) may set either XYZ_FOUND (the default) or Xyz_FOUND (if
overriden by the called) but find_dependency will only look for Xyz_FOUND.

This means that calling, for instance, "find_dependency(LibXml2)" will always
fail because upon finding the package, the LIBXML2_FOUND variable is set.

See a patch below. If you'd prefer, I can submit it on github.

--- /usr/share/cmake-3.2/Modules/CMakeFindDependencyMacro.cmake 2015-04-13
19:09:00.0 +0200
+++ cmake/CMakeFindDependencyMacro.cmake2016-03-22 11:24:08.959963959
+0100
@@ -72,7 +72,8 @@
   set_property(GLOBAL PROPERTY _CMAKE_${dep}_TRANSITIVE_DEPENDENCY TRUE)
 endif()
 
-if (NOT ${dep}_FOUND)
+string(TOUPPER ${dep} DEP)
+if (NOT ${DEP}_FOUND AND NOT ${dep}_FOUND)
   set(${CMAKE_FIND_PACKAGE_NAME}_NOT_FOUND_MESSAGE
"${CMAKE_FIND_PACKAGE_NAME} could not be found because dependency ${dep} could
not be found.")
   set(${CMAKE_FIND_PACKAGE_NAME}_FOUND False)
   return()

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-22 06:54 David Wagner   New Issue
==

-- 

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] [CMake 0016027]: nvcc encloses -ccbin argument with gratuitous quotation marks during intermediate-link phase

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16027 
== 
Reported By:Eyal Rozenberg
Assigned To:
== 
Project:CMake
Issue ID:   16027
Category:   Modules
Reproducibility:sometimes
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-21 17:06 EDT
Last Modified:  2016-03-21 17:06 EDT
== 
Summary:nvcc encloses -ccbin argument with gratuitous
quotation marks during intermediate-link phase
Description: 
I've been using CMake on Debian Stretch with CUDA. I'm not sure what the version
was until recently, but everything worked fine for me. Then I started getting
errors such as:

"/usr/local/cuda/bin/gcc": No such file or directory
CMakeFiles/tester.dir/build.make:2335: recipe for target
'CMakeFiles/wherever/foo.o' failed

The culprit seems to be /usr/share/cmake/Modules/FindCUDA.cmake, line 1554.
Pseudo-patch:

-  list(APPEND nvcc_flags -ccbin "\"${CUDA_HOST_COMPILER}\"")
+  list(APPEND nvcc_flags -ccbin "${CUDA_HOST_COMPILER}")

that resolves the issue.

Steps to Reproduce: 
1. export CC=/link/to/your/appropriate/gcc
2. cmake a project with CMakeList.txt which finds CUDA and with
set(CUDA_SEPARABLE_COMPILATION ON)
3. Build the project

The .cu files will compile, the intermediate-link phase won't pass

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-21 17:06 Eyal Rozenberg New Issue
==

-- 

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] [CMake 0016026]: CMake provides no reliable variable for 'the file a function is declared in'

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=16026 
== 
Reported By:Stephen Kelly
Assigned To:
== 
Project:CMake
Issue ID:   16026
Category:   (No Category)
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-20 19:35 CET
Last Modified:  2016-03-20 19:35 CET
== 
Summary:CMake provides no reliable variable for 'the file a
function is declared in'
Description: 

Given

  $ cat cmake/thefunc.cmake 

  set(somevar "${CMAKE_CURRENT_LIST_DIR}")

  function(thefunc)
message("somevar: ${somevar}")
message("listdir: ${CMAKE_CURRENT_LIST_DIR}")
  endfunction()

  $ cat dir1/CMakeLists.txt 

  include(thefunc)

  thefunc()

  include(GenerateExportHeader)

  $ cat CMakeLists.txt

  cmake_minimum_required(VERSION 2.8.12)

  project(ttt CXX)

  list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake)

  add_subdirectory(dir1)

  thefunc()

  if (COMMAND generate_export_header)
add_library(foo foo.cpp)
generate_export_header(foo)
  endif()

the build output is

  somevar: /home/stephen/dev/src/playground/cmake/cmake
  listdir: /home/stephen/dev/src/playground/cmake/dir1
  somevar: 
  listdir: /home/stephen/dev/src/playground/cmake
  CMake Error: File /exportheader.cmake.in does not exist.
  CMake Error at
/home/stephen/dev/prefix/qtbase/kde/share/cmake-3.5/Modules/GenerateExportHeader.cmake:362
(configure_file):
configure_file Problem configuring file
  Call Stack (most recent call first):
   
/home/stephen/dev/prefix/qtbase/kde/share/cmake-3.5/Modules/GenerateExportHeader.cmake:378
(_do_generate_export_header)
CMakeLists.txt:14 (generate_export_header)


  -- Configuring incomplete, errors occurred!


That is: CMake doesn't provide a way to determine the file a macro or function
is defined in. The workaround is to determine that outside of the function/macro
scope. However, that workaround breaks down because the variable and the
function/macro do not follow the same scoping rules. The function/macro is
available 'globally' after definition, so users can make the mistake of trying
to use it in a scope which does not contain the `include()`.

This affects at least the GenerateExportHeader module and perhaps other modules
shipped with cmake.

One workaround is to check the existence of the variable in the function:

 https://git.reviewboard.kde.org/r/127432/diff/1

Another would be to use a global property instead of a variable for the
workaround.

A better solution may be for cmake to provide the 'path of the file this code
resides in' in a variable. 

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-20 19:35 Stephen Kelly  New Issue
==

-- 

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] [CMake 0016023]: OS X CMake.app (version 3.5) contains empty CFBundleIdentifier, which is malformed

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16023 
== 
Reported By:Sean McBride
Assigned To:
== 
Project:CMake
Issue ID:   16023
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-17 15:43 EDT
Last Modified:  2016-03-17 15:43 EDT
== 
Summary:OS X CMake.app (version 3.5) contains empty
CFBundleIdentifier, which is malformed
Description: 
CMake.app's Info.plist contains:

CFBundleIdentifier


That entry isn't allowed to be empty.

I suggest a value like "org.cmake.cmake" or something.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-17 15:43 Sean McBride   New Issue
==

-- 

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] [CMake 0016021]: Cannot build on OS X with GCC

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16021 
== 
Reported By:Erik Schnetter
Assigned To:
== 
Project:CMake
Issue ID:   16021
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-16 14:14 EDT
Last Modified:  2016-03-16 14:14 EDT
== 
Summary:Cannot build on OS X with GCC
Description: 
I cannot build cmake 3.5.0 on OS X "El Capitan" with GCC 5.3. After configuring
normally, the build aborts with an error message. It seems that cmake uses some
system header files with Apple-specific extensions that GCC cannot handle.

These extensions seem to have to do with the user interface; if so, there should
be an option to not build the parts that cannot be built, and still build the
"regular" cmake.

cmake 3.4.3 builds fine with the same setup.


Steps to Reproduce: 
Install GCC 5.3 via MacPorts; make GCC the default compiler

tar xzf cmake-3.5.0.tar.gz 
cd cmake-3.5.0
# Building without the OpenSSL flag aborts with an error
./configure -- -DCMAKE_USE_OPENSSL=ON
gmake


Additional Information: 
The build aborts with

[ 85%] Building CXX object
Source/CMakeFiles/CPackLib.dir/CPack/cmCPackDragNDropGenerator.cxx.o
In file included from /usr/include/Availability.h:168:0,
 from /usr/include/inttypes.h:224,
 from /tmp/cmake-3.5.0/Utilities/KWIML/include/kwiml/int.h:194,
 from /tmp/cmake-3.5.0/Utilities/cm_kwiml.h:22,
 from /tmp/cmake-3.5.0/Source/cmStandardIncludes.h:34,
 from /tmp/cmake-3.5.0/Source/cmObject.h:15,
 from /tmp/cmake-3.5.0/Source/CPack/cmCPackGenerator.h:16,
 from
/tmp/cmake-3.5.0/Source/CPack/cmCPackDragNDropGenerator.h:16,
 from
/tmp/cmake-3.5.0/Source/CPack/cmCPackDragNDropGenerator.cxx:13:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSInfoDeprecated.h:1242:34:
error: expected '}' before '__attribute__'
   kLSHandlerOptionsDefault   __OSX_AVAILABLE_BUT_DEPRECATED_MSG(__MAC_10_4,
__MAC_10_11, __IPHONE_4_0, __IPHONE_9_0, "Creator codes are deprecated on OS
X.") = 0,
  ^
In file included from
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSInfo.h:529:0,
 from
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LaunchServices.h:27,
 from
/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:39,
 from
/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
 from
/tmp/cmake-3.5.0/Source/CPack/cmCPackDragNDropGenerator.cxx:34:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSInfoDeprecated.h:1242:163:
error: expected unqualified-id before '=' token
   kLSHandlerOptionsDefault   __OSX_AVAILABLE_BUT_DEPRECATED_MSG(__MAC_10_4,
__MAC_10_11, __IPHONE_4_0, __IPHONE_9_0, "Creator codes are deprecated on OS
X.") = 0,


 ^
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSInfoDeprecated.h:1294:1:
error: expected declaration before '}' token
 }
 ^
Source/CMakeFiles/CPackLib.dir/build.make:518: recipe for target
'Source/CMakeFiles/CPackLib.dir/CPack/cmCPackDragNDropGenerator.cxx.o' failed
gmake[2]: ***
[Source/CMakeFiles/CPackLib.dir/CPack/cmCPackDragNDropGenerator.cxx.o] Error 1
CMakeFiles/Makefile2:2018: recipe for target
'Source/CMakeFiles/CPackLib.dir/all' failed
gmake[1]: *** [Source/CMakeFiles/CPackLib.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
gmake: *** [all] Error 2

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-16 14:14 Erik Schnetter New Issue
==

-- 

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-developers] [CMake 0016025]: Add support WINDOWS_EXPORT_ALL_SYMBOLS for executable exports lib

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16025 
== 
Reported By:Yury Zhuravlev
Assigned To:
== 
Project:CMake
Issue ID:   16025
Category:   CMake
Reproducibility:always
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-18 10:04 EDT
Last Modified:  2016-03-18 10:04 EDT
== 
Summary:Add support WINDOWS_EXPORT_ALL_SYMBOLS for
executable exports lib
Description: 
For access from DLL to mother programm we need create .lib by EXPORTS flag but
without /DEF we can't export symbols.

This code must work:
add_executable(prog1 blalba)
set_target_properties(prog1 PROPERTIES ENABLE_EXPORTS 1)
set_target_properties(prog1 PROPERTIES WINDOWS_EXPORT_ALL_SYMBOLS 1)

Now I use ugly perl script for gen .def file.

Thanks. 
PS for .dll's WINDOWS_EXPORT_ALL_SYMBOLS worked correct. 
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-18 10:04 Yury Zhuravlev New Issue
==

-- 

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] [CMake 0016024]: Add support to use OpenBLAS to FindBLAS/FindLAPACK

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16024 
== 
Reported By:J M Dieterich
Assigned To:
== 
Project:CMake
Issue ID:   16024
Category:   Modules
Reproducibility:N/A
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-17 17:10 EDT
Last Modified:  2016-03-17 17:10 EDT
== 
Summary:Add support to use OpenBLAS to FindBLAS/FindLAPACK
Description: 
OpenBLAS (www.openblas.net) is the successor to GotoBLAS. FindBLAS/FindLAPACK
support finding Goto (among other BLAS implmentations) but not OpenBLAS.
OpenBLAS is a relatively widely used BLAS as it is fast and free.

Find attaches a patch adding support to find OpenBLAS (BLA_VENDOR=OpenBLAS) for
both FindBLAS, FindLAPACK.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-17 17:10 J M Dieterich  New Issue
2016-03-17 17:10 J M Dieterich  File Added: add_openblas.diff   

==

-- 

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] [CMake 0016022]: GenerateExportHeader DEFINE_NO_DEPRECATED define conflicts

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16022 
== 
Reported By:Andreas Schuh
Assigned To:
== 
Project:CMake
Issue ID:   16022
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-16 17:27 EDT
Last Modified:  2016-03-16 17:28 EDT
== 
Summary:GenerateExportHeader DEFINE_NO_DEPRECATED define
conflicts
Description: 
The header file generated by generate_export_header adds a

#define DEFINE_NO_DEPRECATED 0|1

macro which is used to decide whether or not to define the respective macro with
the desired library prefix and base name. But this macro has the same name for
all libraries and is not undefined when it is no longer needed. In my project,
this for example created a conflict with the VTK library which uses such
generated header file which must of course be included in the public header
files.

To solve this conflict, I am using now (temporarily) a custom
exportheader.cmake.in template file by changing the
_GENERATE_EXPORT_HEADER_MODULE_DIR path to a directory in my project after
including the GenerateExportHeader module. Find the modified template file
attached.

There is certainly a better fix for this bug.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-16 17:27 Andreas Schuh  New Issue
2016-03-16 17:28 Andreas Schuh  File Added: exportheader.cmake.in   

==

-- 

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