Bug 135142 - pro file corrupted: scopes moved on bottom
Summary: pro file corrupted: scopes moved on bottom
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: QMake (show other bugs)
Version: 3.3.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 78148 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-05 12:26 UTC by Gianni
Modified: 2006-11-20 21:57 UTC (History)
1 user (show)

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 Gianni 2006-10-05 12:26:59 UTC
Version:           3.3.2 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
Compiler:          i486-linux-gnu 
OS:                Linux

Modifications of .pro file done by Kdevelop interfacecorrupts the .pro file when it contains scopes. In facts scope section is moved down.

Example of .pro file:

macx{
  SOQTLIB += $$system(soqt-config --ldflags)
}
win32{
  SOQTLIB += X:\Coin3D\lib\soqt1.lib \
             X:\Coin3D\lib\coin2.lib
}
unix{
  SOQTLIB += -L/usr/local/lib -lSoQt \
             -L/usr/lib -lCoin
}

LIBS += $$SOQTLIB

HEADERS += ...
SOURCES += ...

After adding a class with "Project-> New Class..." the .pro file is corrupted because the platform dependent part (scopes) is pushed down:

HEADERS += ...
SOURCES += ...

LIBS += $$SOQTLIB

macx{
  SOQTLIB += $$system(soqt-config --ldflags)
}
win32{
  SOQTLIB += X:\Coin3D\lib\soqt1.lib \
             X:\Coin3D\lib\coin2.lib
}
unix{
  SOQTLIB += -L/usr/local/lib -lSoQt \
             -L/usr/lib -lCoin
}

Thanks for suggesting at least a work around.
Comment 1 Amilcar do Carmo Lucas 2006-10-05 19:02:51 UTC
This is a know issue and as far as I know it has been solved in the kdevelop/3.4 SVN branch.

To get the source do:
http://www.kdevelop.org/index.html?filename=3.4/branches_compiling.html
Comment 2 Andreas Pakulat 2006-11-20 21:54:39 UTC
Fixed for KDevelop3.4
Comment 3 Andreas Pakulat 2006-11-20 21:57:37 UTC
*** Bug 78148 has been marked as a duplicate of this bug. ***