Bug 151491 - QMake project parse error *.pri file
Summary: QMake project parse error *.pri file
Status: RESOLVED DUPLICATE of bug 151492
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.5.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-29 00:54 UTC by Tomasz Ziobrowski
Modified: 2007-10-29 23:20 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 Tomasz Ziobrowski 2007-10-29 00:54:10 UTC
Version:           3.5.0 (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.2.2 (Gentoo 4.2.2 p1.0) 
OS:                Linux

When parsing Flags.pri included  mutliple times form subdirectory projects 
program returns parse error, at the same time qmake (Qt 4.3.x) work properly with it. 

"
unix{
 # Development machine
 INCLUDEPATH+=/usr/include/OGRE/
 QMAKE_CXX=distcc
 QMAKE_CXXFLAGS_RELEASE= -g3 -Wall -pg
 QMAKE_LFLAGS_RELEASE= -pg
 #QMAKE_CXXFLAGS_RELEASE= -march=k8 -Os -mfpmath=sse
}

win32{
 # Target platform - Windows
 # Pentium-Pro -- becouse of Intel and AMD fork
 INCLUDEPATH+=$$(OGRE_HOME)/include
 LIBS+=-L$$(OGRE_HOME)/bin/release
 #QMAKE_CXXFLAGS_RELEASE= -g3 -Wall
 QMAKE_CXXFLAGS_RELEASE= -march=i686 -Os -Wall

 # QMAKE_LFLAGS_RELEASE=
}
"

Additionally 
Parsing following line 
"=================" 
in .pro files causes as well parse error. 

BTW. 
It would be nice to have line number and token name included to parser string error. 





Additionally 
When parsing project files ... having line od '=' chars return parse error. When qmake parser does'nt do that. 

I would be glad to include simplified project for which those errors occur. But this is my first bug report and I don't know how to include this file here. 

P.S.
Forgive me my English it is not my primary language.
Comment 1 Pino Toscano 2007-10-29 23:20:40 UTC
PS: you don't need to create the same bug report just to attach a file.

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