Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on October 06, 2019, 10:38:55 am

Title: The 06 October 2019 build (11872) is out.
Post by: killerbot on October 06, 2019, 10:38:55 am

IMPORTANT : THIS BUILD 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 06 October 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20191006_rev11872_win64.7z
  - Linux :
   none

The current SDK version is : 1.45.0

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 06 October 2019 build (11872) is out.
Post by: Xaviou on October 06, 2019, 07:10:41 pm
Hi

OS X version of this rev can be downloaded from my Google Drive (https://drive.google.com/open?id=0B2rFQ8rNHzEeN0xtU3R6emdhUWs).

Debian Stretch (32 and 64 bits) can be installed from my repo (https://wxstuff.xaviou.fr/article/debian-repository.html).

Regards
Xav'
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Khram on October 07, 2019, 04:11:30 pm
Spellcheck not work...
Title: Re: The 06 October 2019 build (11872) is out.
Post by: BlueHazzard on October 07, 2019, 05:07:36 pm
Spellcheck not work...
We know and i will fix it
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 07, 2019, 08:04:26 pm
The series of failed assertions still occur when launching this nightly during an RDP session:
http://forums.codeblocks.org/index.php/topic,23158.msg157753.html#msg157753

If there is any logging that can be added to diagnose this, or otherwise any other troubleshooting that can be suggested that doesn't involve me building C::B from source I'm willing to try.  Until then I'm still stuck using the 17.12 release for stability's sake.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 07, 2019, 08:11:04 pm
I doubt any logging would help. Someone should try to reproduce this somehow using a version which is debuggable. :( Then breaking in the debugger would reveal the problem and it would probably be an easy fix.

What are the settings of your rdp? Is it possible that the bit depth of the display is different? 16bits or lower? Can you build wxwidget sample and try the bitmap sample if it works correctly over rdp?

p.s. C::B is almost self contained. You need to build wxWidgets and C::B no other libraries. ;) And you must have zip in PATH.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 08, 2019, 07:42:49 am
I can try building a wxwidget sample program if it's relatively simple.  Is it one of these?
https://github.com/wxWidgets/wxWidgets/tree/master/samples/
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 08, 2019, 08:49:24 am
Yes, probably this one: https://github.com/wxWidgets/wxWidgets/tree/master/samples/image
Title: Re: The 06 October 2019 build (11872) is out.
Post by: AndyJ on October 08, 2019, 02:54:17 pm
With this nightly, predefined breakpoints no longer seem to trigger.

By prefdefined I mean ones that I previous set in the Project/targets options->Debugger->Additional GDB Commands dialog as 'break FuncName'. They are still shown but now seem to have no effect.

Going back to the previous nightly fixes this issue.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: BlueHazzard on October 08, 2019, 04:52:46 pm
Please enable full debugger logging in  Settings->Debugger->Common

then make all your settings and start the debugger
Please provide the content of the "Debugger" tab.
It would be good if one log is from the working codeblocks and one from the non working...
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Frank_CB on October 08, 2019, 08:04:51 pm
Hello,

Building a WIN10 64-bit version of SVN11876 encountered a 'zip' failure.

Building messages log follows:
Code: [Select]
||=== Build: tinyXML in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: AutoRevision in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: ConsoleRunner in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: Squirrel in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqapi.cpp||In function 'SQRESULT sq_setdelegate(HSQUIRRELVM, SQInteger)':|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqapi.cpp|784|warning: this 'if' clause does not guard... [-Wmisleading-indentation]|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqapi.cpp|784|note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'|
include\scripting\squirrel\squtils.h||In instantiation of 'void sqvector<T>::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger = long long unsigned int]':|
include\scripting\squirrel\sqarray.h|77|required from here|
include\scripting\squirrel\squtils.h|88|warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]|
include\scripting\squirrel\sqobject.h|130|note: 'struct SQObjectPtr' declared here|
include\scripting\squirrel\squtils.h||In instantiation of 'void sqvector<T>::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger = long long unsigned int]':|
include\scripting\squirrel\sqarray.h|77|required from here|
include\scripting\squirrel\squtils.h|88|warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]|
include\scripting\squirrel\sqobject.h|130|note: 'struct SQObjectPtr' declared here|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqdebug.cpp||In member function 'SQString* SQVM::PrintObjVal(const SQObject&)':|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqdebug.cpp|79|warning: format '%d' expects argument of type 'int', but argument 3 has type 'SQInteger' {aka 'long long int'} [-Wformat=]|
include\scripting\include\squirrel.h|151|note: in definition of macro '_SC'|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqfuncstate.cpp||In function 'void DumpLiteral(SQObjectPtr&)':|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqfuncstate.cpp|85|warning: format '%d' expects argument of type 'int', but argument 2 has type 'SQInteger' {aka 'long long int'} [-Wformat=]|
include\scripting\include\squirrel.h|151|note: in definition of macro '_SC'|
include\scripting\squirrel\squtils.h||In instantiation of 'void sqvector<T>::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger = long long unsigned int]':|
include\scripting\squirrel\sqarray.h|77|required from here|
include\scripting\squirrel\squtils.h|88|warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]|
include\scripting\squirrel\sqobject.h|130|note: 'struct SQObjectPtr' declared here|
include\scripting\squirrel\squtils.h||In instantiation of 'void sqvector<T>::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger = long long unsigned int]':|
include\scripting\squirrel\sqarray.h|77|required from here|
include\scripting\squirrel\squtils.h|88|warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]|
include\scripting\squirrel\sqobject.h|130|note: 'struct SQObjectPtr' declared here|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqvm.cpp||In member function 'void SQVM::ToString(const SQObjectPtr&, SQObjectPtr&)':|
C:\Projects\CB11876\src\sdk\scripting\squirrel\sqvm.cpp|254|warning: format '%d' expects argument of type 'int', but argument 3 has type 'SQInteger' {aka 'long long int'} [-Wformat=]|
include\scripting\include\squirrel.h|151|note: in definition of macro '_SC'|
include\scripting\squirrel\squtils.h||In instantiation of 'void sqvector<T>::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger = long long unsigned int]':|
include\scripting\squirrel\sqarray.h|77|required from here|
include\scripting\squirrel\squtils.h|88|warning: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]|
include\scripting\squirrel\sqobject.h|130|note: 'struct SQObjectPtr' declared here|
||=== Build: Squirrel std lib in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: SqPlus in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: scintilla in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||=== Build: sdk in Code::Blocks wx3.1.x (64 bit) (compiler: gnu x64) ===|
||Execution of 'zip -jq9 devel31_64\share\CodeBlocks\manager_resources.zip sdk\resources\*.xrc' in 'C:\Projects\CB11876\src' failed.|

Any idea why 'zip' failed?

Regards
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 08, 2019, 08:08:45 pm
@Frank_CB: What project/workspace are you building? Do you have zip in path? Which is the last working revision?
Title: Re: The 06 October 2019 build (11872) is out.
Post by: BlueHazzard on October 08, 2019, 08:14:41 pm
Quote
Any idea why 'zip' failed?
You need a zip.exe in your path. zip.exe is an application to create zip files.
https://superuser.com/questions/901954/where-can-i-find-a-zip-exe-that-works-in-windows-7
Title: Re: The 06 October 2019 build (11872) is out. (c::B will crash)
Post by: nanyu on October 08, 2019, 08:23:24 pm
1. close all projects
2. main menu : Settings -> Environment...
3. click "OK" button (or "cancle " button) to close the dialog...
4. c::b will crash.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 08, 2019, 08:35:09 pm
Yes, probably this one: https://github.com/wxWidgets/wxWidgets/tree/master/samples/image

I built wxwidgets 3.1.2 from source, built the image sample program, added the ".\wxwidgets\lib\gcc_dll" folder to my PATH environment variable and then the image program was able to run.  This is what I got when I launched it from within an RDP session:
https://i.imgur.com/Y1bd8zp.jpg

I didn't get any errors from the sample program.  My settings in the RDP client are:  Full screen, 16 bit color, auto detect connect quality, persistent bitmap caching.  I doubt these matter compared to changes to C::B or WxWidgets though, because the same conditions (RDP settings, bandwidth, client computer, server computer) can still launch the older version of C::B without issue.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Frank_CB on October 08, 2019, 08:48:03 pm
@oBfusCATed, @BlueHazzard

Thanks for your responses. I apparently lost the reference to 'zip' on my system. I'll fix it!

Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 08, 2019, 09:14:36 pm
@nanyu: Already fixed in trunk; A workaround is to have an open project.

@raynebc: My guess is that 16 bit colour is causing it. Is there any wx3.x build of C::B which works correctly? BTW now you're one step closer to building a debug version of CB and placing a breakpoint :)
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 08, 2019, 11:54:52 pm
As per the previous troubleshooting (http://forums.codeblocks.org/index.php/topic,23158.msg157800.html#msg157800), it was determined wx3.1 was what introduced the failed assertions in my scenario.  I tried connecting with the RDP client set to 32 bit color mode and this C::B nightly launched without error.  I connected with 24 bit and 15 bit color modes and launching the nightly resulted in the failed assertion messages for each.  So that does seem to be a trigger for this problem, although unless I'm misremembering, 16 bit color is the default setting for Windows' RDP for quite a while (probably at least Windows XP).

I can try to build the source code, but I don't want to install an SVN client (since I was mostly coerced to switching to Git after Google Code shut down and I transferred over to Github).  Getting the source code snapshot is taking ages though.  Are there any other unlisted build requirements other than what's listed on the Wiki article (wiki.codeblocks.org/index.php/Installing_Code::Blocks_from_source_on_Windows)?

Edit:  The source downloaded.  Do I just continue from here by opening the C::B project and trying to build it from within the IDE?

Edit 2:  I set it up as per the article as far as I can tell, but the build failed at:
#error "You need to have Direct2D capable wxWidget build to build Code::Blocks. We want to support fonts with ligatures!!!"
This compiler directive is in src\sdk\wxscintilla\src\PlatWX.cpp

Edit 3:  Trying the steps listed here (taking sodev's correction into account that include\wx\msw\setup.h is the correct file to edit):
http://forums.codeblocks.org/index.php/topic,23291.msg158631.html#msg158631

Edit 4:  Even after all that and rebuilding both wxWidgets and C::B, it failed on the same line.   I don't want to just hackishly bypass this check just to get it to compile if that will break something.  I'll wait for further guidance.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 09, 2019, 10:12:12 am
Just bypass the check, it is not important for what you're testing.

To fix it properly you have to find the setup.h file which is incorrect and do a rebuild.
There are multiple such files and they are copied by the wxwidgets build.

p.s. you need to have zip in path.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: MaxGaspa on October 09, 2019, 11:59:41 am
Dear CB team,

I recently updated my CB nightly and I had an issue (possible bug).

Windows 7 64 bit latest SP MINGW64 GCC 8.3.0

Just after opening CB (without loading any source file or projects) I was adding an item in the help menu.....

Setting->Environment->Help Files....then any actions (click OK or cancel or try to add an item) is causing a crash (I've got an RPT, attached to this message)

Repeating the same actions with a loaded projects the crash disappears....

Hope this helps.

Max
Title: Re: The 06 October 2019 build (11872) is out.
Post by: sodev on October 09, 2019, 12:11:02 pm
Edit 4:  Even after all that and rebuilding both wxWidgets and C::B, it failed on the same line.   I don't want to just hackishly bypass this check just to get it to compile if that will break something.  I'll wait for further guidance.

After changing such elemental things its a good idea to clean up the wxWidgets source tree and remove everything from previous builds. These are the library folders that start with gcc in the lib folder and the object files folders that start with gcc in the build\msw folder.

Same applies to CodeBlocks, there it is the .obj* and devel* folders under src i think.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: BlueHazzard on October 09, 2019, 02:04:39 pm
Quote
Just after opening CB (without loading any source file or projects) I was adding an item in the help menu.....

Setting->Environment->Help Files....then any actions (click OK or cancel or try to add an item) is causing a crash (I've got an RPT, attached to this message)

Repeating the same actions with a loaded projects the crash disappears....
Thank you for the report. This is already fixed in trunk and will be fixed in the next nightly build
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 09, 2019, 06:48:52 pm
I had edited the setup.h file sodev indicated in the linked thread, and did a full clean and full rebuild of wxwidgets.  Is the makefile's "clean" target broken/insufficient for this purpose?  If I can just comment out that #error check I may just go ahead and do that.  zip.exe is already in my path.

Edit:  Commenting out that check was not enough.  The build failed with a variety of errors:
Code: [Select]
sdk\wxpropgrid\include\wx\propgrid\propdev.h|18|error: aggregate 'WXDLLIMPEXP_PG_FWD wxArrayEditorDialog' has incomplete type and cannot be defined|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|32|error: variable 'WXDLLIMPEXP_PG wxPGGlobalVarsClass' has initializer but incomplete type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected primary-expression before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected '}' before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected ',' or ';' before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|37|error: expected constructor, destructor, or type conversion before ';' token|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|61|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|62|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|63|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|64|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|65|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|66|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|67|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|68|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|70|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|100|error: non-member function 'int HasExtraStyle(int)' cannot have cv-qualifier|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|105|error: expected declaration before '}' token|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|18|error: aggregate 'WXDLLIMPEXP_PG_FWD wxArrayEditorDialog' has incomplete type and cannot be defined|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|32|error: variable 'WXDLLIMPEXP_PG wxPGGlobalVarsClass' has initializer but incomplete type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected primary-expression before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected '}' before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|34|error: expected ',' or ';' before 'public'|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|37|error: expected constructor, destructor, or type conversion before ';' token|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|61|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|62|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|63|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|64|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|65|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|66|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|67|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|68|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|70|error: 'wxPGVariantDataClassInfo' does not name a type|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|100|error: non-member function 'int HasExtraStyle(int)' cannot have cv-qualifier|
sdk\wxpropgrid\include\wx\propgrid\propdev.h|105|error: expected declaration before '}' token|
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 09, 2019, 08:05:59 pm
Are you using the correct project? Suffix wx31 for wxwidgets 3.1.x, wx30 for wxwidgets 3.0.x no suffix for wx2.8 and there are 64 bit variants of wx30 and wx31 also. :(
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 09, 2019, 08:16:30 pm
I hadn't noticed there were several C::B projects, I just opened the normal CodeBlocks.cbp project as directed by the wiki article (http://wiki.codeblocks.org/index.php/Installing_Code::Blocks_from_source_on_Windows).  Perhaps the article should be updated to reflect that the project file suited for the version of wxwidgets in question must be opened.  I picked the "CodeBlocks_wx31" project since I'm using normal MinGW (no 64 but support).  Unfortunately, cc1plus.exe keeps crashing at this point in the build:

Code: [Select]
-------------- Build: sdk in Code::Blocks wx3.1.x (compiler: GNU GCC Compiler)---------------

Running target pre-build steps
.objs31\autorevision +wx +int +t .. include/autorevision.h
mingw32-g++.exe -Wall -g -pipe -mthreads -fmessage-length=0 -fexceptions -Winvalid-pch -std=gnu++11 -DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DcbDEBUG -DCB_PRECOMP -DwxUSE_UNICODE -Woverloaded-virtual -DEXPORT_LIB -DEXPORT_EVENTS -DWXMAKINGDLL_SCI -Wall -g -iquote.objs31\include -I.objs31\include -I. -IC:\wxwidgets\include -IC:\wxwidgets\lib\gcc_dll\mswu -Isdk\wxscintilla\include -Iinclude\tinyxml -Iinclude -Iinclude\tinyxml -Iinclude\scripting\bindings -Iinclude\scripting\include -Iinclude\scripting\sqplus -Iinclude\mozilla_chardet -Iinclude\mozilla_chardet\mfbt -Iinclude\mozilla_chardet\nsprpub\pr\include -Iinclude\mozilla_chardet\xpcom -Iinclude\mozilla_chardet\xpcom\base -Iinclude\mozilla_chardet\xpcom\glue -c C:\cb_svn\src\sdk\configmanager-revision.cpp -o .objs31\sdk\configmanager-revision.o
mingw32-g++.exe -Wall -g -pipe -mthreads -fmessage-length=0 -fexceptions -Winvalid-pch -std=gnu++11 -DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DcbDEBUG -DCB_PRECOMP -DwxUSE_UNICODE -Woverloaded-virtual -DEXPORT_LIB -DEXPORT_EVENTS -DWXMAKINGDLL_SCI -Wall -g -iquote.objs31\include -I.objs31\include -I. -IC:\wxwidgets\include -IC:\wxwidgets\lib\gcc_dll\mswu -Isdk\wxscintilla\include -Iinclude\tinyxml -Iinclude -Iinclude\tinyxml -Iinclude\scripting\bindings -Iinclude\scripting\include -Iinclude\scripting\sqplus -Iinclude\mozilla_chardet -Iinclude\mozilla_chardet\mfbt -Iinclude\mozilla_chardet\nsprpub\pr\include -Iinclude\mozilla_chardet\xpcom -Iinclude\mozilla_chardet\xpcom\base -Iinclude\mozilla_chardet\xpcom\glue -c C:\cb_svn\src\sdk\annoyingdialog.cpp -o .objs31\sdk\annoyingdialog.o
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 11, 2019, 01:17:13 am
With this nightly, predefined breakpoints no longer seem to trigger.

By prefdefined I mean ones that I previous set in the Project/targets options->Debugger->Additional GDB Commands dialog as 'break FuncName'. They are still shown but now seem to have no effect.

Going back to the previous nightly fixes this issue.
Fix in trunk rev11876, thanks for reporting and sorry for breaking it.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 11, 2019, 01:18:16 am
@raynebc: Currently I'm using mingw-w64 to build codeblocks and I don't have problems with, but I'm building the 64bit version of wx3.1.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: raynebc on October 11, 2019, 01:51:40 am
I don't know if I want to change toolsets just to try to get C::B to build, I don't want to do anything that will break my MinGW installation.  If a debug build can add some logging or dialog messages to identify where the assertions are failing, I'll try it.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: AndyJ on October 11, 2019, 01:35:12 pm
With this nightly, predefined breakpoints no longer seem to trigger.

By prefdefined I mean ones that I previous set in the Project/targets options->Debugger->Additional GDB Commands dialog as 'break FuncName'. They are still shown but now seem to have no effect.

Going back to the previous nightly fixes this issue.
Fix in trunk rev11876, thanks for reporting and sorry for breaking it.

Thank you for addressing this so quickly. Looking at your change explains why my colleague wasn't  seeing this when remote debugging. I look forward to the next nightly!
Title: Re: The 06 October 2019 build (11872) is out.
Post by: MaxGaspa on October 11, 2019, 03:45:24 pm
Dear CB Team,

Another (very minor) issue I had, updating from an older (11781) nightly build, is the disappearing of the spell-checker flags from the main CB window. The string en_GB is now displayed instead of showing the UK flags.

Spell-checker works as usual but the flags is no longer present. Using the previous 11781 the flags  were displayed correctly.

Is a very minor issue and CB is perfectly usable but I'm wondering if it is a CB issue or a problem due to my configuration.

Windows 7 latest SP MinGW64 GCC 8.3.0 display resolution 1280 x 1024 (the recommended resolution for my monitor)

Any comment?
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 12, 2019, 12:43:31 am
@MaxGaspa: Are you installing the new night build in a clean folder or are you overriding an old folder? The flags should work correctly, at least they work on two of my systems.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: MaxGaspa on October 14, 2019, 08:28:29 am
@MaxGaspa: Are you installing the new night build in a clean folder or are you overriding an old folder? The flags should work correctly, at least they work on two of my systems.

I'm deleting everything in the installation directory (c:\Codeblocks) before unpacking the new nightly. Then I create the folder

C:\Codeblocks\share\CodeBlocks\SpellChecker

where I copy the SpellChecker files. The spellchecker works fine just the flags are not shown. I'm attaching a snapshot of my files copied in the spellchecker folder and a snapshot of the spellchecker configuration.

The previous used nightly (11781) was showing the flags correctly. It may be a local issue....and I can live with it :-) it's a real minor issue.


Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 14, 2019, 07:54:44 pm
Hm, there is a step you're not showing here.
The images for the spellchecker must be in sized folders.
They should look like 16x16, 20x20,... 64x64.
If they aren't something is wrong.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Miguel Gimenez on October 14, 2019, 08:15:44 pm
The nightly's share/CodeBlocks/SpellChecker folder has only an xml file
The same folder in my devel31 folder has nine nnxnn subfolders, 11 flags in png format and the xml
The same folder in my output31 folder has the 11 flags in png format and the xml

Seems like the update31.bat does not copy the folders from devel31 to output31, and the flags in png are a residue of previous revisions
Title: Re: The 06 October 2019 build (11872) is out.
Post by: MaxGaspa on October 14, 2019, 08:36:21 pm
Hm, there is a step you're not showing here.
The images for the spellchecker must be in sized folders.
They should look like 16x16, 20x20,... 64x64.
If they aren't something is wrong.

I created a folder "16x11". The subfolder is still empty but it works now!!! The flags are shown  as expected even if I didn't copy the flag files in the 16x11 subfolder...strange!

I never created such a folder and no nightly archive is creating it. The archive is containing the flags in the ....\share\CodeBlocks\SpellChecker with no sized sub-folder.

Anyway now it works! Thank you for your suggestion.

Max
Title: Re: The 06 October 2019 build (11872) is out.
Post by: sodev on October 14, 2019, 08:46:36 pm
Interesting, SpellChecker has its own update.bat like FortranProject, but in constrast to the latter, the former actually does also handle the copying of devel to output. However the plain xcopy does not process the image subdirectories hence they are missing. The question when this should be fixed is, who is responsible for copying the resources from devel to output? The plugin itself or the master update.bat?

About the nightly, i didn't check it, probably it wasn't created from a clean source tree and there are remaining files from previous versions that didn't use different size versions. The machine that builds the nightlies should be cleaned and do a fresh build :)
Title: Re: The 06 October 2019 build (11872) is out.
Post by: stahta01 on October 14, 2019, 09:32:14 pm
Interesting, SpellChecker has its own update.bat like FortranProject, but in constrast to the latter, the former actually does also handle the copying of devel to output. However the plain xcopy does not process the image subdirectories hence they are missing. The question when this should be fixed is, who is responsible for copying the resources from devel to output? The plugin itself or the master update.bat?

About the nightly, i didn't check it, probably it wasn't created from a clean source tree and there are remaining files from previous versions that didn't use different size versions. The machine that builds the nightlies should be cleaned and do a fresh build :)

My opinion is the master update batch file should copy from devel to output folder.
Note: This is not true for several plugins that do copy to output folder.

Tim S.
 
Title: Re: The 06 October 2019 build (11872) is out.
Post by: killerbot on October 15, 2019, 09:57:57 am
Interesting, SpellChecker has its own update.bat like FortranProject, but in constrast to the latter, the former actually does also handle the copying of devel to output. However the plain xcopy does not process the image subdirectories hence they are missing. The question when this should be fixed is, who is responsible for copying the resources from devel to output? The plugin itself or the master update.bat?

About the nightly, i didn't check it, probably it wasn't created from a clean source tree and there are remaining files from previous versions that didn't use different size versions. The machine that builds the nightlies should be cleaned and do a fresh build :)

will take care of that for the next one ;-)
Title: Re: The 06 October 2019 build (11872) is out.
Post by: gd_on on October 15, 2019, 07:25:36 pm
The problem with the flag  is a little bit different for me.
In Libre office or Thunderbird, the name of dictionaries are in my case fr.dic and fr.aff.
The name of the file flag used by SpellChecker is fr_FR.png.
Apparently the name of the dictionnary is used to build the name of the file flag (if I understand the code in StatusField.cpp, SpellCheckerStatusField::Update). So, it's not found.
But if I rename fr_FR.png in fr.png in C:\Program Files\CodeBlocks_wx313_64\share\CodeBlocks\SpellChecker\16x16 for me), the flag appears.

gd_on
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 19, 2019, 01:13:28 pm
@killerbot: This should be fixed in master.

@gd: This is separate issue, but I don't know what we could do about it. Post a ticket and we might consider it. Have you tried to rename your dictionary to match the flags (no idea if there is something special in the file which prevents renaming)?
Title: Re: The 06 October 2019 build (11872) is out.
Post by: gd_on on October 19, 2019, 06:16:32 pm
I have created a ticket (#883).
I can rename my Thunderbird dictionaries of course (or in LibreOffice), but it's not a good solution. It's to C::B to build the right name, not to other softs, I think.
As told previously, It's just a minor problem that I can solve temporarilly by renaming the png file (or better by creating a hardlink with LinkShellExtension in Windows).
gd_on
Title: Re: The 06 October 2019 build (11872) is out.
Post by: oBFusCATed on October 19, 2019, 08:14:21 pm
It's to C::B to build the right name, not to other softs, I think.
This is true if there is something like a standard for naming. If anybody is free to name its dictionaries files whatever he likes then how are we supposed to select the images?
Title: Re: The 06 October 2019 build (11872) is out.
Post by: sodev on October 19, 2019, 09:08:16 pm
Well, there is a standard for catalog names, e. g. https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html (https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html). The problem here is that his catalogs don't contain the country code, i think it is a common pattern to fallback to the pure language code in that case.
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Frank_CB on October 29, 2019, 09:53:52 pm
Hello,

At least Windows 10 (64-bit) versions of SVN 11887 and SVN 11889 fail to build successfully because of errors in update.bat, which is part of the post build command for the default section for Spellchecker. Update.bat asks for input from the user as displayed below:

Code: [Select]
0 File(s) copied
C:SpellChecker-off.png
C:SpellChecker.png
2 File(s) copied
Copy image files from rc to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker
From rc\16x16 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\16x16
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\16x16
From rc\20x20 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\20x20
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\20x20
From rc\24x24 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\24x24
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\24x24
From rc\28x28 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\28x28
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\28x28
From rc\32x32 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\32x32
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\32x32
From rc\40x40 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\40x40
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\40x40
From rc\48x48 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\48x48
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\48x48
From rc\56x56 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\56x56
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\56x56
From rc\64x64 to ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\64x64
Make dir ..\..\..\devel31_64\share\CodeBlocks\SpellChecker\64x64
Does ..\..\..\output31_64\share\CodeBlocks\SpellChecker specify a file name
or directory name on the target
(F = file, D = directory)?


Also there are three REM statements that don't make a lot of sense to me either (as to why they are even there?). It looks almost like somebody had been experimenting and forgot to clean up.

Removing the post build command allows me to build those versions of C::B

Regards!

Title: Re: The 06 October 2019 build (11872) is out.
Post by: Miguel Gimenez on October 29, 2019, 10:14:36 pm
Mea culpa, there is already a patch for this at the end of ticket 882
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Frank_CB on October 29, 2019, 10:23:36 pm
Where is ticket 882?
Title: Re: The 06 October 2019 build (11872) is out.
Post by: Frank_CB on October 29, 2019, 11:27:24 pm
@Miguel Gimenez
Downloaded patch from end of ticket 882.
Thanks!