Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

CodeBlock Unicode conversion

<< < (3/4) > >>

RShadow:
I have noticed the CVS version of C::B has most of the string literals wrapped in _();  However C::B still fails to compile against a unicode version of wxWidgets.   I'm starting to fix a lot of the unicode compile errors that still exist, however I'm wondering if anybody is activily working on this?  I don't want to start doing work that is already being done :)

David Perfors:
Unless I had plans to work on it, I never did :oops: I hope you all could forgive me, I had other things to do.

mandrav:

--- Quote from: RShadow ---I have noticed the CVS version of C::B has most of the string literals wrapped in _();  However C::B still fails to compile against a unicode version of wxWidgets.   I'm starting to fix a lot of the unicode compile errors that still exist, however I'm wondering if anybody is activily working on this?  I don't want to start doing work that is already being done :)
--- End quote ---

Mispunt was supposed to do it, but as you see he's been busy lately.
So, feel free to work on it :)

Yiannis.

David Perfors:
One of the reasons I put it aside was that I was unable to compile the sdk (which doesn't need the unicode support as far as I know). I get errors at the xrc part:

--- Code: ---C:\Development\wxbuild\2.4.2\lib/libwxxrc.a(xmlres.o):xmlres.cpp:(.text$_ZN12wxObjectList10CreateNodeEP10wxNodeBaseS1_PvRK9wxListKey[wxObjectList::CreateNode(wxNodeBase*, wxNodeBase*, void*, wxListKey const&)]+0x42): variable 'vtable for wxObjectListNode' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
C:\Development\wxbuild\2.4.2\lib/libwxxrc.a(xmlres.o):xmlres.cpp:(.text+0x7d1): variable 'vtable for wxObject' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.

--- End code ---

(just the first two lines)

I don't know if you get the same message RShadow? I only get it on windows (I thought...)

RShadow:

--- Quote from: mispunt ---One of the reasons I put it aside was that I was unable to compile the sdk (which doesn't need the unicode support as far as I know). I get errors at the xrc part:

--- Code: ---C:\Development\wxbuild\2.4.2\lib/libwxxrc.a(xmlres.o):xmlres.cpp:(.text$_ZN12wxObjectList10CreateNodeEP10wxNodeBaseS1_PvRK9wxListKey[wxObjectList::CreateNode(wxNodeBase*, wxNodeBase*, void*, wxListKey const&)]+0x42): variable 'vtable for wxObjectListNode' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
C:\Development\wxbuild\2.4.2\lib/libwxxrc.a(xmlres.o):xmlres.cpp:(.text+0x7d1): variable 'vtable for wxObject' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.

--- End code ---

(just the first two lines)

I don't know if you get the same message RShadow? I only get it on windows (I thought...)
--- End quote ---


I have not got those errors (at least yet).. right now all my errors are in cbeditor (mainly the reading and setting of config variables.  They are not displayed but *anything* in double or single quotes needs to be _()'ed.

Note: But the main reason I'm so interested in unicode support is beacuse of xrc... all the XRC editors I know of for linux (XRCed and wxGlade) require a unicode version of wxGTK.. so xrc has to be unicode compatible.. but I will investigate further.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version