| Summary: | QMake-Manager ignores win32-section in *.pro files (and overrides them!) | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Andreas Pietzowski <andreas> |
| Component: | Build tools: QMake | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Looks like we do not handle .pro files "transparently" like we should :( Yes we do :(. Every option unknown to trollproject part is excluded. But I wonder why scope win32 is excluded. Scopes should be handled normally. It would be nice to see the section like
LIBS += -lmysqlclient
enclosed in brackets for unix like
unix{
LIBS += -lmysqlclient
}
because the lib-defines are very system-specific and with the sections I can use my pro-file under windows AND linux without a problem for each platform. Is there some development-progress in that direction?
|
Version: 3.0.0 (using KDE 3.2.0, SuSE) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB Hi, I have a Windows project which I also develop and compile under my favourite Desktop (KDE *g*). For that I have to split my *.pro-file a bit like that: win32{ LIBS += C:\Programme\mysql.lib } unix{ LIBS += -lmysqlclient } ...but kdevekop overrides my *.pro-file everytime and I have to re-insert those lines to enable correct compiling under WinXP. Would be nice to see this fixed. Perhaps it would also be cool, to set dependencies in the subproject-settings-dialog. However: KDevelop 3.0 really kicks ass so far - very good work! Thanks Pietz