Skip to content

Commit

Permalink
Don't force debug builds in qmake project files.
Browse files Browse the repository at this point in the history
When creating makefiles with qmake one needs to give the target in command
line. E.g.
  $ qmake -config debug
or
  $ qmake -config release

For Visual studio projects both targets are generated by just running the
qmake command without switches.
  • Loading branch information
kimmov committed Aug 17, 2009
1 parent d16d19e commit ec40b4c
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 3 deletions.
2 changes: 1 addition & 1 deletion gui/gui.pro
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ INCLUDEPATH += .
RCC_DIR = temp
MOC_DIR = temp
OBJECTS_DIR = temp
CONFIG += warn_on debug
CONFIG += warn_on
RESOURCES = gui.qrc
FORMS = main.ui \
resultsview.ui \
Expand Down
7 changes: 6 additions & 1 deletion readme.txt
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,15 @@ Compiling

The Makefile works under Linux.
To make it work under Windows with DJGPP, change "g++" to "gxx".

To build cppcheck with qmake, run the commands:
cd src
qmake -config release (or '-config debug' if doing developer build)
make

To compile the GUI one needs Qt development libraries and issue the following commands:
cd gui
qmake
qmake -config release (or '-config debug' if doing developer build)
lrelease gui.pro
make

Expand Down
2 changes: 1 addition & 1 deletion src/src.pro
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ TARGET = cppcheck
DEPENDPATH += .
INCLUDEPATH += .
OBJECTS_DIR = temp
CONFIG += warn_on debug
CONFIG += warn_on
QT -= gui core

# Input
Expand Down

0 comments on commit ec40b4c

Please sign in to comment.