[CMake] CMake 2.7 continues to display EXECUTABLE_OUTPUT_PATH / LIBRARY_OUTPUT_PATH

Philip Lowman philip at yhbt.com
Thu Jul 3 07:50:41 EDT 2008


On Thu, Jul 3, 2008 at 3:28 AM, Timenkov Yuri <ytimenkov at parallels.com>
wrote:

>
>
> On Thursday 03 July 2008 05:24:07 Miguel A. Figueroa-Villanueva wrote:
> > Hello,
> >
> > Since EXECUTABLE_OUTPUT_PATH / LIBRARY_OUTPUT_PATH have been replaced
> > with the CMAKE_RUNTIME_OUTPUT_DIRECTORY /
> > CMAKE_LIBRARY_OUTPUT_DIRECTORY they shouldn't appear in the GUI
> > (CMakeSetup, QtDialog). That gives the impression that they are not
> > deprecated as suggested by the documentation.
> >
> > Also, it is confusing when people in fact use the new variables. Say
> > you have the following CMakeLists.txt
> >
> > ----
> > project(test)
> > set(CMAKE_RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/bin")
> > add_executable(hello hello.cxx)
> > ----
> >
> > When the user runs the GUI and sees the red EXECUTABLE_OUTPUT_PATH
> > variable, which he is used to working with, he can proceed to change
> > it and it won't have an effect.
> >
> > Is this an easy fix or should I open a bug item?
> Do you regenerate cache? You may have these variables in you CMakeCache.txt
> file. Try with clean build output.
>
>
CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
PROJECT(foo)
ADD_EXECUTABLE(foo foo.cc)

This is all that's needed to reproduce this bug (on CMake 2.6.0 with Visual
Studio 8 generator).

-- 
Philip Lowman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20080703/783fa3cc/attachment-0001.htm>


More information about the CMake mailing list