On 1/25/2012 1:50 AM, Michael Wild wrote:
So, to fix your code, use IMPORTED_LOCATION_NOCONFIG.
Actually just use LOCATION or LOCATION_${CONFIG} for some CONFIG:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LOCATION
On 2012-01-25 08:14-0500 Brad King wrote:
On 1/25/2012 1:50 AM, Michael Wild wrote:
So, to fix your code, use IMPORTED_LOCATION_NOCONFIG.
Actually just use LOCATION or LOCATION_${CONFIG} for some CONFIG:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LOCATION
On 1/25/2012 3:12 PM, Alan W. Irwin wrote:
change the documentation of IMPORTED_LOCATION to indicate
it is not always reliably set for imported targets and urge the reader
to use LOCATION instead.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7d20619f
-Brad
--
Powered by www.kitware.com
On 2012-01-24 06:28+0100 Michael Wild wrote:
On 01/24/2012 05:50 AM, Alan W. Irwin wrote:
The documentation you get from
cmake --help-full
refers to the IMPORTED_LOCATION property as one of the more important
ones set for imported targets. I have to agree that location is the
most important
On 01/25/2012 12:25 AM, Alan W. Irwin wrote:
On 2012-01-24 06:28+0100 Michael Wild wrote:
On 01/24/2012 05:50 AM, Alan W. Irwin wrote:
The documentation you get from
cmake --help-full
refers to the IMPORTED_LOCATION property as one of the more important
ones set for imported targets. I
The documentation you get from
cmake --help-full
refers to the IMPORTED_LOCATION property as one of the more important
ones set for imported targets. I have to agree that location is the
most important property for imported targets, but the name appears to
be wrong for the documentation of
