On sábado, 17 de setembro de 2016 11:23:12 PDT Oswald Buddenhagen wrote: > On Thu, Sep 15, 2016 at 07:51:16PM -0700, Thiago Macieira wrote: > > On quinta-feira, 15 de setembro de 2016 18:33:24 PDT Thiago Macieira wrote: > > > Ok, just to be sure, I've nuked EVERYTHING from another build and it > > > also > > > > > happens: > > I've reduce this to this commit: > after this commit, qtbase is still _supposed_ to configure stand-alone, > provided there are *no* build artifacts from qt5.git (look for hidden > files). > admittedly, i never tested this configuration, but i thought CI does (it > builds every module separately, supposedly without a top-level tree).
So how am I going to reconfigure qtbase once I've built the rest of qt5? My workflow is: cd qtbase configure make repeat for a month cd .. # to qt5.git qmake && make -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development