Brad King wrote: > On 11/29/2011 8:40 PM, Stephen Kelly wrote: >> Alexander Neundorf wrote: >>> Nevertheless, personally I would also provide the Qt5Core_LIBRARY >>> variable, so if somebody wants to have a look what that variable >>> currently actually is (would by the name if the imported target), he can >>> do that, and then maybe do something with the target name. >>> This is harder if there is only the plural version of the variables. >>> I'd say those singular versions are not strictly necessary, but they >>> don't hurt and can in some cases be useful. >> >> If it's a cached variable, someone could potentially redefine >> QtCore_LIBRARY > > 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. Thanks, Steve. -- 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