[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 78148] adding new class break existing qmake project file
From: Gianni <grm.trash () gmail ! com>
Date: 2006-10-02 8:54:36
Message-ID: 20061002085436.31680.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=78148
------- Additional Comments From grm.trash gmail com 2006-10-02 10:54 -------
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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic