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

Standard build environment: wx-2.6/unicode

(1/4) > >>

mandrav:
As of today, all developers are advised to use wx-2.6/unicode for building C::B. This will be our officially supported platform and everyone should use it. Most (if not all) unicode related showstopper bugs have been fixed. By using the unicode version, more subtle unicode related bugs can be caught and dealt with.

I have updated all project files (*-NewBuild.cbp) to use only WX_CFG (defaults to empty) and WX_SUFFIX (defaults to 'u') macros.

takeshimiya:
Good step towards i18n :D

For the stable official builds and SVN win32 unofficial builds, I'd suggest enabling MSLU support with libunicows.
So only one executable would be needed, and it will work even on Windows 9x with Unicode support.

If some of you have doubts about MSLU working well, the last weeks I've been using it with MSLU support.
For example, poEdit is distributed that way (UNICODE=1, MSLU=1).

killerbot:
what's the correct way to build the wx dll now (should an update to the wiki be done )??

takeshimiya:
Previous:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb

Now:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb

killerbot:
just to be sure : we all need this new dll, together with it's new setup.h, don't we ?

Since I noticed the following :
 - cb still builds (only wx ansi was on my system)
 - devpak plug-in does not build with wx ansi -> compiler error : does not find the setup.h (as expected)

Strange that cb still builded ?

Navigation

[0] Message Index

[#] Next page