[Qt-interest] Status of XCode Integration

[Andreas Pakulat]

On 17.03.10 09:56:46, Thiago Macieira wrote:
> Em Quarta-feira 17 Março 2010, às 07:52:42, Andreas Pakulat escreveu:
> > On 16.03.10 16:32:01, Trygve Isaacson wrote:
> > > On Tue, Mar 16, 2010 at 1:46 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > > ...
> > > 
> > > > I don't know about XCode (for either qmake or cmake) but the makefile
> > > > generated by both tools automatically re-run them in the case of
> > > > changing their inputfiles (i.e. .pro or cmakelists.txt). So its even
> > > > automatic as long as you maintain the original cmake/qmake project
> > > > file.
> > > 
> > > ...
> > > 
> > > My experience with XCode is similar. You obviously need to run qmake
> > > to regenerate the project if you add or remove files in .pro files,
> > > and less obviously if you change an existing class so that it becomes
> > > Q_OBJECT-enabled (starts needing moc). But if you are merely
> > > adding/changing signals and slots on classes that already are declared
> > > Q_OBJECT, then XCode will re-moc those classes automatically as needed
> > > whenever you build.
> > 
> > Thats not what Makefiles do, Makefile's re-run qmake completely
> > automatically if the generated Makefile is older than qmake's .pro file
> > (the same for cmake files). So adding new files or adding Q_OBJECT
> > macro's is no problem, I still just run make and it'll re-run qmake for
> > me.
> 
> Adding new Q_OBJECT macros to existing files won't cause qmake to be rerun.
> 
> If you do that and you didn't touch the .pro file, you have to cause qmake to 
> be rerun. You can do that by:

Right, but I wouldn't list header files without Q_OBJECT macro in the .pro
file anyway, so I'd have to add them there after adding the macro and hence
touching the file.

Andreas

-- 
You are always busy.