User forums > Nightly builds

The 16 april 2006 build will NOT be out.

<< < (2/3) > >>

alanwong:

--- Quote from: Takeshi Miya on April 17, 2006, 07:30:00 am ---
--- Quote from: alanwong on April 17, 2006, 05:20:42 am ---Why I can't succeed compile for wxWidgets application .

--- End quote ---


--- Quote ---main.cpp:91:1: converting to execution character set: Illegal byte sequence
main.cpp:108:1: converting to execution character set: Illegal byte sequence

--- End quote ---

That is because you have chinese characters (hanzis) on line 91 and 108. I don't know if GCC supports source files encoded in unicode (and if it supports, what type of encodings it supports), but certainly your actual configuration doesn't.

You can solve it in multiple ways, these are one of them:
1) Investigate if GCC supports unicode for source files, and if so, what encoding.
2) Use another compiler. For example, MSVC latest versions support UTF-8 and UTF-16 source files.
3) Don't use any unicode chars (use only ASCII chars) in your source files, and write all texts in plain english.
This is the most common way, and you will not loose unicode at all, because you can later translate the english texts to any language at runtime, using gettext catalogs. For creating the catalogs, here is a good GUI: http://www.poedit.org

Regards,
Takeshi Miya

--- End quote ---


thank you, Takeshi Miya

I think that GCC supports unicode for source files (with GCC3.4.5), because it is succeed compiled as follows:
#include <iostream>
using namespace std;
int ()
{
  cout<<"中国"<<endl;
  return 0;
}

alanwong:

--- Quote from: alanwong on April 17, 2006, 08:17:49 am ---
--- Quote from: Takeshi Miya on April 17, 2006, 07:30:00 am ---
--- Quote from: alanwong on April 17, 2006, 05:20:42 am ---Why I can't succeed compile for wxWidgets application .

--- End quote ---


--- Quote ---main.cpp:91:1: converting to execution character set: Illegal byte sequence
main.cpp:108:1: converting to execution character set: Illegal byte sequence

--- End quote ---

That is because you have chinese characters (hanzis) on line 91 and 108. I don't know if GCC supports source files encoded in unicode (and if it supports, what type of encodings it supports), but certainly your actual configuration doesn't.

You can solve it in multiple ways, these are one of them:
1) Investigate if GCC supports unicode for source files, and if so, what encoding.
2) Use another compiler. For example, MSVC latest versions support UTF-8 and UTF-16 source files.
3) Don't use any unicode chars (use only ASCII chars) in your source files, and write all texts in plain english.
This is the most common way, and you will not loose unicode at all, because you can later translate the english texts to any language at runtime, using gettext catalogs. For creating the catalogs, here is a good GUI: http://www.poedit.org

Regards,
Takeshi Miya

--- End quote ---


thank you, Takeshi Miya

I think that GCC supports unicode for source files (with GCC3.4.5), because it is succeed compiled as follows:
#include <iostream>
using namespace std;
int ()
{
  cout<<"中国"<<endl;
  return 0;
}

--- End quote ---


Because I don't want Use another compiler. For example, MSVC,  so I select code::blocks.

thomas:

--- Quote from: alanwong on April 17, 2006, 05:20:42 am ---Why I can't succeed compile for wxWidgets application .

--- End quote ---
Thank you for being so kind as to not posting your general problems into this completely unrelated thread.

mmkider:
sorry for thomas.

I reply this question.
you need to select ANSI-mode, because you keyin word that it is local code (GB2312)and not UNICODE.

I try compling this file between ANSI-mode and UNICODE-mode, and it's sucess with ANSI-mode.

Conan Kudo:
Where is our ANSI build?? The latest ANSI build is two weeks old! We need a new ANSI build for our Windows 9x friends! Of course, if a libunicows build is prepared instead, that is OK too....

Navigation

[0] Message Index

[#] Next page

[*] Previous page