From: Alo Sarv (alo.sarv_at_[hidden])
Date: 2005-12-07 23:39:20
> > Well I have to say I'm a totally incompetent when it comes to QT. And
> > I can't even begin to test your patches. So could someone else please
> > do some tests so I can be sure it's not going to cause havoc :-)
Since my main interest in the topic is building the QT4 free edition
with MSVC, I did some testing of the jamfiles on win32, both mingw and
msvc8.0 configurations. Here's my findings and recommended fixes:
1. The alias platform_sources-mechanism in corelib/Jamfile (and
possibly elsewhere as well) doesn't seem to work. On windows, it's
complaining that io/qprocess_unix.cpp doesn't exist. Commenting out
the entire linux-version of platform_sources solves the problem.
2. io/qabstractfileengine.cpp doesn't exist in the qt win32 source
tarball, so it should probably be moved to linux-specific source
3. In corelib/Jamfile, you'll want to use
<link>shared:<define>QT_MAKEDLL and <link>shared:<define>QT_DLL (fixes
mingw-builds on win32). Probably similar change in other places.
4. For msvc, we need to copy mkspecs/win32-g++ to mkspecs/win32-msvc.
So far, qtcore built with this correctly, but maybe we need to make
some tweaks there later on.
After this, qtcore technically compiles with both mingw (after
commenting out the gcc4-specific flags) and msvc, however something
seems to be broken related to mocing - from what I can see, mocing
isn't done at all for some reason. There's no error/warning that I can
find, it just complains about failure to include moc_qbuffer.cpp or
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk