[Cmake-commits] CMake branch, master, updated. v3.6.1-614-gf99df80

[Kitware Robot]

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

The branch, master has been updated
   via  f99df80794df7acc383d93d47b5da3ac8450e117 (commit)
  from  f203694bb848e7a4bd2c623348053532b1b4e589 (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=f99df80794df7acc383d93d47b5da3ac8450e117
commit f99df80794df7acc383d93d47b5da3ac8450e117
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Aug 12 00:01:04 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Aug 12 00:01:04 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index a4e305a..1e20881 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160811)
+set(CMake_VERSION_PATCH 20160812)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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

[CMake] Need fix bid to build CMake generated Library.

[Ken Boulange]

I am a one man company that needs to get a Library built from C/C++ source
using CMake.

 

My system is windows 7 Professional.  I am running MVS 8 (Microsoft Visual
Studios 8)  I need the following library built from the below URL (It's a
DICOM image Library):

 

http://dicom.offis.de/dcmtk.php.en

 

It's configured to be built by CMake.   I've come close, but not close
enough.

 

I am looking for someone to download Cmake and the
"http://dicom.offis.de/dcmtk.php.en;  source,   then run CMake and build the
libraries.

 

I am looking for a fixed bid to do it.  I have very little cash that is why
I need a fixed bid.

 

Can anyone on this list help me?

 

Ken 

 

415 987 9414.

 

-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [cmake-developers] Bugfix: Default behavior of CUDA_USE_STATIC_CUDA_RUNTIME

[Sorley, Stephen L.]

The previous fix uncovered another bug from commit 7229ae7.  That commit 
dropped librt from the link line when using static linking with CUDA 7.0 or 
newer on Linux.  However, librt is still required on the link line in newer 
CUDA versions, I get linker errors without it.

I've attached a second patch to fix this extra bug.

Thanks!
Stephen Sorley

From: Sorley, Stephen L.
Sent: Thursday, August 11, 2016 3:37 PM
To: cmake-developers@cmake.org
Subject: Bugfix: Default behavior of CUDA_USE_STATIC_CUDA_RUNTIME

Recent changes to FindCUDA.cmake (commit 7229ae7) broke the documented behavior 
of the CUDA_USE_STATIC_CUDA_RUNTIME option.  Per the documentation, this option 
should be enabled by default if libcudart_static is present in the selected 
version of CUDA, and silently disabled if it's not.  After commit 7229ae7, the 
option is disabled by default instead.

I've attached a small patch (based on master) that fixes the problem.

Thanks!
Stephen Sorley


0001-Fix-for-missing-librt-on-Linux-when-using-static-cud.patch
Description: 0001-Fix-for-missing-librt-on-Linux-when-using-static-cud.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] Bugfix: Default behavior of CUDA_USE_STATIC_CUDA_RUNTIME

[Sorley, Stephen L.]

Recent changes to FindCUDA.cmake (commit 7229ae7) broke the documented behavior 
of the CUDA_USE_STATIC_CUDA_RUNTIME option.  Per the documentation, this option 
should be enabled by default if libcudart_static is present in the selected 
version of CUDA, and silently disabled if it's not.  After commit 7229ae7, the 
option is disabled by default instead.

I've attached a small patch (based on master) that fixes the problem.

Thanks!
Stephen Sorley


0001-Restore-default-behavior-of-CUDA_USE_STATIC_CUDA_RUN.patch
Description: 0001-Restore-default-behavior-of-CUDA_USE_STATIC_CUDA_RUN.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

Re: [CMake] Imported targets and include ordering

[Roger Leigh]

On 11/08/2016 16:24, rle...@codelibre.net wrote:

I've come across an odd situation where I'm unsure what the most
portable and recommended solution would be.

I'm linking a program against the CURL and ICU libraries.  CURL has
traditional variables for the includes and libraries; ICU has imported
targets.

In FindICU:
  set_target_properties(${_ICU_imported_target} PROPERTIES
INTERFACE_INCLUDE_DIRECTORIES "${ICU_INCLUDE_DIR}")

In my code:

find_package(CURL)
find_package(ICU COMPONENTS uc data)
[...]
list(APPEND libxerces_c_DEPS ${CURL_LIBRARIES})
include_directories(${CURL_INCLUDE_DIRS})
list(APPEND libxerces_c_DEPS ICU::uc ICU::data)

And the resulting includes on the compiler invocation:

/usr/bin/CC   -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -I.
-I/tmp/b2/xerces-source/src -Isrc -I/tmp/b2/xerces-source/tests -isystem
/tmp/b2/superbuild-install/include -msse2 -MD -MT
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o -MF
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o.d -o
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o -c
/tmp/b2/xerces-source/tests/src/XSValueTest/XSValueTest.cpp

The problem is this:
CURL is in /usr/local/include
ICU v55 is in /usr/local/include
ICU v57 is in /tmp/b2/superbuild-install/include with its libs in
/tmp/b2/superbuild-install/lib


Sorry, I noticed that the compiler invocation was from the wrong source 
file; it should have -I/usr/local/include right at the start, then 
-isystem /tmp/b2/superbuild-install/include at the end as above.


--

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] Mantis to GitLab - converter?

[Robert Maynard]

Hi tonka,

We (Ben) wrote a conversion tool that we use to convert mantis issues
over to gitlab. You can find the project at:
https://gitlab.kitware.com/utils/mantis-to-gitlab

It has an Apache 2.0 license.

On Thu, Aug 11, 2016 at 9:31 AM, tonka tonka  wrote:
> Dear Kitware,
>
> First of all, thank for such great tools like cmake, really enjoy your
> tools.
>
>  I’ve saw that you are using GitLab as your sourcecode system. Also I’ve see
> that you have used Mantis as bugtracker before. I have made the same
> transition to GitLab, but I’ve not transferred the Manits issues yet.
>
>  My question is, how do you import the Mantis issue, do you write a tool
> yourself?
>
> If yes, is it opensource/free to use for this onetime convert from Mantis to
> GitLab.
>
> If no, is there any tool which have made the job?
>
> Thanks in advance
>
> Tonka
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-613-gf203694

[Brad King]

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

The branch, master has been updated
   via  f203694bb848e7a4bd2c623348053532b1b4e589 (commit)
   via  3a5f609cbb4ae63fca1eb87918767a4296d16e5f (commit)
   via  f582dba6664e5ea814f3b33c71ae4d83db17b996 (commit)
   via  74f0d4abcd8de84283858fe144772e688669e46a (commit)
   via  94c29976d0020b48a5c565234b71f8f6abaf08be (commit)
  from  3c4d2e84d2659459eeecd2b9da0fceb22a2fb852 (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=f203694bb848e7a4bd2c623348053532b1b4e589
commit f203694bb848e7a4bd2c623348053532b1b4e589
Merge: 3c4d2e8 3a5f609
Author: Brad King 
AuthorDate: Thu Aug 11 13:48:37 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Aug 11 13:48:37 2016 -0400

Merge topic 'cmCryptoHash-raw-digest'

3a5f609c cmCryptoHash: New ByteHash methods that return a byte vector
f582dba6 cmCryptoHash: Return byte vector from internal Finalize method
74f0d4ab cmCryptoHash: New byte hash to string function
94c29976 cmCryptoHash: Documentation comments


---

Summary of changes:
 Source/cmCryptoHash.cxx |  111 +--
 Source/cmCryptoHash.h   |   42 --
 2 files changed, 117 insertions(+), 36 deletions(-)


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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1236-g7dbdc86

[Brad King]

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  7dbdc8675b1235e2f416c05dbb9b00f07c956ade (commit)
   via  f203694bb848e7a4bd2c623348053532b1b4e589 (commit)
   via  3c4d2e84d2659459eeecd2b9da0fceb22a2fb852 (commit)
  from  df237068ee8618e19354d2fec3f0f99b5a9fee85 (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=7dbdc8675b1235e2f416c05dbb9b00f07c956ade
commit 7dbdc8675b1235e2f416c05dbb9b00f07c956ade
Merge: df23706 f203694
Author: Brad King 
AuthorDate: Thu Aug 11 13:48:52 2016 -0400
Commit: Brad King 
CommitDate: Thu Aug 11 13:48:52 2016 -0400

Merge branch 'master' into next


---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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

Re: [CMake] Bash on ubuntu on windows as target

[Tiago Macarios]

Well what I was trying to do was to actually have a target inside the
windows build that would trigger the linux build so to build both at the
same time. imagine you have a VS project one of the "projects" would be the
linux build. So as long as the build folder is different I could have both
building in sync everytime. Get the idea?

If I just do a full build inside bash everything works great =)

On Wed, Aug 10, 2016 at 11:23 PM, <"Máté Ferenc Nagy-Egri via CMake
 wrote:

> +1 for the initiative. Wouldn’t it make more sense however to make it a
> CMAKE_SYSTEM_NAME? If I remember correctly that’s how MinGW works, and this
> should be something very similar.
>
>
>
>
>
> *Feladó: *Tiago Macarios 
> *Elküldve: *2016. augusztus 11., csütörtök 1:51
> *Címzett: *CMake ML 
> *Tárgy: *[CMake] Bash on ubuntu on windows as target
>
>
>
> Hi All,
>
>
>
> Windows 10 anniversary edition comes with support to execute Linux
> binaries. I have been trying to use it with one of our projects, but I have
> been getting a weird error. Maybe someone can help me?
>
>
>
> The target is pretty simple:
>
>
>
> set(BASH "C:\\Windows\\System32\\bash.exe")
>
> set(ARGS "--help")
>
> add_custom_target(linux ${BASH} ${ARGS})
>
>
>
> If I then build that project in visual studio (with some extra verbosity)
> I get:
>
>
>
> Target "CustomBuild" in file "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\
> v4.0\V140\Microsoft.CppCommon.targets" from project
> "C:\_Working\delegate\build\linux.vcxproj" (target
> "_BuildGenerateSourcesAction" depends on it):
>
> Using "CustomBuild" task from assembly "C:\Program Files
> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Build.
> CppTasks.Common.dll".
>
> Task "CustomBuild"
>
>   Write Tracking Logs:
>
>x64\Debug\linux\linux.tlog\custombuild.write.1.tlog
>
>   Read Tracking Logs:
>
>x64\Debug\linux\linux.tlog\custombuild.read.1.tlog
>
>   No output for C:\_WORKING\DELEGATE\BUILD\CMAKEFILES\
> 3FA5525E877A7559336C7D412E1B43B0\LINUX.RULE|C:\_WORKING\DELEGATE\CMAKELISTS.TXT
> was found in the tracking log; source compilation required.
>
>   C:\_Working\delegate\CMakeLists.txt will be compiled as it was not
> found in the tracking log.
>
>   
> C:\_Working\delegate\build\CMakeFiles\3fa5525e877a7559336c7d412e1b43b0\linux.rule
> will be compiled as it was not found in the tracking log.
>
>   setlocal
>
>   "C:\Program Files (x86)\CMake\bin\cmake.exe" -HC:/_Working/delegate
> -BC:/_Working/delegate/build --check-stamp-file C:\_Working\delegate\build\
> CMakeFiles\generate.stamp
>
>   if %errorlevel% neq 0 goto :cmEnd
>
>   :cmEnd
>
>   endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
>
>   :cmErrorLevel
>
>   exit /b %1
>
>   :cmDone
>
>   if %errorlevel% neq 0 goto :VCEnd
>
>   setlocal
>
>   C:\Windows\System32\bash.exe --help
>
>   if %errorlevel% neq 0 goto :cmEnd
>
>   :cmEnd
>
>   endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
>
>   :cmErrorLevel
>
>   exit /b %1
>
>   :cmDone
>
>   if %errorlevel% neq 0 goto :VCEnd
>
>   Building Custom Rule C:/_Working/delegate/CMakeLists.txt
>
>   CMake does not need to re-run because 
> C:\_Working\delegate\build\CMakeFiles\generate.stamp
> is up-to-date.
>
> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\
> v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe"
> exited with code -1073740791.
>
> Done executing task "CustomBuild" -- FAILED.
>
> Done building target "CustomBuild" in project "linux.vcxproj" -- FAILED.
>
>
>
>
>
> The command line seems correct. If I just copy it to the windows prompt it
> works fine:
>
>
>
> C:\Users\tmc>  C:\Windows\System32\bash.exe --help
>
> GNU bash, version 4.3.11(1)-release-(x86_64-pc-linux-gnu)
>
> Usage:  /bin/bash [GNU long option] [option] ...
>
> /bin/bash [GNU long option] [option] script-file ...
>
> GNU long options:
>
> --debug
>
> --debugger
>
> --dump-po-strings
>
> --dump-strings
>
> --help
>
> --init-file
>
> --login
>
> --noediting
>
> --noprofile
>
> --norc
>
> --posix
>
> --rcfile
>
> --restricted
>
> --verbose
>
> --version
>
> Shell options:
>
> -ilrsD or -c command or -O shopt_option (invocation only)
>
> -abefhkmnptuvxBCHP or -o option
>
> Type `/bin/bash -c "help set"' for more information about shell options.
>
> Type `/bin/bash -c help' for more information about shell builtin commands.
>
> Use the `bashbug' command to report bugs.
>
>
>
>
>
> I also tried to use it from the visual studio "external tools" and it
> seems to work. So I am not sure what is going on. Is there a way to debug
> custom_targets?
>
>
>
> In case anyone tries the example above on a 64 bit machine: You will need
> to copy bash.exe from system32 to syswow64 since VS is 32 bits.
>
>
>
> Tiago
>
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep 

[CMake] Imported targets and include ordering

[rleigh]

I've come across an odd situation where I'm unsure what the most 
portable and recommended solution would be.


I'm linking a program against the CURL and ICU libraries.  CURL has 
traditional variables for the includes and libraries; ICU has imported 
targets.


In FindICU:
  set_target_properties(${_ICU_imported_target} PROPERTIES
INTERFACE_INCLUDE_DIRECTORIES "${ICU_INCLUDE_DIR}")

In my code:

find_package(CURL)
find_package(ICU COMPONENTS uc data)
[...]
list(APPEND libxerces_c_DEPS ${CURL_LIBRARIES})
include_directories(${CURL_INCLUDE_DIRS})
list(APPEND libxerces_c_DEPS ICU::uc ICU::data)

And the resulting includes on the compiler invocation:

/usr/bin/CC   -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -I. 
-I/tmp/b2/xerces-source/src -Isrc -I/tmp/b2/xerces-source/tests -isystem 
/tmp/b2/superbuild-install/include -msse2 -MD -MT 
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o -MF 
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o.d -o 
tests/CMakeFiles/XSValueTest.dir/src/XSValueTest/XSValueTest.cpp.o -c 
/tmp/b2/xerces-source/tests/src/XSValueTest/XSValueTest.cpp


The problem is this:
CURL is in /usr/local/include
ICU v55 is in /usr/local/include
ICU v57 is in /tmp/b2/superbuild-install/include with its libs in 
/tmp/b2/superbuild-install/lib


CMAKE_PREFIX_PATH is set appropriately, and all the Find module checks 
are correct.  The problem is that the ICU INTERFACE_INCLUDE_DIRECTORIES 
is treated as a system include.  This would be OK, if it were not for 
the fact that the CURL includes are placed before it.


The problem is that it's not a system path.  However, the CURL path 
*is*.  And this leads to it building against the ICU55 headers, and then 
failing to link against the ICU57 libraries.  But that's just the 
situation on this specific (FreeBSD) system; the situation could be 
reversed on another with a locally built CURL and a system ICU and CURL.


I see that I could use NO_SYSTEM_FROM_IMPORTED for the imported target, 
and/or use BEFORE|AFTER SYSTEM with [target_]include_directories.  
However, none of these feel appropriate.  They would require knowledge I 
don't have as the cmake script author--either of these libraries could 
be using system or non-system paths; I don't have the foreknowledge to 
make that determination.


How could an end user override what are system paths and what are not 
without hand-editing the script?


It seems (being naive) that the hardcoded behaviour of treating 
INTERFACE_INCLUDE_DIRECTORIES as system includes isn't a universally 
useful default, and while I can override the behaviour, that's a 
explicit action on the part of the script author, and might be 
inappropriate for the user's system.  Whether a path is a system include 
or not seems to be something the end user should be able to tune, since 
the script author and cmake find module authors have no idea what the 
local situation is for any arbitrary system.  For example, it wouldn't 
hurt for cmake to "know" that /usr/local/include is a system path as a 
built-in default, and allow additional paths to be added, and then if a 
random find module adds it such that it's used by a target as a 
non-system include we know we can ignore it and just use it as a system 
include instead.  Unless I'm misunderstanding the situation and making 
this work is already possible.



Thanks,
Roger
--

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] Super builds and export with Namespace

[Miller Henry]

I have a few different cmake based projects that depend on each other (as a 
tree, no circular dependencies).  Mostly this works great, but a few people 
have expressed interested in a superbuild which builds everything together for 
various purposes.  I can make this work with ExternalProject, but that isn't a 
useful solution for IDE users.  I'm trying to use add_subdirectory and running 
into a problem with namespaces in my export files

Currently projectA has
   EXPORT(projectA NameSpace ProjectA_)
Which works great, when projectB wants to link to a library in projectA it is 
just FIND_PACKAGE(ProjectA) then TARGET_LINK_LIBRARIES(lib 
ProjectA_LibraryName).  Simple enough without superbuilds.

When I get to a superbuild though I don't know how to handle this.  It is easy 
to do write some sort of FindProjectA.cmake or ProjectAConfig.cmake file to 
make the FIND_PACKAGE work in projectB. However I don't know how to get a 
ProjectA_LibraryName target that I can link to, the superbuild only knows about 
LibraryName without the namespace.

The only idea I can think of is in the superbuild have a bunch of ADD_LIBRARY 
(ProjectA_LibraryName ALIAS LibraryName) lines hard coded. This means I have to 
maintain that file though which I don't like. Does anyone have a better idea?


-- 

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] Mantis to GitLab - converter?

[tonka tonka]

Dear Kitware,

First of all, thank for such great tools like cmake, really enjoy your
tools.

 I’ve saw that you are using GitLab as your sourcecode system. Also I’ve
see that you have used Mantis as bugtracker before. I have made the same
transition to GitLab, but I’ve not transferred the Manits issues yet.

 My question is, how do you import the Mantis issue, do you write a tool
yourself?

If yes, is it opensource/free to use for this onetime convert from Mantis
to GitLab.

If no, is there any tool which have made the job?

Thanks in advance

Tonka
-- 

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] Use GLOB to generate filelist for install package

[Patrik Lehmann]

Thank You both. Now it works!


Am 11.08.2016 um 11:29 schrieb Stuermer, Michael SP/HZA-ZSEP:



-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Patrik
Lehmann
Sent: Thursday, August 11, 2016 11:04 AM
To: cmake@cmake.org
Subject: [CMake] Use GLOB to generate filelist for install package

Hello,

I try to use GLOB to collect the files for my install package, but 
unfortunately I
got the message

'file INSTALL cannot find
"C:/Project/include/test1.h;C:/Project/include/test2.h;...'

My code:

FILE(GLOB MY_INCLUDES_H "${PROJECT_SOURCE_DIR}/include/*.h")

INSTALL(FILES "${MY_INCLUDES_H}"
   DESTINATION "include"
   COMPONENT CPP_INCLUDES)


Remove the '"' around the list of headers in your install command:

INSTALL(FILES ${MY_INCLUDES_H} ...

instead of

INSTALL(FILES "${MY_INCLUDES_H}" ...

The quotes result in the list to be expanded in only one long string instead of 
a list of strings. CMake thinks you are only installing one file with a vry 
long name.
  


Is there a way to collect the files this way or is it needed to add every file
manually?

Kind Regards,
Patrik Lehmann
--

Powered by www.kitware.com

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

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

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

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

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




-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Use GLOB to generate filelist for install package

[Stuermer, Michael SP/HZA-ZSEP]

> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Patrik
> Lehmann
> Sent: Thursday, August 11, 2016 11:04 AM
> To: cmake@cmake.org
> Subject: [CMake] Use GLOB to generate filelist for install package
> 
> Hello,
> 
> I try to use GLOB to collect the files for my install package, but 
> unfortunately I
> got the message
> 
> 'file INSTALL cannot find
> "C:/Project/include/test1.h;C:/Project/include/test2.h;...'
> 
> My code:
> 
> FILE(GLOB MY_INCLUDES_H "${PROJECT_SOURCE_DIR}/include/*.h")
> 
> INSTALL(FILES "${MY_INCLUDES_H}"
>   DESTINATION "include"
>   COMPONENT CPP_INCLUDES)
> 

Remove the '"' around the list of headers in your install command:

INSTALL(FILES ${MY_INCLUDES_H} ...

instead of 

INSTALL(FILES "${MY_INCLUDES_H}" ...

The quotes result in the list to be expanded in only one long string instead of 
a list of strings. CMake thinks you are only installing one file with a vry 
long name.
 

> 
> Is there a way to collect the files this way or is it needed to add every file
> manually?
> 
> Kind Regards,
> Patrik Lehmann
> --
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Use GLOB to generate filelist for install package

[CHEVRIER, Marc]

Remove the quotes around the variable MY_INCLUDES_H in the INSTALL command 
because this is a list. Using quotes, you pass it as a single string.

On 11/08/16 11:03, "CMake on behalf of Patrik Lehmann"  wrote:

Hello,

I try to use GLOB to collect the files for my install package, but 
unfortunately I got the message

'file INSTALL cannot find 
"C:/Project/include/test1.h;C:/Project/include/test2.h;...'

My code:

FILE(GLOB MY_INCLUDES_H "${PROJECT_SOURCE_DIR}/include/*.h")

INSTALL(FILES "${MY_INCLUDES_H}"
  DESTINATION "include"
  COMPONENT CPP_INCLUDES)


Is there a way to collect the files this way or is it needed to add 
every file manually?

Kind Regards,
Patrik Lehmann
-- 

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] Use GLOB to generate filelist for install package

[Patrik Lehmann]

Hello,

I try to use GLOB to collect the files for my install package, but 
unfortunately I got the message


'file INSTALL cannot find 
"C:/Project/include/test1.h;C:/Project/include/test2.h;...'

My code:

FILE(GLOB MY_INCLUDES_H "${PROJECT_SOURCE_DIR}/include/*.h")

INSTALL(FILES "${MY_INCLUDES_H}"
 DESTINATION "include"
 COMPONENT CPP_INCLUDES)


Is there a way to collect the files this way or is it needed to add 
every file manually?


Kind Regards,
Patrik Lehmann
--

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] Bash on ubuntu on windows as target

[Máté Ferenc Nagy-Egri via CMake]

+1 for the initiative. Wouldn’t it make more sense however to make it a 
CMAKE_SYSTEM_NAME? If I remember correctly that’s how MinGW works, and this 
should be something very similar.


Feladó: Tiago Macarios-- 

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