Notes |
|
(0026845)
|
Alex Neundorf
|
2011-06-13 04:48
(edited on: 2011-06-13 05:08) |
|
It behaves the same way as ${CMAKE_CURRENT_LIST_FILE}, so this behaviour is intentional.
I can remember there were discussion(s) about this on the cmake or cmake-developers mailing list, and this was the outcome. Can't remember the details though.
Alex
|
|
|
(0027127)
|
Brad King
|
2011-07-29 18:19
|
|
The behavior is as intended.
The workaround you propose is already in common usage. Typically if I'm writing a module "MyModule.cmake" then I will put code at the top like
get_filename_component(_MyModule_LIST_DIR ${CMAKE_CURRENT_LIST_FILE} PATH)
which is the pre-2.8.3 equivalent to
set(_MyModule_LIST_DIR ${CMAKE_CURRENT_LIST_DIR})
so I can refer to the module location inside functions or macros later. |
|
|
(0028116)
|
David Cole
|
2012-01-02 15:56
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|