Discussion:
[CMake] LOCATION/CMP0026/export/import
Hendrik Greving
2018-11-07 18:04:58 UTC
Permalink
Hello,

w/ LOCATION property made obsolete, how can one read a target's LOCATION
for imported targets? Previously, IMPORTED_LOCATION was conveyed for such
targets, but reading the LOCATION property of imported targets leads to the
same warning as for project targets?

Thanks in advance
Robert Maynard
2018-11-07 19:38:26 UTC
Permalink
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed for such targets, but reading the LOCATION property of imported targets leads to the same warning as for project targets?
Thanks in advance
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
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
https://cmake.org/mailman/listinfo/cmake
--
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:
https://cmake.org/mailman/listinfo/cmake
Hendrik Greving
2018-11-07 20:27:37 UTC
Permalink
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is
obsolete)
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION
for imported targets? Previously, IMPORTED_LOCATION was conveyed for such
targets, but reading the LOCATION property of imported targets leads to the
same warning as for project targets?
Post by Hendrik Greving
Thanks in advance
--
Powered by www.kitware.com
http://www.cmake.org/Wiki/CMake_FAQ
Post by Hendrik Greving
Kitware offers various services to support the CMake community. For more
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
Post by Hendrik Greving
https://cmake.org/mailman/listinfo/cmake
Robert Maynard
2018-11-07 20:35:34 UTC
Permalink
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed for such targets, but reading the LOCATION property of imported targets leads to the same warning as for project targets?
Thanks in advance
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
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
https://cmake.org/mailman/listinfo/cmake
--
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:
https://cmake.org/mailman/listinfo/cmake
Hendrik Greving
2018-11-07 21:51:28 UTC
Permalink
Is IMPORTED_LOCATION a property one can read? I was under the assumption
that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And
as such, reading this LOCATION generates the warning. I just tried and it
indeed didn't let me read IMPORTED_LOCATION.
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
Post by Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is
obsolete)
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard <
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's
LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed
for such targets, but reading the LOCATION property of imported targets
leads to the same warning as for project targets?
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Thanks in advance
--
Powered by www.kitware.com
http://www.cmake.org/Wiki/CMake_FAQ
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Kitware offers various services to support the CMake community. For
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
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
https://cmake.org/mailman/listinfo/cmake
Robert Maynard
2018-11-07 22:06:59 UTC
Permalink
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the assumption that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And as such, reading this LOCATION generates the warning. I just tried and it indeed didn't let me read IMPORTED_LOCATION.
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed for such targets, but reading the LOCATION property of imported targets leads to the same warning as for project targets?
Thanks in advance
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
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
https://cmake.org/mailman/listinfo/cmake
--
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:
https://cmake.org/mailman/listinfo/cmake
Hendrik Greving
2018-11-07 22:15:27 UTC
Permalink
Ok! Except (see above) I do not think one can actually read
IMPORTED_LOCATION, can I?
Thanks! - again!
Post by Robert Maynard
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Post by Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the assumption
that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And
as such, reading this LOCATION generates the warning. I just tried and it
indeed didn't let me read IMPORTED_LOCATION.
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 12:36 PM Robert Maynard <
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
Post by Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is
obsolete)
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard <
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now
evaluated
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
at generate time ), the general solution is that you need to move
your
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's
LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed
for such targets, but reading the LOCATION property of imported targets
leads to the same warning as for project targets?
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Thanks in advance
--
Powered by www.kitware.com
http://www.cmake.org/Wiki/CMake_FAQ
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Kitware offers various services to support the CMake community.
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
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
https://cmake.org/mailman/listinfo/cmake
Robert Maynard
2018-11-07 22:19:12 UTC
Permalink
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
Ok! Except (see above) I do not think one can actually read IMPORTED_LOCATION, can I?
Thanks! - again!
Post by Robert Maynard
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the assumption that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And as such, reading this LOCATION generates the warning. I just tried and it indeed didn't let me read IMPORTED_LOCATION.
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed for such targets, but reading the LOCATION property of imported targets leads to the same warning as for project targets?
Thanks in advance
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
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
https://cmake.org/mailman/listinfo/cmake
--
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:
https://cmake.org/mailman/listinfo/cmake
Hendrik Greving
2018-11-07 22:24:42 UTC
Permalink
Ok, it seems to be IMPORT_LOCATION, not IMPORTED_LOCATION
We have a (.cmake) file that shared among things that use it for build
targets and external projects for imported targets. Is there a way to find
out whether a target is imported or a build target?
Post by Robert Maynard
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
Post by Hendrik Greving
Ok! Except (see above) I do not think one can actually read
IMPORTED_LOCATION, can I?
Post by Hendrik Greving
Thanks! - again!
On Wed, Nov 7, 2018 at 2:07 PM Robert Maynard <
Post by Robert Maynard
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Post by Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the
assumption that setting IMPORTED_LOCATION becomes LOCATION (for imported
targets). And as such, reading this LOCATION generates the warning. I just
tried and it indeed didn't let me read IMPORTED_LOCATION.
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 12:36 PM Robert Maynard <
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
Post by Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION
is obsolete)
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard <
Post by Robert Maynard
With generator expressions making the reading of LOCATION
non-viable
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
during configuration time ( since the actual location is now
evaluated
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
at generate time ), the general solution is that you need to move
your
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
LOCATION reading logic also to generate time. In general this
means
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's
LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed
for such targets, but reading the LOCATION property of imported targets
leads to the same warning as for project targets?
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Thanks in advance
--
Powered by www.kitware.com
http://www.cmake.org/Wiki/CMake_FAQ
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Kitware offers various services to support the CMake community.
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
http://cmake.org/cmake/help/training.html
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
https://cmake.org/mailman/listinfo/cmake
Robert Maynard
2018-11-07 22:28:49 UTC
Permalink
Yes you can get if a target is imported by seeing if the IMPORTED
property is set to true. (
https://cmake.org/cmake/help/v3.12/prop_tgt/IMPORTED.html )
On Wed, Nov 7, 2018 at 5:24 PM Hendrik Greving
Post by Hendrik Greving
Ok, it seems to be IMPORT_LOCATION, not IMPORTED_LOCATION
We have a (.cmake) file that shared among things that use it for build targets and external projects for imported targets. Is there a way to find out whether a target is imported or a build target?
Post by Robert Maynard
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
Ok! Except (see above) I do not think one can actually read IMPORTED_LOCATION, can I?
Thanks! - again!
Post by Robert Maynard
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the assumption that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And as such, reading this LOCATION generates the warning. I just tried and it indeed didn't let me read IMPORTED_LOCATION.
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
Post by Robert Maynard
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something like file(GENERATE ) to dump the location to disk.
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was conveyed for such targets, but reading the LOCATION property of imported targets leads to the same warning as for project targets?
Thanks in advance
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
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
https://cmake.org/mailman/listinfo/cmake
--
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:
https://cmake.org/mailman/listinfo/cmake
Hendrik Greving
2018-11-07 22:32:16 UTC
Permalink
Ok, that works for us!
Post by Robert Maynard
Yes you can get if a target is imported by seeing if the IMPORTED
property is set to true. (
https://cmake.org/cmake/help/v3.12/prop_tgt/IMPORTED.html )
On Wed, Nov 7, 2018 at 5:24 PM Hendrik Greving
Post by Hendrik Greving
Ok, it seems to be IMPORT_LOCATION, not IMPORTED_LOCATION
We have a (.cmake) file that shared among things that use it for build
targets and external projects for imported targets. Is there a way to find
out whether a target is imported or a build target?
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 2:19 PM Robert Maynard <
Post by Robert Maynard
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
Post by Hendrik Greving
Ok! Except (see above) I do not think one can actually read
IMPORTED_LOCATION, can I?
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Thanks! - again!
On Wed, Nov 7, 2018 at 2:07 PM Robert Maynard <
Post by Robert Maynard
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without
triggering
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
Post by Hendrik Greving
Is IMPORTED_LOCATION a property one can read? I was under the
assumption that setting IMPORTED_LOCATION becomes LOCATION (for imported
targets). And as such, reading this LOCATION generates the warning. I just
tried and it indeed didn't let me read IMPORTED_LOCATION.
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 12:36 PM Robert Maynard <
Post by Robert Maynard
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
Post by Hendrik Greving
So IMPORTED_LOCATION is obsolete as well? (since reading
LOCATION is obsolete)
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard <
Post by Robert Maynard
With generator expressions making the reading of LOCATION
non-viable
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
during configuration time ( since the actual location is now
evaluated
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
at generate time ), the general solution is that you need to
move your
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
LOCATION reading logic also to generate time. In general this
means
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
using something like file(GENERATE ) to dump the location to
disk.
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
On Wed, Nov 7, 2018 at 1:05 PM Hendrik Greving
Post by Hendrik Greving
Hello,
w/ LOCATION property made obsolete, how can one read a
target's LOCATION for imported targets? Previously, IMPORTED_LOCATION was
conveyed for such targets, but reading the LOCATION property of imported
targets leads to the same warning as for project targets?
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Thanks in advance
--
Powered by www.kitware.com
http://www.cmake.org/Wiki/CMake_FAQ
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Kitware offers various services to support the CMake
CMake Support: http://cmake.org/cmake/help/support.html
http://cmake.org/cmake/help/consulting.html
http://cmake.org/cmake/help/training.html
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
Post by Robert Maynard
Post by Hendrik Greving
https://cmake.org/mailman/listinfo/cmake
Loading...