[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: Status of Qt4 qmake support
From:       Ian Reinhart Geiser <geiseri () yahoo ! com>
Date:       2006-07-31 15:03:34
Message-ID: 200607311103.34541.geiseri () yahoo ! com
[Download RAW message or body]

On Sunday 30 July 2006 17:42, Andreas Pakulat wrote:
> On 30.07.06 23:05:59, Andreas Pakulat wrote:
> > On 30.07.06 15:39:30, Ian Reinhart Geiser wrote:
> > > Also, do you think the custom variable stuff I attempted is
> > > salvageable to work for custom build steps?
> >
> > I have absolutely no idea, luckily I didn't need to dive too deep into
> > the non-gui code (yet).
>
> I think custom variables should work. What I don't know if it works atm
> is something like this:
>
> CONFIG += qt console newstuff
>     ...
>     newstuff {
>         SOURCES += new.cpp
>         HEADERS += new.h
>     }
>
> I don't think it will, because the current "parser" won't remember that
> newstuff was set. We probably need the qmake parser+AST for that (well
> it could be done with the current stuff, but IMHO the work is not worth
> it).
Yeah, I think I had problems there when I was working out some KDE 3 pri files 
so I could use dcop and kconfigxt from QMake.  

> If you have example projects (either qt3 or qt4) that you can share (via
> PM if you like) that would be really great. I guess in most cases you
> can just rip off any source files and it will still be useful.
I will try to tar up a few nuggets of gold.  I have to admit I love the QMake 
build system, so I use it for everything.

> A quick test with a custom variable that is used inside the contains
> function to provide a custom scope worked so far.
I think simple cases should work, at least all the ones I had at the time 
did :)

Cheers
	-ian reinhart geiser

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]