[Development] Enabling SSE2 by default on x86 builds (32-bit)

Oswald Buddenhagen oswald.buddenhagen at digia.com
Mon Dec 16 12:07:33 CET 2013

On Thu, Dec 12, 2013 at 10:39:04AM -0600, Rex Dieter wrote:
> Oswald Buddenhagen wrote:
> > On Thu, Dec 12, 2013 at 07:18:55AM -0600, Rex Dieter wrote:
> >> Thiago Macieira wrote:
> >> 
> >> > 3bis) distro builds Qt once with -no-sse2 and then some libs with
> >> > -config sse2
> >> 
> >> How could this be implemented exactly?
> >> 
> >> I know qtbase supports
> >> ./configure -(no-)sse2
> >> 
> >> but how for other modules like qtdeclarative that uses pure qmake?
> >> 
> > they inherit the settings from qtbase (through the mkspecs/q*.pri files).
> So now we'd need to manage >1 set of mkspecs/q*pri files for x86 builds 
> somehow?  This is starting to feel ugly.
yes, it's utterly ugly. i'd keep only the non-sse set once the build is
through (you can't configure the sse version with a different data path,
so there is really no way to avoid the file conflict).
this, of course, makes it basically impossible to make a
module-by-module build. but then, the doc build already precludes that

when thiago's proposal is properly approved, we can start thinking how
to integrate this properly upstream ...

More information about the Development mailing list