It can compile and work using Windows's Unicode API.
This was needed for WinCE, because this one doesn't
have a non-Unicode (ANSI) API.
Internally, Harbour isn't Unicode though, which means
a conversion is needed for all strings, when interfacing
with Unicode APIs.
Brgds,
Viktor
On 2008.08.26., at 11:32, Massimo Belgrano wrote:
Wich kind of unicode support have Harbour now?
-----Messaggio originale-----
Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] Per conto di Szakáts Viktor
Inviato: martedì 26 agosto 2008 11.19
A: José Luis Capel
Cc: 'Harbour Project Main Developer List.'
Oggetto: Re: [Harbour] 2008-08-26 00:43 UTC+0200 Viktor
Szakats(harbour.01syenar hu)
Hi Jose,
Does it mean that my sets have to be as shown bellow ?
SET HB_BUILD_WINCE=yes
SET HB_CC_NAME=vcce
SET HB_ARCHITECTURE=w32
SET HB_GT_LIB=gtgui
SET HB_GT_DEFAULT=gui
SET HB_VISUALC_VER=60
SET HB_BUILD_MODE=c
SET CLIBFLAGS=-DHB_OS_WIN_32 -DHB_WINCE -DHB_GTGUI_HACK -
DHARBOUR_MAIN_WIN
-DHB_TR_LEVEL_ALWAYS -DUNICODE
SET HB_BUILD_DLL=yes
Yes. I'd suggest to remove -DHB_OS_WIN_32, -DHB_WINCE and
-DUNICODE. These are either autodetected or #defined by
the make files, so they are all unnecessary on user level.
I'd also recommend using C_USR instead of CLIBFLAGS.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
