Summary: | adding new class break existing qmake project file | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Gioele Barabucci <dev> |
Component: | Build tools: QMake | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.0.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gioele Barabucci
2004-03-21 15:55:22 UTC
Version: 3.3.2 OS: Linux(i686) release 2.6.15-27-386 Compiler:i486-linux-gnu I found a similar problem with "Project-> New Class..." operation. The .pro file before adding a class is something like that: macx{ SOQTLIB += $$system(soqt-config --ldflags) } win32{ SOQTLIB += X:\Coin3D\lib\soqt1.lib \ X:\Coin3D\lib\coin2.lib } unix{ SOQTLIB += -L/usr/local/lib -lSoQt \ -L/usr/lib -lCoin } LIBS += $$SOQTLIB HEADERS += ... SOURCES += ... After adding a class with "Project-> New Class..." the .pro file is corrupted because HEADERS and SOURCES parts are popped up while the platform dependent part is pushed at the bottom: HEADERS += ... SOURCES += ... LIBS += $$SOQTLIB macx{ SOQTLIB += $$system(soqt-config --ldflags) } win32{ SOQTLIB += X:\Coin3D\lib\soqt1.lib \ X:\Coin3D\lib\coin2.lib } unix{ SOQTLIB += -L/usr/local/lib -lSoQt \ -L/usr/lib -lCoin } Thanks for suggesting at least a work around. |