Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
QT Creator 2.0 pro file issue
My project has been using Qt Creator 1.3 for a while. We have several .pro files created for each of our sub projects, but the header and source files specification uses *.h and *.cpp. When we tried to update to Qt Creator 2.0, we are unable to import the sources and headers. If we explicitly name the classes .h and .cpp's, it will import correctly, but this would require a massive amount of changes to our .pro files.
Is there any way around this? Is there a flag in 2.0 that allows the use of *.h and *.cpp specification in .pro files?
DenisKormalev last edited by
There is setting for default extensions for headers and source files if you are asking about it.
I don't think I need the default extensions, I'm curious as to why creator 2.0 doesn't accept this in the .pro files:
HEADERS += *.h
SOURCES += *.cpp
but rather prefers I list them as:
HEADERS += class1.h
SOURCES += class1.cpp
I'd much rather use the * notation
This issue was discussed on the Qt creator ML "here":http://lists.trolltech.com/pipermail/qt-creator/2010-August/007497.html.
The "bug report is here":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-1364. The fix will be in the upcoming Qt Creator 2.0.1 release.
The most important mail in this thread seems to be "this one":http://lists.trolltech.com/pipermail/qt-creator/2010-August/007503.html, recommending against doing this in the first place you will need to rerun qmake manually.
The version I downloaded (http://labs.trolltech.com/blogs/2010/08/25/qt-creator-201/) says that it is version 2.0.1. Has this been pushed back?
Guest last edited by
I just got Qt Creator 2.0.1 and used both *.h and *.cpp and it worked just fine