Project tree in Qt Creator (cmake project)
-
wrote on 22 Jul 2011, 10:19 last edited by
Hi,
I'm using Qt Creator and cmake (2.8.4) to build a project. I have problems configuring Qt Creator.
1.- Project has a .css file, but I don't know how list this file in the project tree. In CMakeLists.txt I have a line (add_custom_target) for this file, and the file is included when I compile the project, but doesn't appear in Qt Creator's project tree.
2.- In the project tree I can see /usr/share/cmake/Modules. Any idea how can I make it disappear?
A picture of my project tree:
!http://i56.tinypic.com/2wq49d4.png(project tree)!How can I see the folder css with my .css files and hide the ../../usr folder?
-
wrote on 22 Jul 2011, 11:54 last edited by
2: You can't because CMake needs those scripts to be useful. Creator cannot (or should not even try to) reliably separate handmade scripts from 'system' scripts.
-
wrote on 17 Aug 2011, 06:57 last edited by
Cmake is limited with regards to providing all files that belong to a project to a IDE. Non-code files tend to get lost and quite some headers. Sorry, there is little we can do about that.
CMake does consider its own files as part of a project. That is why you see them... I am not aware of any way to suppress that, short of patching cmake that is.
-
wrote on 17 Aug 2011, 07:03 last edited by
[quote author="Tobias Hunger" date="1313564234"]Cmake is limited with regards to providing all files that belong to a project to a IDE. Non-code files tend to get lost and quite some headers. Sorry, there is little we can do about that.[/quote]What we (the community) can do about that is improve CMake on this specific part.
[quote author="Tobias Hunger" date="1313564234"]CMake does consider its own files as part of a project. That is why you see them... I am not aware of any way to suppress that, short of patching cmake that is.[/quote]So it's a CMake dev choice and patching CMake or requesting this specific behavior should happen there.
-
wrote on 17 Aug 2011, 15:13 last edited by
I think there was some work on the codeblocks cmake generator (which we also use). So maybe a newer version does work better already:-)