With 4.6 qt are providing an opensource version of the Visual Studio
2008 binary packag
Qt 4.6 is pre-built using the shared C runtime (MD(d),msvcrtd.lib)
With /MD cflag we do Creates a multithreaded DLL using MSVCRT.lib.
according to list of MS complier flags and their descriptions.
Why ?
Imo Is better a choice that allow use qt
If qt find advantage of using msvcrtd.lib can't be advantage also for harbour?
Wich Disadvantage in msvcrtd.lib?
2009/12/8 Viktor Szakáts harbour...@syenar.hu:
Can -MD be predefined by harbour for msvc?
No.
Though, you can easily define it
for whether you want to link it with static (LIBCMT.LIB) or shared
(MSVCRT.LIB :: MSVCRT.DLL) library. All we have to do is to add the
following options when linking:
/NODEFAULTLIB: MSVCRT.LIB
/DEFAULTLIB: LIBCMT.LIB
This way, we can use QT MSVC Binaries with Harbour MSVC2008 default flag
(which
Why ?
Imo Is better a choice that allow use qt
Who says we don't allow QT usage? It can be used with
MinGW just as before (disregarding uncomfortable MinGW
installation of DWARF builds), and it's not us who define
the rules to use QT, it's Nokia.
If qt find advantage of using msvcrtd.lib
the
following options when linking:
/NODEFAULTLIB: MSVCRT.LIB
/DEFAULTLIB: LIBCMT.LIB
This way, we can use QT MSVC Binaries with Harbour MSVC2008 default flag
(which is MT)
Thanks for the tip Andi.
Generally this seems a little bit dangerous as both .dll and static
version of C RTL is linked
So I finally managed to use Harbour with QT for MSVC.
(just some obvious bits were missing)
So:
Whole Harbour needs to be built with -MD C compiler option,
and the final apps as well:
win-make HB_USER_CFLAGS=-MD
hbmk2 hbide.hbp -cflag=-MD
Due to beautiful nature of C++, the mingw .dlls
