Well, sent that a little too soon. I just realized that in my testing, I
wasn't specifying the source directory (which is an error) and when I do
"-N" does affect how "-L" behaves...
However, -L still leaves a lot of cache variables out (as does -LA), and I
would like to see the value of CMAKE_PROJECT_NAME.
Any tips?
Thanks,
Steven
On Thu, May 19, 2016 at 2:16 PM, Steven Velez wrote:
> The docs say:
>
> View mode only.
>>
>> Only load the cache. Do not actually run configure and generate steps.
>>
>
> But I wonder what you can do with cmake after that to view the cache?
>
> The -L parameter seems to display the same set of variables with or
> without this set, and scripts run in process script mode still seem to have
> no access to cache values.
>
> So, what's left?
>
> To state my problem a little more generally I would like a way to discover
> the project name set in a binary dir by it's associated CMakeLists.txt file.
>
> Is this possible without writing my own code to parse either the
> CMakeLists.txt or CMakeCache.txt?
>
> Thanks,
> Steven
>
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake