On 5/22/12 7:12pm, Till Oliver Knoll wrote: > Don't you have the same problem (how to automate the moc/ui step > within XCode) when building an executable?
Well, if I simply use a text editor, I'd rely on the console. That would be "automated" by qmake. However, with Xcode, things might get easier (code completion, on the fly errors/warnings, and so on). > Or how exactly does trying to build a library complicate matters? Why > the distinction? Isn't your question more like "How to integrate Qt > build steps into XCode"? That would be a question, but I don't find anywhere a good integration for Qt and Xcode, at least, I didn't find anything satisfying. > By the way, unless you find a way to add "custom build steps" (which > you would still need to setup manually!) I don't know how to > integrate Qt's moc and uic steps into XCode. I actually do this: in a custom script build phase, I create a qmake project, then the makefile, and build mocs/uis; finally I create a static library that I add to my Xcode project. It works just fine, but it isn't that clean: I didn't find a way to have a nice list of Qt byproducts (mocs/uis), so I am using a trivial loop. Any suggestion on how to improve this is welcome! _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
