> Maybe I missed to mention that the Qt tests are passed just in the case of > forcing the C++ mode in the whole harbour build. If we force the C++ mode > just in hbide, demoxbp and demoqt build, the resulting executables crashes > in different points.
That's very bad news. QT 4.6.0 seems to be a royal mess up. It has such stupid, but most importantly _global_ requirements that probably I'll have to skip it from unified builds :( This is simply insane. For MSVC they are forcing to use -MD switch which forces _all_ other dependencies to be rebuilt using this option making everything incompatible. With MINGW they force us to use a basically not released compiler version, plus C++ mode on the whole project... Or - which I don't know - on _every projects_ which are linked to an executable wanting to use QT 4.6 ? I'd like to recommend to stick with 4.5.2 until these issues are cleared up. > @set HB_USER_LDFLAGS=-static-libgcc > @set HB_USER_DFLAGS=-static-libgcc Can you tell, what these options are doing? > As I understand correctly the Qt integration is crucial for the whole > project future, that’s why I spent some time with this issue. It used to be, but now I seriously wonder if we're on the right path with QT. If QT requires us to design the whole project and all dependencies around it, it doesn't look very good to me. We're not a QT only project that's for sure, and I miss the luxury option to create a separate build of everything just for the sake of one lib. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
