On Thursday, December 01, 2011 01:58:31 you wrote: > On Thursday 01 December 2011 01:16:53 Stephen Kelly wrote: > > On Wednesday, November 30, 2011 11:01:32 Thiago Macieira wrote: > > > On Wednesday, 30 de November de 2011 19.01.53, Alexander Neundorf wrote: > > > > > For now I'm interested in floating the general idea of > > > > > putting > > > > > build-time- tools into qtbase.git instead of qttools.git. > > > > > > > > Sounds reasonable IMO. > > > > > > Agreed. > > > > > > HarryF has done some work for the Fremantle port of Qt to make > > > qdbusxxx2xxx be bootstrapped. I don't know, however, if lupdate and > > > lrelease can be or have been bootstrapped. They should be, if > > > possible, > > > so they are built with the host compiler, not the target one when > > > cross-compiling. > > > > I think I'm missing something here. > > > > Is this a blocker to moving them into qtbase.git? Can the bootstrapping > > happen even after moving them? > > It is not a blocker. > > AFAIK, bootstraping allow to run the tool on the host (when crosscompiling) > that is required since you need to generate your .cpp on the host so they > can be compiled on the host
Yes, I understand the need to have the tools compiled for the host architecture when cross compiling, but I don't understand why that was brought up in the context of moving the source code for the tools to a different repo. It is probably just unrelated. Thanks, -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
