[cmake-developers] [CMake 0011671]: changing RUNTIME_OUTPUT_DIR after fetching LOCATION fails
Mantis Bug Tracker
mantis at public.kitware.com
Sun Jan 9 15:18:51 EST 2011
The following issue has been SUBMITTED.
======================================================================
http://public.kitware.com/Bug/view.php?id=11671
======================================================================
Reported By: Andreas Pakulat
Assigned To:
======================================================================
Project: CMake
Issue ID: 11671
Category: CMake
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 2011-01-09 15:18 EST
Last Modified: 2011-01-09 15:18 EST
======================================================================
Summary: changing RUNTIME_OUTPUT_DIR after fetching LOCATION
fails
Description:
Attached is a simple cmake project which is supposed to put the setup binary
into the top-level build directory, but puts it into the bin/ directory as set
via CMAKE_RUNTIME_OUTPUT_DIRECTORY. The reason for this is that the LOCATION
property of the target is being read and this seems to cause cmake to not update
it anymore later on.
Commenting out the get_property line will put the binary into the top-level
build directory.
I think this should either be allowed, with the implication that one needs to
re-fetch the LOCATION property. Or it should be yielding a warning to set this
property on a target where it has no effect and be documented in the cmake
manual.
Steps to Reproduce:
Run cmake + make on the attached project, the setup binary should be in the
top-level directory and not in the bin/ directory.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-01-09 15:18 Andreas PakulatNew Issue
2011-01-09 15:18 Andreas PakulatFile Added: test_output_dir.tar.gz
======================================================================
More information about the cmake-developers
mailing list