Re: [cmake-developers] Header-only library targets
I've recently switched from CMake 2.8.12 to 3.2, full of enthusiasm that header-only libraries would now be better supported through the INTERFACE option/target. However, the support for header-only libraries isn't really great, in particular if you're using an IDE like Visual Studio. The main problem is that if you define an INTERFACE target, there's no way to specify headers, and they won't show up in IDEs. There's workarounds with a custom target, but that's not really great for example to set dependencies, populate the include directory of the library or to INSTALL the target. i'm sometimes using the workaround of generating a dummy cpp file and use a static library instead of an interface library ... ugly hack, but allows to populate msvc/xcode/qtcreator projects ... -- 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 0015648]: FindXercesC.cmake does not work on Windows
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15648 == Reported By:Martin Baute Assigned To: == Project:CMake Issue ID: 15648 Category: Modules Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-07-13 04:38 EDT Last Modified: 2015-07-13 04:38 EDT == Summary:FindXercesC.cmake does not work on Windows Description: The FindXercesC module shipping with CMake is rather simple. It looks for the Xerces-C library using this line: find_library( XercesC_LIBRARY xerces-c DOC Xerces-C++ libraries ) This does not work on Windows -- here, the Xerces-C library is named xerces-c_3.lib (or ...-c_3D.lib for the debug build), making FindXercesC.cmake fail with XercesC_LIBRARY-NOTFOUND. Suggested fix would be using this line: find_library( XercesC_LIBRARY NAMES xerces-c xerces-c_3 xerces-c_2 DOC Xerces-C++ libraries ) == Issue History Date ModifiedUsername FieldChange == 2015-07-13 04:38 Martin Baute 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] [CMake] Problem with CMake 3.3.0-rc3
On Sat, Jul 11, 2015 at 5:07 AM, Stephen Kelly steve...@gmail.com wrote: Brad King wrote: Steve, please take a look. It looks like the cmState methods RemoveUserDefinedCommands and RenameCommand need to work better together. This needs to be fixed for 3.3. Fixed with http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f2ee169d cmState: Restore renamed commands on cleanup Confirmed in rc4 - thanks! CY -- 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] cmake.exe parameters and system command line length limit
You don't. It's just another way to specify the command line arguments, but as a single command line argument instead of dozens or hundreds. It's a mechanism for you to avoid the command line length limit. Wasn't that your question...? On Mon, Jul 13, 2015 at 2:01 PM, Robert Goulet robert.gou...@autodesk.com wrote: Hi David, That option looks interesting. How do we populate it with the other CMake cache values that are originally set by CMake and not by our command line options? Thanks. -Original Message- From: David Cole [mailto:dlrd...@aol.com] Sent: Monday, July 13, 2015 1:56 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] cmake.exe parameters and system command line length limit You could use the -C command line option to pass in the name of a file containing initial cache values. See the -C initial-cache section at the top of this documentation section: http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html#options The format of the file is just a bunch of set(... CACHE ...) commands. Read the doc paragraph carefully, and give it a try. Maybe somebody else can point to a valid example of a live -C file being used out there on the Internet. HTH, David C. On Mon, Jul 13, 2015 at 1:44 PM, Robert Goulet robert.gou...@autodesk.com wrote: Hi all, We use a custom script to handle which parameters we set to cmake.exe on Windows. It sets CMake values based on the options provided to this script, using the -D cmake parameter. This works well, but recently we’ve reached the limit on how many characters we can set to a single system command line (cmd.exe), because our number of options is growing. Is there a work-around for this using CMake, or perhaps feed CMake parameters from a file rather than from command-line parameters? i.e. “cmake.exe params.txt” ? Thanks! -- 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 -- 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] cmake.exe parameters and system command line length limit
Hi David, That option looks interesting. How do we populate it with the other CMake cache values that are originally set by CMake and not by our command line options? Thanks. -Original Message- From: David Cole [mailto:dlrd...@aol.com] Sent: Monday, July 13, 2015 1:56 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] cmake.exe parameters and system command line length limit You could use the -C command line option to pass in the name of a file containing initial cache values. See the -C initial-cache section at the top of this documentation section: http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html#options The format of the file is just a bunch of set(... CACHE ...) commands. Read the doc paragraph carefully, and give it a try. Maybe somebody else can point to a valid example of a live -C file being used out there on the Internet. HTH, David C. On Mon, Jul 13, 2015 at 1:44 PM, Robert Goulet robert.gou...@autodesk.com wrote: Hi all, We use a custom script to handle which parameters we set to cmake.exe on Windows. It sets CMake values based on the options provided to this script, using the -D cmake parameter. This works well, but recently we’ve reached the limit on how many characters we can set to a single system command line (cmd.exe), because our number of options is growing. Is there a work-around for this using CMake, or perhaps feed CMake parameters from a file rather than from command-line parameters? i.e. “cmake.exe params.txt” ? Thanks! -- 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 -- 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] Header-only library targets
Yeah, we all do such ugly hack for header project. However it's time to change this situation right? I think current version of interface library is already closed to what header library project wants, through maybe original design goal was not going to do so, but I couldn’t see any scene to use interface library except for header-only library target. Yes, I’m badly want this feature, because AFAK there doesn’t exist an open source, cross-platform build system yet to support header-only target in a graceful way. CMake already did many things right as a C/C++ build system, compared to many other ones, I hope Make could be the first one fulfill this. 在 2015年7月13日，下午5:38，Tim Blechmann tim at klingt.org 写道： I've recently switched from CMake 2.8.12 to 3.2, full of enthusiasm that header-only libraries would now be better supported through the INTERFACE option/target. However, the support for header-only libraries isn't really great, in particular if you're using an IDE like Visual Studio. The main problem is that if you define an INTERFACE target, there's no way to specify headers, and they won't show up in IDEs. There's workarounds with a custom target, but that's not really great for example to set dependencies, populate the include directory of the library or to INSTALL the target. i'm sometimes using the workaround of generating a dummy cpp file and use a static library instead of an interface library ... ugly hack, but allows to populate msvc/xcode/qtcreator projects ... -- 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.exe parameters and system command line length limit
Hi all, We use a custom script to handle which parameters we set to cmake.exe on Windows. It sets CMake values based on the options provided to this script, using the -D cmake parameter. This works well, but recently we've reached the limit on how many characters we can set to a single system command line (cmd.exe), because our number of options is growing. Is there a work-around for this using CMake, or perhaps feed CMake parameters from a file rather than from command-line parameters? i.e. cmake.exe params.txt ? Thanks! -- 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] cmake.exe parameters and system command line length limit
You could use the -C command line option to pass in the name of a file containing initial cache values. See the -C initial-cache section at the top of this documentation section: http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html#options The format of the file is just a bunch of set(... CACHE ...) commands. Read the doc paragraph carefully, and give it a try. Maybe somebody else can point to a valid example of a live -C file being used out there on the Internet. HTH, David C. On Mon, Jul 13, 2015 at 1:44 PM, Robert Goulet robert.gou...@autodesk.com wrote: Hi all, We use a custom script to handle which parameters we set to cmake.exe on Windows. It sets CMake values based on the options provided to this script, using the -D cmake parameter. This works well, but recently we’ve reached the limit on how many characters we can set to a single system command line (cmd.exe), because our number of options is growing. Is there a work-around for this using CMake, or perhaps feed CMake parameters from a file rather than from command-line parameters? i.e. “cmake.exe params.txt” ? Thanks! -- 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 -- 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] Extended Nsight Tegra support for CMake
I've improved the patch according to the Brad's and Dmitry's comments - namely: 1. Improved the documentation for a few target properties. 2. Removed the explicit toolchain file for Nsight Tegra generator test. 3. Improved the generator heuristics for NsightTegraProjectRevisionNumber attribute. Thanks, -Mikhail -Original Message- From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Mikhail Filimonov Sent: 9 июля 2015 г. 18:43 To: Brad King Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] [PATCH] Extended Nsight Tegra support for CMake Thanks for your feedback, Brad From: Brad King [mailto:brad.k...@kitware.com] Sent: 9 июля 2015 г. 18:02 We'd like to keep testing the default behavior without an explicit toolchain file. Also we need to be independent of the toolsets that happen to be available on the system where the test runs, so we should avoid hard-coding a toolset name if possible. Is this part of the patch needed to test everything else? If so, please look at adding more test cases for the new combinations (which can just be more builds of the same test source tree). That's more like a demonstration sample that will show the developers how the various Nsight Tegra project properties could be defined via the various CMake properties even if not directly related to Android - i.e. C_STANDARD and CMAKE_GENERATOR_TOOLSET Currently where's no samples directory in CMake source tree - so I've slightly reworked the existing test case. Maybe you could propose a better way to deliver that sample? Thanks, -Mikhail --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- ExtendedNsightTegraSupport2.patch Description: ExtendedNsightTegraSupport2.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-developers] [PATCH] Extended Nsight Tegra support for CMake
I've reviewed the patch and tried it locally - looks good. -Dmitry -Original Message- From: Mikhail Filimonov Sent: Monday, July 13, 2015 7:45 PM To: cmake-developers@cmake.org Subject: RE: [cmake-developers] [PATCH] Extended Nsight Tegra support for CMake I've improved the patch according to the Brad's and Dmitry's comments - namely: 1. Improved the documentation for a few target properties. 2. Removed the explicit toolchain file for Nsight Tegra generator test. 3. Improved the generator heuristics for NsightTegraProjectRevisionNumber attribute. Thanks, -Mikhail -Original Message- From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Mikhail Filimonov Sent: 9 июля 2015 г. 18:43 To: Brad King Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] [PATCH] Extended Nsight Tegra support for CMake Thanks for your feedback, Brad From: Brad King [mailto:brad.k...@kitware.com] Sent: 9 июля 2015 г. 18:02 We'd like to keep testing the default behavior without an explicit toolchain file. Also we need to be independent of the toolsets that happen to be available on the system where the test runs, so we should avoid hard-coding a toolset name if possible. Is this part of the patch needed to test everything else? If so, please look at adding more test cases for the new combinations (which can just be more builds of the same test source tree). That's more like a demonstration sample that will show the developers how the various Nsight Tegra project properties could be defined via the various CMake properties even if not directly related to Android - i.e. C_STANDARD and CMAKE_GENERATOR_TOOLSET Currently where's no samples directory in CMake source tree - so I've slightly reworked the existing test case. Maybe you could propose a better way to deliver that sample? Thanks, -Mikhail --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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] [ANNOUNCE] CMake 3.3.0-rc4 is now ready!
I am proud to announce the fourth CMake 3.3 release candidate. Sources and binaries are available at: http://www.cmake.org/download/ Documentation is available at: http://www.cmake.org/cmake/help/v3.3 Release notes appear below and are also published at http://www.cmake.org/cmake/help/v3.3/release/3.3.html Some of the more significant features of CMake 3.3 are: * The if() command learned a new IN_LIST operator that evaluates to true if a given element is contained in a named list. * The add_dependencies() command learned to allow dependencies to be added to *interface libraries*. Dependencies added to an interface library are followed transitively in its place since the target itself does not build. * The find_library(), find_path(), and find_file() commands now search in installation prefixes derived from the PATH environment variable. * The LANG_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN target properties now affect compilation in sources of all target types. See policy CMP0063. * A LANG_INCLUDE_WHAT_YOU_USE target property and supporting CMAKE_LANG_INCLUDE_WHAT_YOU_USE variable were introduced to tell the *Makefile Generators* and the Ninja generator to run include- what-you-use along with the compiler for C and CXX languages. Deprecated and Removed Features: * The ctest_build() and build_command() commands no longer tell make tools to ignore errors with the -i option. Previously this was done for *Makefile Generators* but not others. See policy CMP0061. * The Visual Studio 7 generator (.NET 2002) is now deprecated and will be removed in a future version of CMake. * The Visual Studio 6 generator is now deprecated and will be removed in a future version of CMake. * The add_definitions() command no longer causes a DEFINITIONS directory property to be populated. See policy CMP0059. CMake 3.3 Release Notes *** Changes made since CMake 3.2 include the following. New Features Generators -- * The *Makefile Generators* now add .DELETE_ON_ERROR to the makefiles that contain the actual build rules for files on disk. This tells GNU make to remove rule outputs when their recipe modifies an output but fails. * The *Visual Studio Generators* learned to support .xaml source files and automatically associate them with corresponding .h and .cpp sources. * A new experimental Green Hills MULTI generator was added on Windows. Green Hills MULTI is an IDE for embedded real-time systems. Commands * The add_dependencies() command learned to allow dependencies to be added to *interface libraries*. Dependencies added to an interface library are followed transitively in its place since the target itself does not build. * The execute_process() command learned to support specifying the same file for OUTPUT_FILE and ERROR_FILE. * The file(GLOB) and file(GLOB_RECURSE) commands learned a new LIST_DIRECTORIES bool option to specify whether the glob result should include directories. * The find_library(), find_path(), and find_file() commands now search in installation prefixes derived from the PATH environment variable. * The if() command learned a new IN_LIST operator that evaluates to true if a given element is contained in a named list. * The install(EXPORT) and export() commands learned to export targets that populate the INTERFACE_SOURCES target property. * The install(TARGETS) command learned to support generator expressions in the DESTINATION value. Variables - * The version of some Fortran compilers is now detected and stored in the CMAKE_Fortran_COMPILER_VERSION variable. * The *Visual Studio Generators* learned a new CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD option to put the INSTALL target in the default build of a solution (.sln) file. Properties -- * A CROSSCOMPILING_EMULATOR target property and supporting CMAKE_CROSSCOMPILING_EMULATOR variable were introduced to allow target platform binaries to run on the host during cross compiling. * A LANG_INCLUDE_WHAT_YOU_USE target property and supporting CMAKE_LANG_INCLUDE_WHAT_YOU_USE variable were introduced to tell the *Makefile Generators* and the Ninja generator to run include- what-you-use along with the compiler for C and CXX languages. * The LANG_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN target properties now affect compilation in sources of all target types. See policy CMP0063. * The XCODE_ATTRIBUTE_an-attribute target property learned to support generator expressions. Modules --- * The CheckFortranCompilerFlag module was introduced to check Fortran compiler flags, much like the CheckCCompilerFlag module already does for C. * The ExternalData module learned a new ExternalData_NO_SYMLINKS option to disable use of symbolic links to populate the real data files and use copies instead. * The ExternalData module learned a new RECURSE: option
[cmake-developers] OSX - Application bundle and private frameworks?
Hi,
I am trying to copy a private framework into an application bundle:
- I can find the frameworks properly with the find_library,
- I put those frameworks in the add_executable command
add_executable(
MACOSX_BUNDLE
### source files ...
### frameworks
${sbigudFramework}
${fcCamFramework}
)
target_link_libraries( [...] ${sbigudFramework} ${fcCamFramework})
- and I specify the location of those frameworks within the application
bundle:
set_source_files_properties(${fcCamFramework} PROPERTIES
MACOSX_PACKAGE_LOCATION Frameworks)
set_source_files_properties(${sbigudFramework} PROPERTIES
MACOSX_PACKAGE_LOCATION Frameworks)
The problem is the following:
- Everything works fine with XCode, I have the full content of the
frameworks at the specified location
- When I use the Makefile generator, I have only one file per framework
instead of the directory and the framework content:
ls -al .app/Contents/Frameworks/
total 0
drwxr-xr-x 4 raffi staff 136 Jul 14 00:26 .
drwxr-xr-x 6 raffi staff 204 Jul 14 00:08 ..
-rwxr-xr-x 1 raffi staff0 Jul 14 00:26 SBIGUDrv.framework
-rwxr-xr-x 1 raffi staff0 Jul 14 00:26 fcCamFw.framework
Am I doing something wrong? I am using cmake 3.0.2 3.2.3 / OSX 10.10.
Best,
Raffi
--
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] Wrapping functions in CMake
On Thu, Jul 9, 2015 at 7:35 PM, Clifford Yapp cliffy...@gmail.com wrote: [...] 2. Second we maintain global lists of all exec, library, and custom targets. This allows us to run timestamping build targets that run at the very beginning and very end of the build process, by setting up target dependences for the beginning and ending timestamp targets. The ending time stamp target must depend on every other build target, and the beginning timestamp is depended on by every other build target. To do this, as far as I know, we need lists of all build targets so we can set this up with the add_dependencies command. In our project suite setup, we need a list of all existing targets as well. Having access to it from CMakeLists would be invaluable. Petr -- 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
