User forums > Nightly builds
The 12.11 RC2 (23 November 2012 build 8598) is out.
Teybeo:
I've just created a test file in Notepad++ with some french accents in it and saved it in UTF-8 without BOM.
In rev 8438, the accents are displayed, the encoding is shown as "UTF-8" without BOM.
In rev 8549, the accents are displayed, the encoding is shown as "UTF-8" without BOM.
In rev 8598, the accents are not displayed, the encoding is shown as "System Default".
Then I return in Notepad++ and save it as UTF-8 with BOM active
In all builds, the accents are displayed and the encoding is shown as "UTF-8" with BOM.
MortenMacFly:
--- Quote from: Teybeo on November 25, 2012, 03:10:01 pm ---I've just created a test file in Notepad++ with some french accents in it and saved it in UTF-8 without BOM.
--- End quote ---
Fixed in trunk. Thank you.
stahta01:
--- Quote from: MortenMacFly on November 24, 2012, 01:18:49 pm ---
--- Quote from: gd_on on November 24, 2012, 12:10:04 pm ---I've just tried to compile C::B svn 8604 on windows, but it complains for a new cb_release_type environment variable not defined. What are we supposed to put in it ?
--- End quote ---
Either -g or -O2.
--- End quote ---
I do not understand the use of a global variable in this location.
Would not a custom variable be a better/more correct choice?
Edit: If nothing else; would not using "cflags" instead of "base" be more correct?
--- Code: ---<Add option="$(#CB_RELEASE_TYPE)" />
--- End code ---
Tim S.
MortenMacFly:
--- Quote from: stahta01 on November 25, 2012, 03:39:09 pm ---I do not understand the use of a global variable in this location.
Would not a custom variable be a better/more correct choice?
--- End quote ---
It wouldn't work across projects in a workspace. Why this was done it to allow to compile the whole C::B workspace either in debug (-g) or release (-o2) mode. This is not doable with an envvar currently, unless its a global (OS/system) envvar. But if so and its not set you would simple have neither the one nor the other flag. GCV's are queried to the user exactly for this purpose.
I'll think of a better solution though...
Alpha:
For plugin templates, Code::Blocks already creates the global variable $(#cb), so maybe using the cflags subfield would be logical:
--- Code: ---<Add option="$(#cb.cflags)" />
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version