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

Standard build environment: wx-2.6/unicode

<< < (2/4) > >>

killerbot:
devpak plug-in warnings :
 ../../../sdk/sdk.h.gch not used because wxUSE_UNICODE is defined.

I hope this is ok, how to get rid of that warning ??

killerbot:
okay okay, seems I am not having a good day.
It is obvious I should use CodeBlocks-NewBuild-UNI.cbp and not the CodeBlocks-NewBuild.cbp (so the previous things I noticed should be considered garbage).

Question : since the official product will be the unicode build, does it make sense to keep the build file for the ansi one ??

tiwag:

--- Quote from: Takeshi Miya on December 29, 2005, 12:28:30 pm ---Now:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb

--- End quote ---

i would propose to use for the future a slightly modified build, with added version number of used wxwidgets version number
otherwise the produced shared library has the same name when using wx261 or wx262 which sometimes is annoying.

my proposal for future usage,
append wxwidgets version+release to VENDOR string

for wxwidgets 2.6.1

--- Code: ---mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb261
--- End code ---

for wxwidgets 2.6.2

--- Code: ---mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb262
--- End code ---

and so on ... ( when wxwidgets community releases newer versions then ... )

this would also clearify which wxwidgets version was used by a specific developer ( thinking of SVN binaries downloads )

What's your opion ?

tiwag:

--- Quote from: mandrav on December 29, 2005, 10:34:54 am ---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.

--- End quote ---

Hi Yiannis

i've just now built a new wx262 unicode build of CB and got these warnings

did you notice it too ?!

[edit]
same problem

src\plugins\contrib\source_exporter\wxPdfDocument\src\pdffont.cpp:910

--- Code: ---    if (c >= 0 && c < 128)
--- End code ---



[attachment deleted by admin]

mandrav:

--- Quote from: tiwag on December 29, 2005, 03:47:30 pm ---Hi Yiannis

i've just now built a new wx262 unicode build of CB and got these warnings

did you notice it too ?!

--- End quote ---

Yes I did.

Navigation

[0] Message Index

[#] Next page

[*] Previous page