On Mon, Jul 20, 2015 at 16:01:29 -0400, Clifford Yapp wrote: > I've put both in and added the man pages - progress so far attached. > Are there any other docs that list target properties, or are the rst > files the canonical sources for property docs?
Those should be it. > For testing these properties, what would you suggest? They're > intended to report local configure-time absolute paths, which can't be > hard coded... is it enough to check them to make sure they're not > empty or is there something more robust that could be devised?" They should end with the path under the CMake source tree at least (I assume they are absolute?). Try matching this regex: .*/Testing/RunCMake/get_property possibly? You can also put the test under an add_subdirectory() call as well. Other things that come to mind: symlink resolution[1] and how relative paths are handled (if they aren't absolute). Thanks, --Ben [1]My setup is: $HOME/code/cmake -> depot/group-bld/cmake What is the difference if $PWD is $HOME/code/cmake/build versus $HOME/code/depot/group-bld/cmake/build? I doubt this is something that fits in the test suite, but a double test would be good at least. -- 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