The 21 June 2016 build (10868) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc510-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc510-TDM.7z

The 21 June 2016 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2016/CB_20160621_rev10868_win32.7z
  - Linux :
   none

The current SDK version is : 1.30.0

Resolved Fixed:

• compiler : add support for the following options : -std==c++1y and -std=c++1z
• editor: Enable folding for newly created files (partly fixes ticket #366)
• projectoptionsmanipulator plugin: show summary of operation done at end
• projectoptionsmanipulator plugin: query the user to save all projects at end for convenience
• projectoptionsmanipulator plugin: added modified/bug-fixed patch by bluehazzard: Add possibility to change compiler
• updated exchndl (crash handler) DLL to v0.8.0
• updated wxPDFDoc library to recent GIT version to resolve licensing issues
• wxSmith: fix assert with wx3.0, due to doubled properties in some sizeritems

Regressions/Confirmed/Annoying/Common bugs:

[oBFusCATed]

Does this build fix the problem with the new flag dialog in the compiler settings?

[killerbot]

the gcc 5 problem, I don't think anything has been done for that part.

[MortenMacFly]

Does this build fix the problem with the new flag dialog in the compiler settings?

What problem?

[ollydbg]

Does this build fix the problem with the new flag dialog in the compiler settings?

What problem?

See here http://forums.next.codeblocks.org/index.php/topic,21207.msg144691.html#msg144691

[eckard_klotz]

Hello Developers.

While starting this nightly (10868) I get an warning that one plug-in could not be loaded and in the log-tab I find the following content:

C:\Tool\Development\CodeBlocks\Nightlies\2016_06_21\bin\share\codeblocks\plugins\wxSmithContribItems.dll: not loaded (missing symbols?)

This happens on a laptop with win10 (frequently updated at least once a week) and Norton 360 Online as virus scanner. Please find attached the complete Code::Blocks log-tab content after starting.

Best regards,
                    Eckard.

[oBFusCATed]

Have you installed the night build in a new separate directory or you've overrode the old nightly with the files from the new one?

[eckard_klotz]

Hello oBFusCATed

I install every nightly in its own sub folder.

Best regards,
                    Eckard.

[oBFusCATed]

Thanks, this means that something is broken in the build. Anyone else seeing this problem?

[eckard_klotz]

Hello oBFusCATed.

In the meanwhile I recognized that there was no wxSmithContribItems.dll. After some investigation I found out that it was removed by my virus-scanner (Symantec Norton 360) as result of a heuristic check. I forced Norton to restore the dll and scanned it directly without a result. Thus I sent it to Symantec and reported it as a false positive.

I've got now a response that approves that it was realy a false positive:

...
In relation to submission [3967076].

Upon further analysis and investigation we have verified your submission and, as such, the detection(s) for the following file(s) will be removed from our products:

   Filename: wxspeedbutton.dll
   MD5: 102668EE5DAF98349C3980B532CB9053
   SHA256: AC6FA0579276CB1A928AF8C841C4660163B494EF4175E7DD8AD3018585BE3752
   Result:    Whitelisting for above file is taking effect from now on.





If detection persists, please contact support:
Norton: https://support.norton.com/sp/en/us/home/current/info
SEP: https://support.symantec.com/en_US/endpoint-protection.54619.html

Decisions made by Symantec are subject to change if alterations to the Software are made over time or as classification criteria and/or the policy employed by Symantec changes over time to address the evolving landscape.

If you are a software vendor and would like to upload your software for proactive whitelisting, please complete the following form: https://submit.symantec.com/whitelist/

For more information on best practices to reduce false positives:
http://www.symantec.com/content/en/us/enterprise/white_papers/b-to_increase_downloads-instill_trust_first_WP.en-us.pdf
...

After updating Norton it is not detecting the wxSmithContribItems.dll as suspicious any more and the nightly 10868 starts without problems.

Best regards,
                    Eckard.

[New Pagodi]

On a similar note: AVG antivirus has also started falsely reporting wxspeedbutton.dll as a virus.

I just added an exception for it.

[Oleg_Sam]

This nightly build is crashes, when select global compiler options and right click to add new compiler flag for SDCC compiler on Windows7 platform. :'(

[raynebc]

That crash is a known issue:
http://forums.next.codeblocks.org/index.php/topic,21090.msg144241.html#msg144241

Avast just started throwing false positives with this nightly as well.

[ollydbg]

This nightly build is crashes, when select global compiler options and right click to add new compiler flag for SDCC compiler on Windows7 platform. :'(

It should be the bug report here: SVN build crashes when trying to editing/adding new compiler flags

[Oleg_Sam]

The build-ins variables $(PROJECT_FILE), $(PROJECT_NAME), $(PROJECT_DIR) is not changed when reloading projects. To reproduce this bug:
1. Create Console application test1.
2. Open Project build option->Pre/post build steps
3. Add Pre build steps
     echo $(PROJECT_FILE)
     echo $(PROJECT_NAME)
     echo $(PROJECT_DIR)
4. Save project test1
5. Close project test1
6. Repeat steps 1..5 for project test2
7. Load project test1
8. Rebuild test1
9. Look at the build log and see that  build-ins variables is correct (test1).
10. Close Project test1
11. Load project test2
12. Rebuild test2
13. Look at the build log and see that  build-ins variables is not correct (test1).
      Its not changed and must be test2.

This bug is in all versions CB from 16.01.
My platform is Windows7 32 bit.