[CMake] Running CxxTest fails on Fedora 24
The Fedora /usr/bin/cxxtestgen script calls /usr/bin/python3. NOT python2 or python. CMake runs /usr/bin/python /usr/bin/cxxtestgen which is linked to python2, and the script fails. I don't quite understand why CMake feels the need to call it explicitly with the Python interpreter that it found instead of using the shebang. Maybe Windows? Eh. I am fixing it in my script by doing this: > FIND_PACKAGE(PythonInterp 3 QUIET) > FIND_PACKAGE(CxxTest) I thought this might help anyone else hitting this. -- Knowledge is Power -- Power Corrupts Study Hard -- Be Evil -- 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] Need fix bid to build CMake generated Library.
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] Imported targets and include ordering
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?
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
Re: [CMake] Bash on ubuntu on windows as target
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 messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/C
[CMake] Imported targets and include ordering
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
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?
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
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
> -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
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
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
