It gives you 2 bytes wchar_t but there are these other problems people where saying. English will probably work. But Hebrew? I'm not sure!
Subhobroto Sinha wrote:
The program runs on Windows just fine because Windows Unicode function expects wchar_t to be 2 bytes (unlike GNU's) which is what it gets..
So the program runs on wine correctly too...
But I want the app to be a native ELF using GLibc's own Internal functions...
I have assumed that the user may not have WINE
Regards
On Sun, 28 Dec 2003 Dan Kegel wrote :
Dan Kegel wrote:
I'm way out of touch with Wine these days, but here's[ meant to say "my two bits"... obviously my mind is wandering... ]
1. If you want to get something useful done, switch to C. Mixing g++ and Winelib seems to be a bit tricky, and you might end up spending all your time on that instead of solving the problem you originally wanted to solve.
2. If you insist on using C++:
if the problem resists analysis, perhaps you could use Valgrind
to help track down the problem.
3. Compile with MS Visual C++. I run MSVC++ 4.0 on Wine just fine, and I bet even newer versions will run the commandline versions of the compilers ok on wine.
#3 really is the best option, since then your app will run fine both on Windows and on Wine...
- Dan
