> Hi Viktor, > >>> For me this are two different things. >>> 1. broken watcom binaries due to forces stack calling convention. >> It's broken either way. Default is broken for OLE servers, >> special build is broken for non-watcom Harbour .dlls. > > The default build is broken for any OLE code and maybe some other > type of code. And it's broken for very long time. The problem was > reported few times to this list in the past, i.e. in last year Marek > reported it and because we haven't fixed it then he droped OpenWatcom > and switched to MinGW. Probably also many other users changed C compiler > and now no one reports problems with OpenWatcom builds. In summary > MS-Windows OpenWatcom builds has been not usable for users who need > some functionality like OLE for over year. > The problem with harbour.DLL exists only for users who want to > mix C compilers and use harbour.dll compiled by different C compiler > then the one used for static libraries and user code what is not > a problem for users who do not plan to make such mix.
It's a problem for all users trying to use the unified Windows builds in watcom -shared mode. The other is a problem for users who want to use OLE. The point is: It's broken in both ways, just differently. If it helps I can delete win/watcom target from unified package, which solves my concern, though it's far from a proper solution. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
