summaryrefslogtreecommitdiffstats
path: root/Tests/Tutorial/Step6/MathFunctions
diff options
context:
space:
mode:
authorAlex Neundorf <neundorf@kde.org>2012-07-28 16:00:19 (GMT)
committerAlex Neundorf <neundorf@kde.org>2012-08-16 21:15:21 (GMT)
commit5271ba56be87d5f412ea21c6c30cb72a893ceb25 (patch)
treebb6a7c67fc4ff2e06b4f206ec60ed77bbb77cafd /Tests/Tutorial/Step6/MathFunctions
parentc4306dc8057c45bc5edfd18465f85790800124cd (diff)
downloadCMake-5271ba56be87d5f412ea21c6c30cb72a893ceb25.zip
CMake-5271ba56be87d5f412ea21c6c30cb72a893ceb25.tar.gz
CMake-5271ba56be87d5f412ea21c6c30cb72a893ceb25.tar.bz2
Eclipse: fix #13358: don't create bad linked resources
directory where the project file is located (${CMAKE_BINARY_DIR}), which can happen e.g. for EXECUTABLE_OUTPUT_PATH and related variables. Now, it seems this code never worked. If EXECUTABLE_OUTPUT_PATH was set to point into a subdir of CMAKE_BINARY_DIR, the code did nothing. If it pointed directly at CMAKE_BINARY_DIR or some other location, it created a linked resource. I tested this with Eclipse Europa (3.3) and Juno (4.2), and in this case both versions of Eclipse complained that this is a bad location for a linked resource. Alex
Diffstat (limited to 'Tests/Tutorial/Step6/MathFunctions')
0 files changed, 0 insertions, 0 deletions