[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 135978] New: Some problems with QMake manager (QT4)
From: Dario Vecchio <dariovecchio () tiscali ! it>
Date: 2006-10-19 17:22:34
Message-ID: 20061019192231.135978.dariovecchio () tiscali ! it
[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=135978
Summary: Some problems with QMake manager (QT4)
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: dariovecchio tiscali it
Version: 3.4 SVN rev 597183 (using KDE KDE 3.5.1)
Installed from: Compiled From Sources
Compiler: gcc 4.1.0
OS: Linux
- QMake Manager (QT 4.1.3)
- Add Subproject
- After inserting the subproject name should show the configuration dialog
(we have not yet specified if it is an application, a library or whatever)
- Subproject Settings
- "Configuration" tab, "Build Mode" has no default selection (no radiobutton is checked)
- "Includes" tab shows "Directories Inside Project" without the first letter
(e.g. "rc" instead of "src")
- Checking any subproject in the "Includes" tab results in wrong -I<subproject dir>
command line parameter (e.g. myproject/src, myproject/thelib results in
-I<absolute path to myproject>/srcthelib). The error is already in the .pro file.
I also think the path should be relative (-I../thelib) even in .pro file (qmake seems
to transform some path from absolute to relative). If everythink inside project is relative
we can easily move the project.
- Build order:
- seems to reflect the creation order and not the dependencies (if you create
"src" application and then "thelib" library it doesn't work)
- now works if manually change the build order in the root project
- SOURCES->RMB->context menu->Properties: removes the file
- Shared Libraries: no rpath (linker option) to the relative subdir (the executable
wont start)
- I add a static lib (existing subproject) to "src" build and everythink is ok.
Then I change the static lib to a dll: the "src" project gets confused. The lib is removed
from "convenient libraries inside project" and an external nonexistent static lib.a
is added to the "src" project.
I also had a situation in which thelib.pro contains at the same time
CONFIG += dll and CONFIG -= dll for a static library
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic