[cmake-developers] Listing source-tree files encountered

Clifford Yapp cliffyapp at gmail.com
Sat Jul 18 00:06:55 EDT 2015


On Fri, Jul 17, 2015 at 11:50 AM, Brad King <brad.king at kitware.com> wrote:
> On 07/15/2015 10:38 PM, Clifford Yapp wrote:
>> Lists that contains a verbatim collection of all path specifiers,
>> regardless of form, that are passed to the various add_* targets would
>> be enough, I think - it'd then be up to our own CMake logic to make
>> sense of it all.  I'm not hoping to push our whole
>> in-src-dir/distcheck system into mainstream CMake, just looking for a
>> way to achieve the current result without requiring the
>> built-in-command overrides - I think collecting raw lists of paths
>> supplied to targets is the key piece that is currently driving the
>> command overrides.
>
> Once the list of all targets is available in a global property as
> discussed in another branch of this thread, then you could loop
> over that and check the SOURCES target property to get the list
> of original path specifiers.  That would handle almost everything.
> What would be left for your use case?

That sounds like it should work - I hadn't considered the
possibilities of the SOURCES target property.  Is that property
available for custom targets as well?

Thanks,
CY


More information about the cmake-developers mailing list