MSVC 2008 > EXE SIZE: 6573 KB > DIFFERENCE: Links one external lib statically ( www.dosadi.com ) > RUN: PASS1 6.75 Secs > PASS2 4.97 Secs > PASS3 5.00 Secs > > BCC 5.5.1 > EXE SIZE: 6706 KB > DIFFERENCE: Links one external lib dynamically pulled via implib > RUN: PASS1 5.72 > PASS2 5.69 > PASS3 5.63 > > MINGW > EXE SIZE: 8287 KB > DIFFERENCE: Does not include above lib, does not include 2 .prgs 1 .res > RUN: PASS1 4.48 > PASS2 4.51 > PASS3 4.53 >
This can be misleading. In almost all tests msvc the fastest, mingw follows and bcc lags behind by quite much. msvc and mingw are much better supported, so it's way easier to work with them. > Personal observation: > * MINGW has the limitation not to allow more than 1 resource files ( > really a shame ). > This is false information. Just try multiple resources with hbmk2 and it should work. Resources are compiled to objects in mingw and you can link any number of such objects to an executable. > * MINGW is very tricky when you need Windows .dlls to be manipulated ( > again a severe limit ). > I'd call it the most convenient, since you don't need implibs at all, of course you can't link any .dlls with non-matching calling convention, but it this case no implib would help anyway. * BCC is handy to include any external lib because of "implib" utility > but slowest of all. > Also good to know that implib is buggy, so it will something give strange results. (openssl, libcurl) Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
