[Qt-interest] Status of XCode Integration

[Dan White]

----- Michael Jackson <mike.jackson at bluequartz.net> wrote:
> On 3/16/10 3:50 PM, in article 4B9FE108.10404 at fxtech.com, "Paul Miller"
> wrote:
> 
> > On 3/16/2010 1:53 PM, Dan White wrote:
> >> The info at the link is rather confusing.
> >> 
> >> To me, it is a no-brainer.
> >> 
> >> Once I have a .pro file, either from qmake -project or by hand editing, I
> >> just give the qmake command and create an XCode project file.  Everything
> >> just works from there.
> >> 
> >> If the project grows in such a way as to cause the contents of the .pro file
> >> to change, you need to regenerate the XCode project file.  Because I can do
> >> this, I do not maintain the XCode project file.  I trash it and rebuild it as
> >> needed.
> > 
> > The problem with this is if you change any signals/slots or add new
> > headers that need to be moc'd. It would be nice if the moc steps would
> > automatically be built like they are with the Visual Studio add-in.
> 
> Certainly do NOT want to start a qmake/cmake flame war BUT  CMake will
> correctly regenerate the moc/uic files when needed. You just need to update
> the CMake file with the new headers that need to be moc'ed and CMake will
> regenerate the Xcode project for you. During the build some auto-magical
> thing happens and my moc'ed headers are regenerated when needed.
> 
> Just my 2 cents
> Mike Jackson

This seems to me to be no different than updating the .pro file and running qmake to regen the Xcode project file.

“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)