[Bug 74099] New: FileBuffer misbehaves on scopes

[Holger Freyther]

------- 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=74099      
           Summary: FileBuffer misbehaves on scopes
           Product: kdevelop
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: trollproject
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: freyther at kde.org


Version:           KDE_3_2_BRANCH (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
Compiler:          gcc-Version 3.3.3 20040125 (prerelease) (Debian) 

The parsers in FileBuffer and Trollprojectwidget misbehaves in regards to scopes.

First system( rm $${TARGET} ) gets parsed as a scope but is perfectly valid with qmake.

Then also if you've something like these

TEMPLATE = app
CONFIG +=  foo
SOME_VAR = $$(SOME_VAR)

contains( SOME_VAR, foo-bar ){
      foo {
          TEMPLATE = lib         
      }else {
           TEMPLATE = something_different
           TARGET = bar
      }
}


The scope does not get ignored and TEMPLATE and TARGET are getting picked from the last version. Here from within the scope. Now if you configre the qmake project. Target will be bar and the TEMPLATE will be different as well.