jadooo wrote:
Thanks a lot for the valuable information.
I am trying to port my application developed in linux to windows, now as
it is quiet clear that I could not use cygwin, due to lack of Unicode
support,
is there any other alternative to try out my porting activity.
---
Linux doesn't support double-wide characters in its
system calls -- it's all in 'glibc'.
Cygwin doesn't need to support unicode anymore than
the linux kernel does. It's whoever built the gcc/glib
packages that needs to supply that application-level (not
system-level) datatype.
In the same way, gcc/glib supports 64-bit data types
on 32-bit machines and the glib file I/O transparently supports
64-bit file offsets even on 32-bit machines.
But, AFAIK, glib doesn't support calling the standard
*nix file-io calls with 'wchar' comprised wstrings.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
