Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on October 19, 2017, 07:02:46 pm
-
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 (http://forums.codeblocks.org/index.php/topic,3232.0.html).
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-2.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 19 October 2017 build is out.
- Windows :
http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2017/CB_20171019_rev11210_win32.7z
- Linux :
none
The current SDK version is : 1.32.0
Resolved Fixed:
- sdk: Make sure we show an error message box when we cannot save the config file
- Replace the cbMessageBox with AnnoyingDialog which makes it possible to retry the saving of the config file
- CC: Make sure to correctly disable the checkboxes in the Symbol browser settings (thanks ollydbg)
- compiler: Add -std=c++14 and -std=gnu++14 to the list of C++ only flags (format the file to be a bit more readable)
- compiler: Clean up the clang flags a bit and add the common sort options
- SDK: Fix crash when reading truncated config file
- SDK: Return false if there are errors reading a xml file with tinyxml
- SDK: Allow the user to discard old config file if it fails to load
- CC: Make the size of toolbar controls configurable in the settings (ticket #303, thanks ollydbg)
- CC: Fix doxygen spelling in the settings panel
- updated exchndl (crash handler) to v0.8.2
- Scintilla: Prevent sending EVT_MOUSE_CAPTURE_LOST while opening a context menu in wxSTC
- wx30: Fix assert when closing the application during long compilation
- UI: Add 'Enable both' and 'Disable both' menu items in the Options submenu for the files in the project tree
- UI: Add update ui processing for the File -> Properties menu item
- UI: Remove 'Save All', 'Save all projects' and 'Close all project' menu items from the File menu
- UI: Clean up the UpdateUI behaviour of the File menu items
- UI: Make sure that menu items in the context menu in Projects tab are correctly enabled/disabled
- UI: Notify the user that there is running compilation during quit and ask if he/she wants to stop it
- SourceExporter/NassiShneiderman: Make sure only one File -> Export menu is created no matter which plugin is created first
- sdk: Introduce an API which can be used to get the list of compiler plugins from the plugin manager
- sdk: Make PluginManager::GetPlugins to be const and to return const object
- UI: Make sure that menu items in the Project menu are correctly disabled
Regressions/Confirmed/Annoying/Common bugs:
-
ok.. BUT
"UI: Remove 'Save All', 'Save all projects' and 'Close all project' menu items from the File menu"
This sucks... why remove it?! :/
-
'Save All', 'Save all projects'
Are the same as "Save everything". Where is the difference between "Save all" and "Save all projects"?
'Close all project'
Same as "Close workspace"
-
'Save All', 'Save all projects'
Are the same as "Save everything"
'Close all project'
Same as "Close workspace"
lol ooh oook.... ;)
-
Is there some reason for still using wxWidgets 2.8?
-
No one is doing the build for windows with wx28. I think Morten could and will provide experimental builds with 3.x
-
"experimental" lol.. ;)
-
No one is doing the build for windows with wx28. I think Morten could and will provide experimental builds with 3.x
I'm confused - you mean no one is doing the build without wx28 or you mean with wx3.x?
I've attempted 32bit & 64bit windows builds with 3.0.3 & 3.1.0 which kind of work but seem to end up with odd delays while typing/highlighting things and selections randomly adding to the previous selection. 2.8 seems much more stable on windows so I was wondering if there's a deliberate decision to remain with 2.8 for windows.
-
I'm confused - you mean no one is doing the build without wx28 or you mean with wx3.x?
I meant wx3.x, sorry...
The wx3.x build won't get any more stable if we don't start to provide build so people can report problem with them...
-
we can do build with wx30 or 31. But as mentioned in another post, we need to decide on which wx3.x.
By default linux distros will have a wx 3.0.x, and it seems that for windows we probably would best use wx 3.1 ?
Wx 3.1 is beta beta, not adviced for production, things is those wx guys are extremely slow in coming up with release, and for sure with a decent wx3.x.
Note, at the mean time we would aslo switch to 64but windows builds and no longer do 32 bits.
I have such wx31 64 bit builds in the pipeline, I had a working build (or at least it seemed like that, well one plug-in was causing havoc but that has been fixed) 3 months ago.
-
I have such wx31 64 bit builds in the pipeline, I had a working build (or at least it seemed like that, well one plug-in was causing havoc but that has been fixed) 3 months ago.
wx3.1 for sure. This is the only one which allows hidpi on windows and this is one problem we need to tackle soon.
So post the builds and lets see what happens. :)
-
we can do build with wx30 or 31. But as mentioned in another post, we need to decide on which wx3.x.
By default linux distros will have a wx 3.0.x, and it seems that for windows we probably would best use wx 3.1 ?
Wx 3.1 is beta beta, not advised for production, things is those wx guys are extremely slow in coming up with release, and for sure with a decent wx3.x.
Note, at the mean time we would also switch to 64bit windows builds and no longer do 32 bits.
I have such wx(v3.1)(64 bit) builds in the pipeline, I had a working build (or at least it seemed like that, well one plug-in was causing havoc but that has been fixed) 3 months ago.
I use Windows 7 ULTIMATE SP1 x64 FOREVER MORE!
so a 64bit build would be great...
lol ooh yah LET the BUG HUNT BEGIN!! ;) :P
So post the builds and lets see what happens. :)
lol ohh yah let er ripp
-
I have such wx31 64 bit builds in the pipeline, I had a working build (or at least it seemed like that, well one plug-in was causing havoc but that has been fixed) 3 months ago.
Do you see the crash issue I reported here: Threadsearch plugin cause crash when initilized (wx3.1,C::B svn head) (http://forums.codeblocks.org/index.php/topic,22198.0.html)?
-
'Save All', 'Save all projects'
Are the same as "Save everything". Where is the difference between "Save all" and "Save all projects"?
'Close all project'
Same as "Close workspace"
... keyboard shortcut Ctrl-Shift S is no more saving all files (doing nothing now).
Should the default keyboard shortcuts, in menu Setting/Editors/Keyboard shortcuts/'Save everything', be updated to add an additional one (Ctrl-Shift S) ?
-
Unfortunately the key binder is interfering with the default shortcuts here.
I've changed the ctrl-shirt-s to be file ->everything, but in the past file -> save everything has been assigned the alt-shift-s short cut.
This is saved in the config of the keybinder and now it is reset and the default is lost.
I'll think about a solution, because I suppose this will affect many people.
Thanks for reporting.
-
I just checked and updated, the build I had prepared is a wx30. I will start with that one somewhere this weekend, and then next week prepare a wx31.
-
I just checked and updated, the build I had prepared is a wx30. I will start with that one somewhere this weekend, and then next week prepare a wx31.
thx, its about time we move on from WxWidgets (v2.8) lol ;)
because as I noticed the project files.. only the Wx(v3) files had a cbp for 64bit builds... ;)