[cmake-developers] [CMake 0015959]: Using CMake-Gui to run generate for Windows followed by generate for Unix generates incorrect Unix makefiles

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15959 
== 
Reported By:Jon Kristensen
Assigned To:
== 
Project:CMake
Issue ID:   15959
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-02-08 02:56 EST
Last Modified:  2016-02-08 02:56 EST
== 
Summary:Using CMake-Gui to run generate for Windows followed
by generate for Unix generates incorrect Unix makefiles
Description: 
Running a generator that uses the Windows Shell, and then running a generator
that uses the Unix shell without exiting Cmake-gui first, causes the Unix
makefiles to have the wrong shell command (SHELL = cmd.exe) and Windows path
names (with ‘\’s instead of ‘/’s).




Steps to Reproduce: 
1. Start cmake-gui
2. Select a project that uses the Visual Studio 2015 generator and run generate
3. Select a project that uses the CDT4 – Unix makefiles and run generate

Additional Information: 
Assumed cause (based on cmake-3.4.3 source distribution) :

The selection of shell seems to be based on the variable cmState::windowsShell
This variable is set to false in the cmState constructor, 
and is set to true (through a call to member SetWindowsShell(true) from all
generators that use a Windows shell.
But I could find no code that resets it if a non-Windows-Shell generator is run
at a later time
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-02-08 02:56 Jon Kristensen 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

Re: [cmake-developers] [PATCH] Bug fix: Dylibs inside .framework folders fails in BundleUtilities.cmake.

[Christian Askeland]

> On 5. feb. 2016, at 16.22, Brad King  wrote:
> 
> On 02/04/2016 01:34 PM, Christian Askeland wrote:
>> The specific cause is when e.g.
>> 
>> /Library/Frameworks/GStreamer.framework/Versions/1.0/lib/libgio-2.0.0.dylib
>> 
>> is detected by fixup_bundle. BundleUtilities.cmake/set_bundle_key_values()
>> interprets this as a framework, thus doing a string replace that creates an
>> embedded_item that is equal to the original path, i.e. it is not embedded.
>> 
>> The fix is to rely on the correct framework detection in
>> GetPrerequisite.cmake/gp_item_default_embedded_path() instead.
> [snip]
>> -if(item MATCHES "[^/]+\\.framework/")
>> +# Use default_embedded_path from gp_item_default_embedded_path() to 
>> query whether the item is a framework
>> +if(default_embedded_path MATCHES "/Frameworks")
> 
> If the project uses gp_item_default_embedded_path_override then
> we cannot rely on the value from gp_item_default_embedded_path.

Good point, I didn't see that one.

> Is there another way to detect whether the item is actually the
> main framework library itself or just something else inside one?
> 

We could reuse the check from gp_item_default_embedded_path(), instead of 
looking at the result from that function:

 if((item NOT MATCHES "\\.dylib$") AND (item MATCHES "[^/]+\\.framework/"))

I haven't tested the line above, but can do so tomorrow and post a new patch, 
if it looks reasonable.

> Thanks,
> -Brad
> 


-Christian
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] [PATCH] Help: fix mistake in cmake-buildsystem(7)

[Paul Wilkinson]

The COMPATIBLE_INTERFACE_NUMBER_MAX example now sets
INTERFACE_CONTAINER_SIZE_REQUIRED on lib1Version2 and lib1Version3 (it
previously set it on lib1Version2 twice and never on
lib1Version3. Probably a copy-paste mistake?)
---
 Help/manual/cmake-buildsystem.7.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Help/manual/cmake-buildsystem.7.rst
b/Help/manual/cmake-buildsystem.7.rst
index 4a04f31..9004bb2 100644
--- a/Help/manual/cmake-buildsystem.7.rst
+++ b/Help/manual/cmake-buildsystem.7.rst
@@ -427,7 +427,7 @@ specified will be calculated:
   )

   add_library(lib1Version3 SHARED lib1_v3.cpp)
-  set_property(TARGET lib1Version2 PROPERTY
INTERFACE_CONTAINER_SIZE_REQUIRED 1000)
+  set_property(TARGET lib1Version3 PROPERTY
INTERFACE_CONTAINER_SIZE_REQUIRED 1000)

   add_executable(exe1 exe1.cpp)
   # CONTAINER_SIZE_REQUIRED will be "200"
-- 
1.9.1
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc1-53-gc4e3666

[Gregor Jasny via Cmake-commits]

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

The branch, next has been updated
   via  c4e3666047f50c16673ab70c66b57046995052b5 (commit)
   via  2cae5128fdc6316a7f0913cb89ec467b33b9715b (commit)
   via  c8100794b4faab4255c1229f966f57525c18ccc7 (commit)
   via  d276b6e9971a3f4d0a99c6e46ebb0533fbeee5db (commit)
  from  b11b9d05dd1d9e77ac76f6b9b72c4f1face53418 (commit)

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

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c4e3666047f50c16673ab70c66b57046995052b5
commit c4e3666047f50c16673ab70c66b57046995052b5
Merge: b11b9d0 2cae512
Author: Gregor Jasny 
AuthorDate: Sun Feb 7 14:42:32 2016 -0500
Commit: CMake Topic Stage 
CommitDate: Sun Feb 7 14:42:32 2016 -0500

Merge topic 'apple-isystem-gcc' into next

2cae5128 Apple: Enable -isystem for GNU Compiler >= 4 (#15953)
c8100794 CMake Nightly Date Stamp
d276b6e9 CMake Nightly Date Stamp


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2cae5128fdc6316a7f0913cb89ec467b33b9715b
commit 2cae5128fdc6316a7f0913cb89ec467b33b9715b
Author: Gregor Jasny 
AuthorDate: Sun Feb 7 20:20:02 2016 +0100
Commit: Gregor Jasny 
CommitDate: Sun Feb 7 20:20:02 2016 +0100

Apple: Enable -isystem for GNU Compiler >= 4 (#15953)

Due to #4662 -isystem support was disabled for all GNU Compilers
on Apple platforms. But the change was probably a just work around
for a broken compiler on Tiger (see 10837#c27206). So we tighten
the condition to only kick in for GCC versions earlier than 4.
That should ensure sane behavior for Xcode 3.2 and later.

diff --git a/Modules/Compiler/GNU.cmake b/Modules/Compiler/GNU.cmake
index 764fbf9..d1ca85e 100644
--- a/Modules/Compiler/GNU.cmake
+++ b/Modules/Compiler/GNU.cmake
@@ -52,7 +52,7 @@ macro(__compiler_gnu lang)
   set(CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT "-O2 -g -DNDEBUG")
   set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE " 
   -E  > ")
   set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "  
  -S  -o ")
-  if(NOT APPLE)
+  if(NOT APPLE OR NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 4) # work 
around #4462
 set(CMAKE_INCLUDE_SYSTEM_FLAG_${lang} "-isystem ")
   endif()
 endmacro()

---

Summary of changes:
 Modules/Compiler/GNU.cmake |2 +-
 Source/CMakeVersion.cmake  |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


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

[cmake-developers] [CMake 0015957]: cmake-gui.1 man page should not be installed unless --qt-gui is given

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=15957 
== 
Reported By:Orion Poplawski
Assigned To:
== 
Project:CMake
Issue ID:   15957
Category:   CMake
Reproducibility:always
Severity:   trivial
Priority:   normal
Status: new
== 
Date Submitted: 2016-02-07 17:45 EST
Last Modified:  2016-02-07 17:45 EST
== 
Summary:cmake-gui.1 man page should not be installed unless
--qt-gui is given
Description: 
cmake-gui.1 man page should not be installed unless --qt-gui is given
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-02-07 17:45 Orion PoplawskiNew 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 0015956]: TryCompile generation of cmake failed

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=15956 
== 
Reported By:davidk
Assigned To:
== 
Project:CMake
Issue ID:   15956
Category:   (No Category)
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-02-07 17:24 EST
Last Modified:  2016-02-07 17:24 EST
== 
Summary:TryCompile generation of cmake failed
Description: 
CMake 3.1.3 fails to compile a project, but CMake 3.0 works well.
It seems like the problem occurs when CMake tries to check the avaible compiler
features.
Yes, I have a working c/c++ compiler installed (gcc 5.3).
I'm executing CMake with root privileges, so there shouldn't be any permission
problems.

Steps to Reproduce: 
Try to configure kdelibs4support (A KDE library)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-02-07 17:24 davidk New Issue
2016-02-07 17:24 davidk 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

Re: [CMake] [cmake-developers] Drop support for older Xcode versions?

[Michael Jackson]

What is the oldest version of OS X that CMake actually runs on? I guess 
I would support the last version of Xcode that actually ran on that 
platform. In reality this is probably 10.6.8? But At the next major 
update of CMake (3.5 or 3.6) I would actually draw a line in the sand 
and pump that up to OS X 10.9, 10.8 at the absolute minimum. I think 
that is Xcode 6?


Just my thoughts.

Mike Jackson


Eric Wing 
February 6, 2016 at 6:46 PMvia Postbox 



I personally am not using them. My more serious problem is that the
Xcode projects being generated now are not keeping up with modern
Xcode and the features that need to be accessible/set. The reality of
Apple development is you must be on the latest stable Xcode if you
need to ship apps on the Mac or iOS Store, otherwise Apple can reject
your app. Their design philosophy, regardless if you agree with it or
not, is to build with the latest and build against backwards
compatibility deployment targets, not build with the oldest and pray
it will work with future changes that couldn't be predicted at the
time. Their platform, their rules.

So I'm all in favor of dropping legacy platforms if it means
ultimately helping make the Xcode generator work better for modern
Xcode. General rule of thumb for Apple development is support the
latest and -1 version. If you can do more, fine, but don't compromise
the recent stuff in order to achieve distant backwards compatibility.

-Eric
Gregor Jasny via CMake 
February 6, 2016 at 5:49 AMvia Postbox 


Hello,

I'd like to get your feedback on deprecating or dropping support for
older Xcode versions. During changes on the Xcode generator it gets
harder and harder to test against old and very old Xcode versions like 3
and 4.

Are there still users around for these versions of Xcode?

PS: I'm talking here about the Xcode generator which creates Xcode
projects, not the Makefile or Ninja generator.

Thanks,
Gregor


--
Michael A. Jackson 400 S. Pioneer Blvd
Owner, President   Springboro, Ohio 45066
BlueQuartz Software, LLC   EMail: mike.jack...@bluequartz.net
Voice: 937-806-1165Web: http://www.bluequartz.net
Fax: 
937-746-0783
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] ExternalProject question

[Nicholas Braden]

You will need to look at their building documentation to find how to
set those preferences when building with CMake.

On Sat, Feb 6, 2016 at 11:47 PM, vadtec  wrote:
> I'm using ExternalProject to build external dependencies. curl provides a
> cmake build process, but I cannot figure out how to pass options such as:
>
> --disable-manual --disable-shared --without-librtmp --without-libidn
> --without-winidn --without-winssl --disable-ldap --disable-ldaps
> --enable-ipv6 --enable-threaded-resolver --enable-cookies --enable-static
>
> to the build process. The only way I've found to get it to work is to use a
> custom CONFIGURE_COMMAND and related steps. I would prefer to use the cmake
> build process.
>
> This is what I have that works:
>
> ExternalProject_Add(
> CURL
> DEPENDS OPENSSL ZLIB OPENSSH
> SOURCE_DIR ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/
> PREFIX ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/
> DOWNLOAD_COMMAND tar xvjf ${PROJECT_BINARY_DIR}/deps/curl-7.43.0.tar.bz2
> DOWNLOAD_DIR ${PROJECT_BINARY_DIR}/deps/
> CONFIGURE_COMMAND cd ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/ &&
> ./configure --prefix=${PROJECT_BINARY_DIR}/deps/binary/linux/
> --disable-manual --disable-shared --without-librtmp --without-libidn
> --without-winidn --without-winssl --disable-ldap --disable-ldaps
> --enable-ipv6 --enable-threaded-resolver --enable-cookies --enable-static
> BUILD_COMMAND cd ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/ && make
> INSTALL_COMMAND ""
> )
>
> I want to use this, so that cmake can do its thing while still giving me the
> specific variant of curl I want:
>
> ExternalProject_Add(
> CURL
> DEPENDS OPENSSL ZLIB OPENSSH
> SOURCE_DIR ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/
> PREFIX ${PROJECT_BINARY_DIR}/deps/curl-7.43.0/
> DOWNLOAD_COMMAND tar xvjf ${PROJECT_BINARY_DIR}/deps/curl-7.43.0.tar.bz2
> DOWNLOAD_DIR ${PROJECT_BINARY_DIR}/deps/
> CMAKE_ARGS
> -DCMAKE_INSTALL_PREFIX=${PROJECT_BINARY_DIR}/deps/binary/linux/
> -DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS}
> -DCMAKE_C_FLAGS=${CMAKE_C_FLAGS}
> -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
> -DCMAKE_MOUDLE_PATH=${MAKE_MOUDLE_PATH}
> INSTALL_COMMAND ""
> )
>
> 
> Vadtec
> vad...@vadtec.net
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[cmake-developers] [CMake 0015958]: ctest FTP failure

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=15958 
== 
Reported By:Orion Poplawski
Assigned To:
== 
Project:CMake
Issue ID:   15958
Category:   CTest
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-02-07 17:53 EST
Last Modified:  2016-02-07 17:53 EST
== 
Summary:ctest FTP failure
Description: 
See https://bugzilla.redhat.com/show_bug.cgi?id=1305310

332:   Expected stderr to match:
332: 
332:expect-err> Error message was: ([Cc]ould *n.t resolve host:?
'?-no-site-'?|The requested URL returned error:.*)
332:expect-err>Problems when submitting via FTP
332: 
332:   Actual stderr:
332: 
332:actual-err>Error when uploading file:
/home/bob/rpmbuild/BUILD/cmake-3.4.3/build/Tests/RunCMake/ctest_submit/FailDrop-ftp-build/Testing/20160206-1516/Configure.xml
332:actual-err>Error message was: Could not resolve host: -no-site-;
Name or service not known
332:actual-err>Problems when submitting via FTP



Additional Information: 
diff -urt
cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/CDashSubmitQuiet-stderr.txt
cmake-3.4.3/Tests/RunCMake/ctest_submit/CDashSubmitQuiet-stderr.txt
---
cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/CDashSubmitQuiet-stderr.txt
2016-01-25
17:57:22.0 +0100
+++
cmake-3.4.3/Tests/RunCMake/ctest_submit/CDashSubmitQuiet-stderr.txt 
2016-02-06
15:52:14.309214430 +0100
@@ -1,3 +1,3 @@
  *Error when uploading file: .*/Configure.xml
- *Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?|The requested
URL returned error:.*)
+ *Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?.*|The
requested URL returned error:.*)
  *Problems when submitting via HTTP
diff -urt cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-ftp-stderr.txt
cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-ftp-stderr.txt
---
cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-ftp-stderr.txt
2016-01-25
17:57:22.0 +0100
+++ cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-ftp-stderr.txt 
2016-02-06
16:20:06.557615425 +0100
@@ -1,2 +1,2 @@
-Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?|The requested
URL returned error:.*)
+Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?.*|The requested
URL returned error:.*)
Problems when submitting via FTP
diff -urt cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-https-stderr.txt
cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-https-stderr.txt
---
cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-https-stderr.txt  
2016-01-25
17:57:22.0 +0100
+++ cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-https-stderr.txt   
2016-02-06
16:19:54.332442544 +0100
@@ -1,2 +1,2 @@
-Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?|The requested
URL returned error:.*|Protocol "https" not supported or disabled in .*|.* was
built with SSL disabled.*)
+Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?.*|The requested
URL returned error:.*|Protocol "https" not supported or disabled in .*|.* was
built with SSL disabled.*)
Problems when submitting via HTTP
diff -urt cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-http-stderr.txt
cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-http-stderr.txt
---
cmake-3.4.3-orig/Tests/RunCMake/ctest_submit/FailDrop-http-stderr.txt   
2016-01-25
17:57:22.0 +0100
+++ cmake-3.4.3/Tests/RunCMake/ctest_submit/FailDrop-http-stderr.txt
2016-02-06
16:19:17.430908893 +0100
@@ -1,2 +1,2 @@
-Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?|The requested
URL returned error:.*)
+Error message was: ([Cc]ould *n.t resolve host:? '?-no-site-'?.*|The requested
URL returned error:.*)
Problems when submitting via HTTP
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-02-07 17:53 Orion PoplawskiNew 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: 

[cmake-developers] Visual Studio 2015 Makefile Project (GDB)

[Cedric Perthuis]

Hi,

Visual studio has a new interesting extension which adds the project type
"Makefile Project (GDB)".

I am interested in exploring adding this project type to cmake, and
probably to the Visual Studio 2015 generator.

It's used to build and debug a program using GDB over an SSH connection,
it's mainly targeted at developing Linux programs from the Visual Studio
IDE. It doesn't include the build, it only hooks the build command of VS to
a user defined windows command. Up to that command to use SSH to execute
code on the target.

It's a VS 2015 NMake project type with 3 config files for build command,
run command, and SSH parameters. Some of the interesting parts of the
vcxproj


LinuxDebugger
ssh
gdb
gdb
{8E0AD268-B47B-4ED3-B9E0-F93E5CB1077B}
  

 
Makefile
true
v140
  

 

false
false
<_ApplicableDebuggers>Desktop
LinuxDebugger
  

And the 3 config files:
  



  

Neither the project nor the config files include any source file (I am sure
we can add cpp files but they won't be associated with any compiler). The
project has slots for build and debug command. As a user you have to write
a build command which transfers of sources via SSH and do the compilation
yourself.

Here's an example of build command that the user can use

build.bat $(RemoteHostName) $(RemoteUserName) $(PrivateKey)
$(SecureShellExecutable) $(RemoteWorkingDirectory) $(RemoteExecutable)

The build.bat would be something along those lines:
"%SecureShellExecutable%" %RemoteUserName%@%RemoteHostName% -i
"%PrivateKey%" "mkdir -p %RemoteWorkingDirectory%"
"%SecureShellCopy%" -i "%PrivateKey%" source.cpp  %RemoteUserName%@
%RemoteHostName%:%RemoteWorkingDirectory%/source.cpp
"%SecureShellExecutable%" %RemoteUserName%@%RemoteHostName% -i
"%PrivateKey%" "cd %RemoteWorkingDirectory%;g++ -g source.cpp -o
%RemoteExecutable%"

Adding a generator for this is probably straightforward, but to respect the
format of the other cmake (and make it easier for the developer), I think
it should go further and also generate a linux makefile.

- the vs2015 generator can be augmented to create this new project type
- the linux makefile can already be generated from the makefile generator.

My question is what would be a good way to combine those 2. I was thinking
of trying to invoke the makefile generator from the vs2015 generator?

Any thoughts or advice?

Thanks,
Cedric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Visual Studio 2015 Makefile Project (GDB)

[Cedric Perthuis]

I did some experiments, and I think it's a bit easier than I thought. I
don't think I need to generate the linux makefile from the Visual Studio
generator on windows. I would just add few new cmake options for the Visual
Studio GDB project type and among those the "build command" option.
And as a user, in the build command option, I can simply execute a script
on the target which calls cmake there to generate the makefile and then
call make.

On Sun, Feb 7, 2016 at 4:01 PM, Cedric Perthuis 
wrote:

> Hi,
>
> Visual studio has a new interesting extension which adds the project type
> "Makefile Project (GDB)".
>
> I am interested in exploring adding this project type to cmake, and
> probably to the Visual Studio 2015 generator.
>
> It's used to build and debug a program using GDB over an SSH connection,
> it's mainly targeted at developing Linux programs from the Visual Studio
> IDE. It doesn't include the build, it only hooks the build command of VS to
> a user defined windows command. Up to that command to use SSH to execute
> code on the target.
>
> It's a VS 2015 NMake project type with 3 config files for build command,
> run command, and SSH parameters. Some of the interesting parts of the
> vcxproj
>
> 
> LinuxDebugger
> ssh
> gdb
> gdb
> {8E0AD268-B47B-4ED3-B9E0-F93E5CB1077B}
>   
>
>   Label="Configuration">
> Makefile
> true
> v140
>   
>
>  
>
> false
> false
> <_ApplicableDebuggers>Desktop
> LinuxDebugger
>   
>
> And the 3 config files:
>   
> 
> 
> 
>   
>
> Neither the project nor the config files include any source file (I am
> sure we can add cpp files but they won't be associated with any compiler).
> The project has slots for build and debug command. As a user you have to
> write a build command which transfers of sources via SSH and do the
> compilation yourself.
>
> Here's an example of build command that the user can use
>
> build.bat $(RemoteHostName) $(RemoteUserName) $(PrivateKey)
> $(SecureShellExecutable) $(RemoteWorkingDirectory) $(RemoteExecutable)
>
> The build.bat would be something along those lines:
> "%SecureShellExecutable%" %RemoteUserName%@%RemoteHostName% -i
> "%PrivateKey%" "mkdir -p %RemoteWorkingDirectory%"
> "%SecureShellCopy%" -i "%PrivateKey%" source.cpp  %RemoteUserName%@
> %RemoteHostName%:%RemoteWorkingDirectory%/source.cpp
> "%SecureShellExecutable%" %RemoteUserName%@%RemoteHostName% -i
> "%PrivateKey%" "cd %RemoteWorkingDirectory%;g++ -g source.cpp -o
> %RemoteExecutable%"
>
> Adding a generator for this is probably straightforward, but to respect
> the format of the other cmake (and make it easier for the developer), I
> think it should go further and also generate a linux makefile.
>
> - the vs2015 generator can be augmented to create this new project type
> - the linux makefile can already be generated from the makefile generator.
>
> My question is what would be a good way to combine those 2. I was thinking
> of trying to invoke the makefile generator from the vs2015 generator?
>
> Any thoughts or advice?
>
> Thanks,
> Cedric
>
>
>
>
>
>
-- 

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] Find correct boost among peers

[B. Scott Harper]

I have several versions of boost downloaded on my machine inside a
"thirdparty" directory. Different projects rely on various versions.

I am trying to find a later version than the first version in that
collection. I have gotten the closest by using a file(GLOB ...) as follows:

file(GLOB BOOST_ROOT ${THIRD_PARTY_DIR}/boost_*)
find_package(Boost
  1.60.0
  REQUIRED)

...but if I have any versions of Boost earlier than 1.60.0 in this case, it
will find only the first directory, recognize that it's too early, and bail
out without trying any other directories.

When I print out the results of the GLOB action using message(STATUS "Boost
root: " ${BOOST_ROOT}), I don't see any delimiters in the string, and I
wonder if this it causing the problem? Is this expected beahiour or am I
using this incorrectly?

Cheers,
-- Scott
-- 

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