Bug 76040 - kdevelop qmake manager curly bracket qmake variables incorrectly treated as scopes
Summary: kdevelop qmake manager curly bracket qmake variables incorrectly treated as s...
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: QMake (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-24 17:38 UTC by Sep Seyedi
Modified: 2006-11-20 22:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sep Seyedi 2004-02-24 17:38:22 UTC
Version:           unknown (using KDE 3.1.4)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.4.22-xfs

Previous to using the qmake manager I was creating my .pro files manually. I was defining some variables in a global .pro file and including it into my other .pro files. In my 'other' .pro files I was using my variables using the syntax $${VARIABLE}. Most of the time, I use my variables to give my libraries versions, like -lmylib-$${VERSION}, as some people might do.

Upon importing my entire project into kdevelop 3 and starting to use qmake manager to edit my qmake project it seems that it is incorrectly parsing my variables as a scope, when it should pick it up as just text.

One easy way of fixing it manually using the qmake manager is to delete the incorrectly detected scopes and insert things like -lmylib-$${VERSION} as an external library. Doing this, qmake manager seems to treat my .pro files properly.

-ss.
Comment 1 Amilcar do Carmo Lucas 2004-02-27 11:02:18 UTC
How about providing your KDevelop version ?
Comment 2 Sep Seyedi 2004-02-27 20:14:26 UTC
Sorry I didn't notice, but the kdevelop version is: kde 3.0.0b2. The Qt version is 3.2.1 if needed.

One thing to note: I mentioned an easy fix above, but as I have used to further I have noticed that this fix doesn't last long. The qmake manager when it needs to parse the file again it seems to screw up and mess up in output the new .pro file. This is only b/c of the curly brackets for the qmake variables. I forget why I was using the curly brackets but I think it had to do something red hat 9s Qt. Anyways, since qmake allows it, I think that they should be parsed properly. Thanks. 
-ss
Comment 3 maciek gajewski 2005-02-15 19:50:56 UTC
with kdevelop-3.1.92,  and qt-3.3. i hvae the following problem:
trying to make .pro file more usable, i defined few variables, using gui:
PYTHON_PREFIX=/usr/local
PYTHON_VERSION=2.3
then, i used the variables to specify libraries and paths, using manager gui 
external icludes path: $${PYTHON_PREFIX}/include/python$${PYTHON_VERSION}
external libs path: $${PYTHON_PREFIX}/lib/python$${PYTHON_VERSION}/convifg
external lib: -lpython$${PYTHON_VERSION}


after re-loading project qmake project manager trates variables as scopes or subprojects, and messes the project completely
Comment 4 Andreas Pakulat 2006-11-20 22:23:38 UTC
Fixed in SVN.