Improving qmake-qt4 support in KDevelop3.4

Hi,

I had a quick try with a Qt4 project I have and the
qmake-buildmanager
completely messes up the qmake project files.

However having browsed a bit through the various
qmake-related dirs
under buildtools I'm a bit lost 

Apart from KDevelop's API documentation, is there some kind
of
introductory material to how the qmake buildsystem works?

Also would it be better to try to extend the existing qmake
manager, or
should I better copy it as "qmake4" (wherever I
find a qmake dir) and
start replacing existing stuff.

One thing the qmake-manager messes up is the value of the QT
variable,
for my project it only contains "xml", and thus
qmake generates includes
only for $QTDIR/include and $QTDIR/include/QtXml. However
adding
gui+core qmake also generates includes for QtCore and QtGui.

I do understand that one could use "custom
makefiles" for such projects,
but then all the other neat stuff I just provided patches
for would've
been a complete waste of time...

Andreas

-- 
Don't worry so loud, your roommate can't think.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 24.07.06 20:46:39, Andreas Pakulat wrote:
> However having browsed a bit through the various
qmake-related dirs
> under buildtools I'm a bit lost 
> 
> Apart from KDevelop's API documentation, is there some
kind of
> introductory material to how the qmake buildsystem
works?

Well, I started a bit on  that, and now I'm really
confused. According
to the docs KDevBuildTool is deprecated, however the
qmakeprojectpart.cpp still subclasses it and is the class
used for qmake
support.

Then there's buildtools/projectmanager/importers/qmake
which contains a
KDevProjectEditor. However there's no
KDevProjectImporter...

Last but not least there's the real "parsing"
stuff (.ll and .yy in
lib/parsers/qmake)...

I'm really totally confused as to which way I should take
(should I
implement KDevProjectImporter+~Editor+~Builder, or should I
try to do
the same as the current qmake manager does)?

I'd really appreciate it if somebody (maybe as PM if it's
lengthy) could
shed some light on this for me. Thanks in advance.

Andreas

-- 
You will be held hostage by a radical group.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Monday 24 July 2006 22:06, Andreas Pakulat wrote:
> On 24.07.06 20:46:39, Andreas Pakulat wrote:
> > However having browsed a bit through the various
qmake-related dirs
> > under buildtools I'm a bit lost 
> >
> > Apart from KDevelop's API documentation, is there
some kind of
> > introductory material to how the qmake buildsystem
works?

The API documentation on the kdevelop website is for trunk.
Do not use it for KDevelop 3.4 development.

> Well, I started a bit on  that, and now I'm really
confused. According
> to the docs KDevBuildTool is deprecated, however the
> qmakeprojectpart.cpp still subclasses it and is the
class used for qmake
> support.
Please regenerate the API documentation on your local
machine, that will give 
you KDevelop 3.4 up-to-date documentation.

the qmake project stuff should be in buildtools/qmake


amilcar

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 25.07.06 00:57:13, Amilcar do Carmo Lucas wrote:
> On Monday 24 July 2006 22:06, Andreas Pakulat wrote:
> > On 24.07.06 20:46:39, Andreas Pakulat wrote:
> > > However having browsed a bit through the
various qmake-related dirs
> > > under buildtools I'm a bit lost 
> > >
> > > Apart from KDevelop's API documentation, is
there some kind of
> > > introductory material to how the qmake
buildsystem works?
> 
> The API documentation on the kdevelop website is for
trunk.

Yeah, just figured this myself  I guess
the kdevplatformdoc.tar.bz2
is also for trunk?

> > Well, I started a bit on  that, and now I'm
really confused. According
> > to the docs KDevBuildTool is deprecated, however
the
> > qmakeprojectpart.cpp still subclasses it and is
the class used for qmake
> > support.
> Please regenerate the API documentation on your local
machine, that will give 
> you KDevelop 3.4 up-to-date documentation.

I actually first did that, but it somehow looked incomplete
and thus I
thought it hasn't been properly generated...

Andreas

-- 
It was all so different before everything changed.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 25.07.06 01:20:35, Andreas Pakulat wrote:
> On 25.07.06 00:57:13, Amilcar do Carmo Lucas wrote:
> > > Well, I started a bit on  that, and now I'm
really confused. According
> > > to the docs KDevBuildTool is deprecated,
however the
> > > qmakeprojectpart.cpp still subclasses it and
is the class used for qmake
> > > support.
> > Please regenerate the API documentation on your
local machine, that will give 
> > you KDevelop 3.4 up-to-date documentation.
> 
> I actually first did that, but it somehow looked
incomplete and thus I
> thought it hasn't been properly generated...

There definitely is a problem with the apidoc generation,
I'll post a
separate thread.

-- 
You're at the end of the road again.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Monday 24 July 2006 15:06, Andreas Pakulat wrote:
> On 24.07.06 20:46:39, Andreas Pakulat wrote:
> > However having browsed a bit through the various
qmake-related dirs
> > under buildtools I'm a bit lost 
> >
> > Apart from KDevelop's API documentation, is there
some kind of
> > introductory material to how the qmake buildsystem
works?
>
> Well, I started a bit on  that, and now I'm really
confused. According
> to the docs KDevBuildTool is deprecated, however the
> qmakeprojectpart.cpp still subclasses it and is the
class used for qmake
> support.
>
> Then there's buildtools/projectmanager/importers/qmake
which contains a
> KDevProjectEditor. However there's no
KDevProjectImporter...
>
> Last but not least there's the real
"parsing" stuff (.ll and .yy in
> lib/parsers/qmake)...
>
> I'm really totally confused as to which way I should
take (should I
> implement KDevProjectImporter+~Editor+~Builder, or
should I try to do
> the same as the current qmake manager does)?
>
> I'd really appreciate it if somebody (maybe as PM if
it's lengthy) could
> shed some light on this for me. Thanks in advance.
>
> Andreas

buildtools/projectmanager should be ignored for the KDevelop
3.x series. 
Please be sure to work on buildtools/qmake

Sorry for the confusion
--
Matt

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 24.07.06 19:19:42, Matt Rogers wrote:
> On Monday 24 July 2006 15:06, Andreas Pakulat wrote:
> > On 24.07.06 20:46:39, Andreas Pakulat wrote:
> > > However having browsed a bit through the
various qmake-related dirs
> > > under buildtools I'm a bit lost 
> > >
> > > Apart from KDevelop's API documentation, is
there some kind of
> > > introductory material to how the qmake
buildsystem works?
> >
> > Well, I started a bit on  that, and now I'm
really confused. According
> > to the docs KDevBuildTool is deprecated, however
the
> > qmakeprojectpart.cpp still subclasses it and is
the class used for qmake
> > support.
> >
> > Then there's
buildtools/projectmanager/importers/qmake which contains a
> > KDevProjectEditor. However there's no
KDevProjectImporter...
> >
> > Last but not least there's the real
"parsing" stuff (.ll and .yy in
> > lib/parsers/qmake)...
> >
> > I'm really totally confused as to which way I
should take (should I
> > implement KDevProjectImporter+~Editor+~Builder, or
should I try to do
> > the same as the current qmake manager does)?
> >
> > I'd really appreciate it if somebody (maybe as PM
if it's lengthy) could
> > shed some light on this for me. Thanks in advance.
> >
> > Andreas
> 
> buildtools/projectmanager should be ignored for the
KDevelop 3.x series. 
> Please be sure to work on buildtools/qmake
> 
> Sorry for the confusion

I guess part of the confusion is the small amount of
documentation how
all this works. Would be really great if that could be
improved for
KDevelop4...

Andreas

-- 
Don't look now, but the man in the moon is laughing at you.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Tuesday 25 July 2006 6:58 am, Andreas Pakulat wrote:
> I guess part of the confusion is the small amount of
documentation how
> all this works. Would be really great if that could be
improved for
> KDevelop4...

This is an absolute necessity.  We recognize it.  However,
at the moment, 
things are changing so rapidly that any kind of overall
guide to the 
KDevelop4 API is premature.  I'm trying to document changes
and new methods, 
but in the end we're going to need an API review and a real
effort to 
document the overrall design and broad scope of the API.

Adam

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 24.07.06 19:19:42, Matt Rogers wrote:
> On Monday 24 July 2006 15:06, Andreas Pakulat wrote:
> > On 24.07.06 20:46:39, Andreas Pakulat wrote:
> > > However having browsed a bit through the
various qmake-related dirs
> > > under buildtools I'm a bit lost 
> > >
> > > Apart from KDevelop's API documentation, is
there some kind of
> > > introductory material to how the qmake
buildsystem works?
> >
> > Well, I started a bit on  that, and now I'm
really confused. According
> > to the docs KDevBuildTool is deprecated, however
the
> > qmakeprojectpart.cpp still subclasses it and is
the class used for qmake
> > support.
> >
> > Then there's
buildtools/projectmanager/importers/qmake which contains a
> > KDevProjectEditor. However there's no
KDevProjectImporter...
> >
> > Last but not least there's the real
"parsing" stuff (.ll and .yy in
> > lib/parsers/qmake)...
> >
> > I'm really totally confused as to which way I
should take (should I
> > implement KDevProjectImporter+~Editor+~Builder, or
should I try to do
> > the same as the current qmake manager does)?
> >
> > I'd really appreciate it if somebody (maybe as PM
if it's lengthy) could
> > shed some light on this for me. Thanks in advance.
> >
> > Andreas
> 
> buildtools/projectmanager should be ignored for the
KDevelop 3.x series. 

And buildtools/lib/parsers as well, I guess? Because I can
only see the
parser beeing used in buildtools/projectmanager/qmake and
nowhere else.

Well, this means that qmake support is
"hardcoded", which explains why
so much stuff doesn't work.

So I'm going to fork buildtools/qmake as qmake4 and I think
I should get
a svn account before to do this in a separate branch inside
SVN...

Andreas

-- 
You are fairminded, just and loving.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On 25.07.06 19:44:35, Andreas Pakulat wrote:
> On 24.07.06 19:19:42, Matt Rogers wrote:
> > buildtools/projectmanager should be ignored for
the KDevelop 3.x series. 
> 
> And buildtools/lib/parsers as well, I guess? Because I
can only see the
> parser beeing used in buildtools/projectmanager/qmake
and nowhere else.

Having looked a bit at the parser, I've got one last
question: Are there
objections against using it for qmake4 support? I think it
would make
things easier for me as I don't have to fully understand
the FileBuffer
(which seems to be the parser for qmake projects atm) class,
I'd only
have to provide similar functionality using the AST...

Andreas

-- 
Excellent day for putting Slinkies on an escalator.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel