i tried to cancel the preprocessor setting _UNICODE/UNICODE in embedded
visual c++ : but when i build the code i get an unresolved external of
'CreateFileA' error
i use 'CreateFile' for serial communication but have some trouble with
unicode converting (see other thread),so i thinked about disabling unicode ...
Paul T.
"mfuser" <mfu...@discussions.microsoft.com> wrote in message
news:52EC56FE-3586-4846...@microsoft.com...
No.
> i tried to cancel the preprocessor setting _UNICODE/UNICODE in embedded
> visual c++ : but when i build the code i get an unresolved external of
> 'CreateFileA' error
Yes, 99% of the *A functions just don't exist under CE. The whole system is
built on WCHAR (just like the NT series) but it doesn't contain the
wrappers for CHAR to save space.
> i use 'CreateFile' for serial communication but have some trouble with
> unicode converting (see other thread),so i thinked about disabling unicode
Two things:
- That problem is trivial (see other thread).
- You get rid of some overhead and gain some flexibility even when compiling
for the desktop. Actually, when porting, I suggest you first make the code
compile cleanly with _UNICODE/UNICODE on the desktop and then start porting
to CE.
Uli
--
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932