On Thu, Apr 19, 2012 at 5:25 PM, Lincoln Ramsay <lincoln.ram...@nokia.com>wrote:
> On 04/20/2012 10:19 AM, ext Coda Highland wrote: > >> Traditionally, qmake was much better at this than it is now. Or at least > >> it seemed to be. > > > > It's purely an issue of SEEMING to be. In-tree builds do work for a > > good number of projects, but you start bumping into problems -- for > > example, switching between debug and release and getting the object > > files mixed up. Shadow builds are safer in general. > > This whole discussion is about shadow builds :) > > There's a very real limitation in qmake though where the number of > slashes in the source and builds trees must be the same or some things > break. > > Creator tries to enforce this by making shadow builds sit next to the > source tree. > > Some of us don't care (or aren't hit by) these qmake limitations and > want to put the build tree inside the source tree. Not an in-source > build, but a shadow build where the build directory lives under the > source tree. > > ie. > > foo.pro > foo.cpp > build/Makefile > build/foo.o > build/foo > > Creator has always warned about this but Diego claims it has stopped him > from doing this. > > huh! This has also never been a problem for me! > -- > Lincoln Ramsay - Senior Software Engineer > Qt Development Frameworks, Nokia - http://qt.nokia.com/ > _______________________________________________ > Qt-creator mailing list > Qt-creator@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
