Bug in cmake parser?
Andreas Pakulat
apaku at gmx.de
Sat Dec 29 02:31:04 UTC 2007
On 29.12.07 03:25:11, Andreas Pakulat wrote:
> Hi,
>
> trying to fix cmake support up for win32 I've stumbled across something
> which I think is a bug in the parser. When creating ExecProgramAst it
> seems like its workingDirectory option is set automatically to the
> executable, if no WORKING_DIRECTORY argument is given to the function in
> the CMakeLists.txt.
>
> So for something like
>
> exec_program(${KDE4_KDECONFIG_EXECUTABLE} ARGS --path data
> OUTPUT_VARIABLE _data_DIR)
>
> visit( ExecProgramAst* ) gets a working directory of
> "D:/andreas/kde4/bin/kde4-config.exe", i.e. the same as the actual value
> of the variable KDE4_KDECONFIG_EXECUTABLE.
>
> I can reproduce that with the two attached files on both win32 and
> linux. So it seems for some reason the parser does "the right thing" on
> linux to create a default working dir.
>
> As its now 3:30 am, I'm not going to look into it right away and instead
> sending this, so maybe somebody with a bit more insight has a fix at
> hand by the time I wake up :)
And here the testcase.
Andreas
--
You are destined to become the commandant of the fighting men of the
department of transportation.
-------------- next part --------------
find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})
kde4_add_executable(testqp main.cpp)
target_link_libraries(testqp ${KDE4_KDEUI_LIBS})
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.cpp
Type: text/x-c++src
Size: 862 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20071229/69c65a5f/attachment.cpp>
More information about the KDevelop-devel
mailing list