Brad,
On Wednesday 25 March 2009 07:38:41 Brad King wrote:
> Thanks for the example. There were two bugs canceling each other out for
> this use case. One was fixed in 2.6.3 which exposed the other. I've
> committed a fix and a test (the full commit log explains everything).
>
> I'll schedule t
KSpam wrote:
I attached a small example with the problem. The problem is actually a bit
more complicated than my original explanation. I have a macro in my
top-level CMakeLists.txt file:
macro (getScriptDir _scriptDir)
get_filename_component(${_scriptDir} ${CMAKE_CURRENT_LIST_FILE} PATH)
KSpam wrote:
My build system relies heavily on CMAKE_CURRENT_LIST_FILE. For instance, I
typically get a variable for the directory containing the current list file
as follows:
get_filename_component(scriptDir ${CMAKE_CURRENT_LIST_FILE} PATH)
This has worked in prior versions of CMake; howeve
My build system relies heavily on CMAKE_CURRENT_LIST_FILE. For instance, I
typically get a variable for the directory containing the current list file
as follows:
get_filename_component(scriptDir ${CMAKE_CURRENT_LIST_FILE} PATH)
This has worked in prior versions of CMake; however, it does not
