MantisBT - CMake
View Issue Details
0016068CMakeCMakepublic2016-04-15 10:562016-06-10 14:31
Martin Haaß 
Kitware Robot 
normalminoralways
closedmoved 
x86_68linux/anydebian testing
CMake 3.5.1 
 
0016068: qt5 autorcc uses wrong output folder
The file qrc_Editor.cpp generated by the qt5 rcc compile step from Editor.qrc is put into CMAKE_BINARY_DIR/CMakeFiles/${target}.dir
where it cannot be found/referenced.
Files generated by automoc and autoui are put in CMAKE_BINARY_DIR, where they can be found.
Inside CMAKE_BINARY_DIR/CMakeFiles/${target}.dir there is another folder ${target}.dir/CMakeFiles/${target}.dir which contains qrc_Editor.cpp.o.
To me it looks like cmake start the rcc step with the wrong folder
No tags attached.
Issue History
2016-04-15 10:56Martin HaaßNew Issue
2016-04-22 09:12Brad KingNote Added: 0040923
2016-05-02 10:32Martin HaaßNote Added: 0041004
2016-06-10 14:29Kitware RobotNote Added: 0042984
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0040923)
Brad King   
2016-04-22 09:12   
Related change:

Autogen: Generate qrc_NAME.cpp files in subdirectories
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9c6fa684 [^]

As far as the issue reported here, IIUC it shouldn't matter where the .cpp file goes because CMake compiles it and includes it in the link step for the target.
(0041004)
Martin Haaß   
2016-05-02 10:32   
True, bug on our side: the generated *.cpp was source-included to enforce a dependency.
FWIW the qrc_ files still end up in a different folder than the other generated files, like e.g. ui*.h
(0042984)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.