[Bug 61969] New: incorrect handling of libs in nested subdirs by qmake manager
Andreas Koepfle
koepfle at ti.uni-mannheim.de
Fri Aug 1 19:10:05 UTC 2003
------- 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=61969
Summary: incorrect handling of libs in nested subdirs by qmake
manager
Product: kdevelop
Version: unspecified
Platform: SuSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-devel at kdevelop.org
ReportedBy: koepfle at ti.uni-mannheim.de
Version: 3.0.0a5 cvs (using KDE KDE 3.1.2)
Installed from: SuSE RPMs
Compiler: gcc 3.3 prerelease
OS: Linux
qmake manager scrambles the LIBS and TARGETDEPS lines when linking to a lib, if the lib is in a nested subdirectory.
our project directory structure look like this:
|-libs
| |-mylib1
| |-mylib2
| |-bin
|
|-app
We put the created libraries in libs/bin (by setting DESTDIR=../bin in mylib1.pro & mylib2.pro)
Then after adding libs/mylib1 & libs/mylib2 in the Libraries dialog for app the corresponding lines in app.pro should read:
LIBS += ../libs/bin/libmylib1.a \
../libs/bin/libmylib2.a
TARGETDEPS += ../libs/bin/libmylib1.a \
../libs/bin/libmylib2.a
however they look like this:
LIBS += ../bin/libmylib1.a \
../bin/libmylib2.a
TARGETDEPS += ../bin/libmylib1.a \
../bin/libmylib2.a
I'm attaching a testcase and a patch that fixes this problem.
More information about the KDevelop-devel
mailing list