User forums > Nightly builds

The 10 May 2018 build (11400) is out.

(1/3) > >>

killerbot:

IMPORTANT : THIS IS THE FIRST BUILD THAT USES WX 311 AND IS A 64 BIT APPLICATION.



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(s) for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw31u_gcc_cb_wx311_gcc510-TDM.7z


The 10 May 2018 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2018/CB_20180510_rev11400_win64.7z
  - Linux :
   none

The current SDK version is : 1.36.0

Resolved Fixed:


* wxSmith: Fix assert when using the wxGridBagSizer (ticket #664, thanks bluehazzard)
* editor config: Make it possible to type in the syntax highlight preview
* debugger: Make the line for the current possition during debugging to use the same colour as the caret line (ticket #659)
* envvars: Using the configuration dialog could set incorrect variables (ticket #641, thanks homertp)
* SmartIndent: Improve brace completion for Fortran (ticket #667, thanks darmar)
* UI: Prevent the splash screen from staying on top from the compiler selector dialog
* rnggen: Better explanation of the purpose and usage of the plugin (ticket #648, thanks Miguel Gimenez)
* BrowseTracker - Internationalize ConfigPanel
* scintilla-patch: Fix occurrence highlight rendering after the update to 3.7.x when building with wx2.8 on Windows (ticket #681)
Regressions/Confirmed/Annoying/Common bugs:

ivan braga:
As an image speaks more than a thousand words.

After compiling wxwidgets 3.1.1 with the following command:

../configure --enable-debug \
        --with-opengl \
        --enable-xrc \
        --enable-monolithic \
        --enable-unicode

I compiled the code :: blocks with the following command:

./bootstrap
./configure --prefix = / opt / codeblocks --with-contrib-plugins = all

Everything followed without errors, but when I try to execute the code :: blocks, what happens in the image happens.

It remains stuck in the startup screen, and begins to consume all ram, until the system hangs.

Any suggestions for solving the problem?

oBFusCATed:
Use gdb to find out where it is stuck.
Another option is to use memory tracking tool like heaptrack to see where the memory is being allocated.

cyuyan:
When I drag the toolbar back and forth, something will happen below. Please look at the picture.

oBFusCATed:
cyuyan:
What is the DPI of your monitor?
What is the scaling in windows you've set?
Are you using windows in the first place?
Which windows version or os version?
What is the size of the toolbar icons?

Navigation

[0] Message Index

[#] Next page