[cmake-developers] Generating imported library targets without the cmake executable

Brad King brad.king at kitware.com
Wed Nov 30 09:31:47 EST 2011


On 11/30/2011 9:09 AM, Stephen Kelly wrote:
> Brad King wrote:
>> Alex was proposing simply to provide the singular name as a variable but not
>> to cache it.  The only reason to cache a variable is when we're searching and
>> need to let the user help out or override.  In a Config.cmake file we know
>> the answer.
>
> Ok, so you're saying the user should definitely not be able to override the
> value, so it shouldn't be cached. The remaining question is whether it
> should be provided anyway uncached for the reasons Alex described. If that
> should be done, then I can do that.

I don't mind providing it for convenience.  However more variables means
more variables.  Users may not know which one to use when.  I don't have
a strong opinion either way.

-Brad



More information about the cmake-developers mailing list