I know I asked this before, but just to make double-dog-sure I got this right...
Is this unicode stuff only concerning compiling Harbour on Windows, or creating .EXEs from Clipper code with Harbour on Windows. I believe the answer is "both" but I get messed up from time to time. Thanks Viktor On Wed, Mar 3, 2010 at 12:51 AM, Viktor Szakáts <harbour...@syenar.hu>wrote: > > I thought I'd start this out as I don't really understand a lot of the > Changelog stuff in layman's terms. > > > > Fact: Win9x OS's will need a unicows.dll file to work in future .exe > compiles generated by Harbour. > > Not exactly. > > The _default_ Harbour build will need unicows.dll. > Anyone, anytime may create a non-UNICODE Harbour build > by using HB_BUILD_UNICODE=no. > > > Question: Does that mean if I just download and include 1 single file, > unicows.dll in the path where the generated .exe's are put and executed > from, everything will magically work for Win9x => Windows 7 64-bit type > OS's? > > Unfortunately no. I've written detailed description > on the method a few days ago on this list. But of > course there are several general descriptions about > it on MS website and other places. > > It doesn't currently work reliably with Harbour though. > > Brgds, > Viktor > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > -- smu johnson <smujohn...@gmail.com>
_______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
