On 2013-12-03 11:59, Brad King wrote:
I'd like to avoid new uses of define_property if possible. It
is a legacy from the old builtin documentation system.
Sorry to go off on a tangent, but this triggered a question in my mind...
I have a wrapping utility file that declares some (CMake) helper
functions/macros to automatically generate Python bindings for a C++
library. There is some dependency logic that uses custom target
properties under the hood.
Right now I am using define_property to declare those. Should I (can I)
not do that?
Loosely related: is there a way to make export() and install(EXPORT) set
these properties for exported targets?
--
Matthew
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
