[Qt-interest] Qt build discrepancies (static)

[Bob Hood]

I usually build Qt in the shared mode, and everything there is fine.
I've recently needed to build Qt statically (for an internal tool, I
don't want to have to "package" things up to distribute it), and things
don't seem to be even between the 32- and 64-bit builds.

After setting the appropriate environment ("VC\bin\vcvars32.bat" or
"VC\bin\amd64\vcvarsamd64.bat"), I configure each architecture of Qt
4.5.2 using the following command:

configure -static -debug-and-release -nomake examples -nomake demos

After each build is complete, there's quite a large difference in the
resulting distribution: The 32-bit build is more than twice the disc
footprint of the 64-bit build. I did some looking, and it turns out that
there are a number of libraries that are built for 32-bit that aren't
for 64-bit, using the same configure line. Specifically:

QtAssistantClient.lib
QtAssistantClientd.lib
QtScriptTools.lib
QtScriptToolsd.lib
QtUiTools.lib
QtUiToolsd.lib
QtWebKit.lib
QtWebKitd.lib

Now, in my current need, I can function just fine without these in the
64-bit build, but I'm wondering why they are skipped in 64-bit builds?
I'm trying to encapsulate all the "expert knowledge" for building Qt
into a Python script, and if there are additional flags needed to make
the 64-bit static build identical to the 32-bit static build, I'd
appreciate knowing them if anybody can help out here.

Thanks!


Render me gone,                       |||
Bob                                 ^(===)^
---------------------------------oOO--(_)--OOo---------------------------------
                      "If ya can't beat 'em, tariff 'em."
                                   - /Harley-Davidson Motor Company/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090706/5f8a92c5/attachment.html