[cmake-developers] Listing all targets (was: Wrapping functions in CMake)

[David Cole]

I think the see also is relevant because it points to another way to
get to a whole different set of "properties". Perhaps what they're
looking for when they stumble upon get_cmake_property is actually
target properties, which are only accessible via get_property.

While it's relevant, and I think it should remain, I do think it could
use some clarification.

I'll take a stab at this, and clarify the docs, too, unless somebody
else chimes in and tells me "wait! I'm doing it already...."

:-)


Cheers,
David C.


On Fri, Jul 17, 2015 at 2:55 PM, Ben Boeckel <ben.boeckel at kitware.com> wrote:
> On Fri, Jul 17, 2015 at 14:16:34 -0400, David Cole wrote:
>> get_cmake_property is more like "strictly well-pre-defined, read only
>> (ish), built-into CMake" properties. Note there is no
>> set_cmake_property... What docs are you looking at that you think have
>> a bug...?
>
> Help/command/get_cmake_property:
>
>     get_cmake_property
>     ------------------
>
>     Get a property of the CMake instance.
>
>     ::
>
>       get_cmake_property(VAR property)
>
>       Get a property from the CMake instance.  The value of the property is
>       stored in the variable VAR.  If the property is not found, VAR will be
>       set to "NOTFOUND".  Some supported properties include: VARIABLES,
>       CACHE_VARIABLES, COMMANDS, MACROS, and COMPONENTS.
>
>       See also the more general get_property() command.
>
> `get_property` has no way (that I see) to ask for the same properties.
> The whole command docs could use a revamp too (while TARGETS is being
> implemented to avoid conflicts?).
>
> --Ben