Hi,
I've pushed an export-policy topic to my clone which attempts to disallow
including the result of the export command. This is part of making it
possible to make export() be executed at generate time in the future.
There are limitations to my topic already. For example, it doesn't warn if
On 2013-06-28 08:40, Brad King wrote:
What about the APPEND mode of export? Do you plan to try to
collect all the appended pieces together, all delayed until
generate time?
That would be great if you could! One of my big gripes with export() is
how much less elegant it is generating a
On 2013-06-28 09:06, Stephen Kelly wrote:
Brad King wrote:
Perhaps the policy could also disallow the
APPEND mode altogether. IIRC I've participated in discussion
in the past about how APPEND is a bad approach anyway.
I've never used it, but then I've never used export() except in unit tests
On 6/28/2013 12:27 PM, Matthew Woehlke wrote:
To me it would make much more sense if export() was more like
install(EXPORT), where one declares at the point of the add_library()
the desire to export a target, which adds to a list the CMake keeps
track of internally in order to generate an
On 6/28/2013 12:49 PM, Brad King wrote:
On 6/28/2013 12:27 PM, Matthew Woehlke wrote:
To me it would make much more sense if export() was more like
install(EXPORT), where one declares at the point of the add_library()
the desire to export a target, which adds to a list the CMake keeps
