Bug 74099 - FileBuffer misbehaves on scopes
Summary: FileBuffer misbehaves on scopes
Status: RESOLVED DUPLICATE of bug 59109
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: QMake (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-04 00:26 UTC by Holger Freyther
Modified: 2006-11-20 22:15 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 Holger Freyther 2004-02-04 00:26:55 UTC
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.
Comment 1 thasart 2004-07-20 20:32:08 UTC
the pasing of qmake commands are wron and should be fixed,
but constructs like:

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

cannot be parsed by the kdevelop qmake-parse i think...
Comment 2 Andreas Pakulat 2006-11-20 22:15:40 UTC

*** This bug has been marked as a duplicate of 59109 ***