Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on June 08, 2019, 10:43:27 am

Title: The 08 June 2019 build (11712) is out.
Post by: killerbot on June 08, 2019, 10:43:27 am

IMPORTANT : THIS IS THE FIRT BUILD THAT USES WX 311 with 2D SUPPORT.




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(s) for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw31u_gcc_cb_wx311_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z


The 08 June 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20190608_rev11712_win64.7z
  - Linux :
   none

The current SDK version is : 1.38.0

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 08 May 2019 build (11712) is out.
Post by: oBFusCATed on June 08, 2019, 10:55:24 am
Isn't this the 08 June night build and not 08 May?  8)
Title: Re: The 08 June 2019 build (11712) is out.
Post by: killerbot on June 08, 2019, 02:05:00 pm
corrected  :-[
Title: Re: The 08 June 2019 build (11712) is out.
Post by: naseyuki on June 08, 2019, 04:43:36 pm
Thank you for C:B!

Most of the UI problems are gone! And it's seems to be fast then before on Windows!

There's a little problem however, trying to uninstall the Thread Search plugin leaves the program frozen til Windows decide to close it by force, isn't a regression since random crashes always seems to happen uninstalling or disabling plugins, but now just this one (to my knowledge) is left. (Ticket #838)
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 08, 2019, 06:34:05 pm
This is known problem. It requires major changes to be fixed properly, so it will wait for now until I find the time. It is not really critical one at least to me.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: killerbot on June 08, 2019, 07:58:23 pm
anyone seen this when building on linux :

Code
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
     };
     ^
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization
wxscolourproperty.cpp:88:5: error: cannot convert ‘const char*’ to ‘const wxChar* {aka const wchar_t*}’ in initialization

Code
gcc (SUSE Linux) 7.4.1 20190424 [gcc-7-branch revision 270538]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 08, 2019, 08:11:08 pm
Yes, this is known, too, see the discussion in ticket #687.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: BlueHazzard on June 09, 2019, 12:10:25 am
Quote from: Khram on June 08, 2019, 09:17:52 pm
Spellcheck no work !!!
Working on it: http://forums.codeblocks.org/index.php/topic,23206.0.html
be patient...
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 09, 2019, 05:16:56 am
A slight annoyance to me is that starting at some point in the nightly builds newer than the 17.12 release (at least as far back as the 3-9-2019 nightly), the font used in certain areas (title text for various window panels such as "Management" and "Breakpoints", log text in the logs panel, source file names in the tabs above the editor area) changed whereas the text in other areas remained the same (main menu titles, contents of the Projects tab in the management panel, the source code text for open files).  I can't find where to change the font to match the one used in 17.12, which I like more.

Settings>Editor>Font is set to Courier New, regular style, size 10 in all my C::B instances.  Environment settings>View>Message logs' font size is set to 8 in all my C::B instances, but the differences are easy to see (top log panel is 17.12, lower log panel is this nightly):
https://i.imgur.com/ARChuVF.jpg

I tried messing with font sizes and the "Font quality" settings in Configure editor>other editor settings, but I couldn't find how to make it look the old way.  Is there a way I can make it look the way it used to or do I just have to get used to the uglier font?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 09, 2019, 11:18:38 am
You're talking about the text in the logs aren't you?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 09, 2019, 12:31:50 pm
There are other instances like I mentioned, but the log text is the biggest one because I look at it all the time.  It looks like the "ugly" log text is possibly a Unicode font that is picking up the Japanese system locale I currently have set in Windows (I change it occasionally for testing purposes).  17.12 didn't seem to change the font to reflect the locale, notice that it doesn't display the backslashes as the yen symbol as Windows does in Japanese locale.  For both versions of Codeblocks, the spell checker language is set to US English, as is Windows's input method editor.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 09, 2019, 02:32:33 pm
This is probably hardcoded font and it doens't find it on your system. I suppose something in wx's font selection changed. If you want to do experiments check the ListCtrlLogger::UpdateSettings and TextCtrlLogger::UpdateSettings.

What happens if you build cb with latest wx-master?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: Xaviou on June 09, 2019, 06:35:18 pm
Hi.

Building this rev on OSX fails :
Code
config.status: error: cannot find input file: `src/src/resources/images/22x22/Makefile.in'

When updating with svn, I have "accepted incoming deletion" of this "22x22" folder.
Have I done something wrong ?

Regards
Xav'
Title: Re: The 08 June 2019 build (11712) is out.
Post by: Miguel Gimenez on June 09, 2019, 07:28:06 pm
The 22x22 folder is not needed anymore. Probably you must execute ./configure again
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 09, 2019, 08:28:49 pm
Xaviou: Have you run the bootstrap script?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: Xaviou on June 09, 2019, 09:46:24 pm
Hi
Quote from: oBFusCATed on June 09, 2019, 08:28:49 pm
Xaviou: Have you run the bootstrap script?
Shame on me  :-[ I didn't thought about re-running this script.
It worked : Thank you.

I also have the Linux problem reported by killerbot (http://forums.codeblocks.org/index.php/topic,23315.msg158784.html#msg158784).
Is there a solution or do we have to wait ? (I'm on a Debian Stretch using the official wx-3.0 libs).

Regards
Xav'
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 09, 2019, 10:27:57 pm
Quote from: oBFusCATed on June 09, 2019, 02:32:33 pm
This is probably hardcoded font and it doens't find it on your system. I suppose something in wx's font selection changed. If you want to do experiments check the ListCtrlLogger::UpdateSettings and TextCtrlLogger::UpdateSettings.

What happens if you build cb with latest wx-master?

Investigating the source code would demand more time and expertise than I have.  It's not that big a deal, just a bit annoying that it picks an ugly font and there's seemingly no way to change it.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: LETARTARE on June 10, 2019, 01:05:15 pm
Quote
IMPORTANT : THIS IS THE FIRT BUILD THAT USES WX 311 with 2D SUPPORT.
Will this version and the following be compilable with 'wx2.8.12' ?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 10, 2019, 07:58:59 pm
LETARTARE: What do you mean by compatible? C::B still builds with wx2.8 (a minor build fix is in the works for the windows build). Generally everybody should consider moving to wx3.x releases. At least give the new version a spin to find out if anything useful for you is still working.

Dropping wx2.8 is inevitable!
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 11, 2019, 06:18:42 pm
I'm seeing the failed assertion messages at launch of this nightly that I reported with the March 9 nightly:
http://forums.codeblocks.org/index.php/topic,23158.msg157753.html#msg157753

Is there anything useful a person with no significant C++ knowledge like me could do to help troubleshoot this?  I'll largely be stuck on 17.12 indefinitely otherwise.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 11, 2019, 08:40:11 pm
We need at least backtrace, but this requires building from source.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 12, 2019, 05:49:29 am
There's no other way I could get a build with debugging symbols included or something like that?
Title: Re: The 08 June 2019 build (11712) is out.
Post by: oBFusCATed on June 12, 2019, 07:19:04 pm
Unfortunately, yes you have to build from source.
Title: Re: The 08 June 2019 build (11712) is out.
Post by: raynebc on June 14, 2019, 06:39:54 am
I found that if I changed the OS back to US-English locale and rebooted, this hotfix seems to use the same font in the build log that 17.12 uses.  It's a really niche issue, but hopefully that narrows it down a little.