Author Topic: The 28 October 2017 build (11219) is out.  (Read 3290 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5040
The 28 October 2017 build (11219) is out.
« on: October 29, 2017, 07:32:53 am »

IMPORTANT : THIS IS THE FIRST BUILD THAT USES WX 303 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/wxmsw30u_gcc_cb_wx303_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 28 October 2017 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2017/CB_20171028_rev11219_win64.7z
  - Linux :
   none

The current SDK version is : 1.32.0

Resolved Fixed:

  • debugger: Mark the GDB attach to process command to be a continue command
  • wx3: Fix assert when loading files and the global enconding setting is set to default (ticket #305)

Regressions/Confirmed/Annoying/Common bugs:


    « Last Edit: October 29, 2017, 03:51:01 pm by killerbot »

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5040
    Re: The 28 October 2017 build (11219) is out.
    « Reply #1 on: October 29, 2017, 07:35:00 am »
    we will first see how well a wx303 64 bit application works, once that is stable enough we will upgrade to wx310.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 4982
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 28 October 2017 build (11219) is out.
    « Reply #2 on: October 29, 2017, 08:54:36 am »
    Hi, thanks for your work.

    The first thing I see when start the C::B, I get a warning dialog, see below:
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 4982
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 28 October 2017 build (11219) is out.
    « Reply #3 on: October 29, 2017, 09:00:40 am »
    OK, I see a second issue: the threadsearch plugin's file mask field can't be saved when I close the setting dialog(or close C::B), which I meet days ago under wxWidgets 3.1 based 32 bit C::B, see my original bug report here: Re: Threadsearch plugin cause crash when initilized (wx3.1,C::B svn head)
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 57
    • Sage of Life, Reason, and Time
    Re: The 28 October 2017 build (11219) is out.
    « Reply #4 on: October 29, 2017, 09:06:20 am »
    Quote
    Mark the GDB attach to process command to be a continue command

    NICE I had issues with importing and building....
    - LibPNG  http://www.libpng.org/pub/png/libpng.html

    the project file once imported it does NOT work correctly, the VC++ project file..
    it uses the copy cmd to copy and rename... as follows..
    Code: [Select]
    <Tool Name="VCPreBuildEventTool" CommandLine="copy ..\..\scripts\pnglibconf.h.prebuilt ..\..\pnglibconf.h"/>

    copy ..\..\scripts\pnglibconf.h.prebuilt ..\..\pnglibconf.h

    the problem is in CodeBlocks it pauses to ask whether it is a FILE or DIRECTORY lol :P ;)
    and the C::B console sub-window HAS NO CMD input box.. so its a stall..

    SO my work around as follows.. 
    even when switching to xcopy

    ops lol that was the old method..  lol ;) 
    when I last compiled and updated libPNG.. that was v1.6.30 now v1.6.32..
    I have it just haven't felt like compiling it yet...

    anyway back to the point here is the new method that seems to work fully as a "work around"
    Code: [Select]
    <ExtraCommands>
         <Add before="cmd /C  type ..\..\scripts\pnglibconf.h.prebuilt &gt; ..\..\pnglibconf.h" />
    </ExtraCommands>


    :: THIS ONE WORKS INSIDE CodeBlocks
    cmd /C  type ..\..\scripts\pnglibconf.h.prebuilt > ..\..\pnglibconf.h

    is there anything you devs can do to mitigate this?
    I thought of this problem I have when importing LibPNG VC++ project file because of your changelog comment
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 16GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 750Ti SC 2GB  --  GFX Drivers: Nvidia v388.13
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 57
    • Sage of Life, Reason, and Time
    Re: The 28 October 2017 build (11219) is out.
    « Reply #5 on: October 29, 2017, 09:09:02 am »
    COOL thx.. Huwayy!! 64bit C::B AT LAST!!!!!! lol ;)
    I will download and give it a run in my test directory!

    EDIT:
    the  the mingw10m.dll linked above is 32bit.. and for windows to load the NEW and SHINY 64bit C::B
    pretty sure ALL must be 64bit.. ie. exe, dlls, and plugin dlls
    testing now..

    ALL binary files except [ mingw10m.dll ] are 64bit!
    « Last Edit: October 29, 2017, 09:34:00 am by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 16GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 750Ti SC 2GB  --  GFX Drivers: Nvidia v388.13
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10356
    Re: The 28 October 2017 build (11219) is out.
    « Reply #6 on: October 29, 2017, 09:18:19 am »
    the problem is in CodeBlocks it pauses to ask whether it is a FILE or DIRECTORY lol :P ;)
    and the C::B console sub-window HAS NO CMD input box.. so its a stall..
    No, it is not a cb problem. When you use some command you must make sure that it will never ask for input. Check the copy command's help to see if there is some flag which makes it quiet or forces execution.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline Xaviou

    • Regular
    • ***
    • Posts: 254
      • X@v's wxStuff
    Re: The 28 October 2017 build (11219) is out.
    « Reply #7 on: October 29, 2017, 09:25:23 am »
    Hi.

    The MinGW dll's link points to the same file as the one for the "old" 32 bits version.

    Is it a normal thing ?

    Regards
    Xav'
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : https://wxstuff.xaviou.fr/

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 57
    • Sage of Life, Reason, and Time
    Re: The 28 October 2017 build (11219) is out.
    « Reply #8 on: October 29, 2017, 09:40:06 am »
    the problem is in CodeBlocks it pauses to ask whether it is a FILE or DIRECTORY lol :P ;)
    and the C::B console sub-window HAS NO CMD input box.. so its a stall..
    No, it is not a cb problem. When you use some command you must make sure that it will never ask for input. Check the copy command's help to see if there is some flag which makes it quiet or forces execution.

    hmm.. meh..
    so no chance an addition check box style option could be added to the cmd entry screen?


    the copy and xcopy command can do
    Code: [Select]
    /Y = Suppresses prompting to confirm you want to overwrite an  existing destination file.
    does not work on the is it a DIR or FILE

    there is also
    Code: [Select]
    /I = If destination does not exist and copying more than one file, assumes that destination must be a directory.
    but does not apply maybe.. not sure.. that is I may have tried it when I was debugging my "problem"..

    « Last Edit: October 29, 2017, 09:41:52 am by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 16GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 750Ti SC 2GB  --  GFX Drivers: Nvidia v388.13
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5040
    Re: The 28 October 2017 build (11219) is out.
    « Reply #9 on: October 29, 2017, 10:15:33 am »
    for some reason I don't seem to find (mingw10.dll)it in my TDM-GCC-64 install location, WTF.

    Anyone else do find it in this TDM-GCC-64 install location ?

    EDIT : I have a feeling that this dll is no longer needed, please try without.
    Maybe it is only needed for 32 bit (will check my 32 bit installation later today, or maybe since TDM 5.1 no longer needed, though I think I have found it there in the 32 installation location ...)

    So please try without the mingwm10.dll.

    EDIT 2 : this dll is indeed present in 32bit setup, and apparently not in 64 bit.
    « Last Edit: October 29, 2017, 10:41:03 am by killerbot »

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 4982
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 28 October 2017 build (11219) is out.
    « Reply #10 on: October 29, 2017, 10:22:10 am »
    Question:
    What does the mingwm10.dll use for? I mean I just download this dll, and extracted it, and I don't see any issue when I start this 64bit C::B.
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7217
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 28 October 2017 build (11219) is out.
    « Reply #11 on: October 29, 2017, 01:03:42 pm »
    Builds for Fedora (25, 26, 27, Rawhide), CentOS 7 and Debian (stable and testing) can be found in my copr or on my server.
    Links can be found in my signature.

    Offline Kilmatead

    • Single posting newcomer
    • *
    • Posts: 3
    Re: The 28 October 2017 build (11219) is out.
    « Reply #12 on: October 29, 2017, 01:08:36 pm »
    Am I the only one seeing rather serious redraw issues in the editor?  Just holding down the <Up> or <Down> keys to vertically scroll quickly through text seems to leave (I don't know how best to describe it) "residual caret positions", complete with highlighted backgrounds (from the highlight-line-under-caret setting).



    Also, if scrolling occurs (from the cursor movement, not from mouse), many lines will either be duplicated or disappear entirely - though this is only a visual distortion, as all aberrant effects disappear if the screen is refreshed for any reason (re-showing hidden panels, changing font size, etc).

    I can't seem to find any settings which cause it - I erased all CB settings (from appdata), and it occurs from a "stock" setup as well.

    Win7 x64, CB 11219

    (This does't happen for any of the older x86 nightlies, just this new x64 one.)

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10356
    Re: The 28 October 2017 build (11219) is out.
    « Reply #13 on: October 29, 2017, 01:33:50 pm »
    hmm.. meh..
    so no chance an addition check box style option could be added to the cmd entry screen?
    What will be the purpose of this checkbox?
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5040
    Re: The 28 October 2017 build (11219) is out.
    « Reply #14 on: October 29, 2017, 03:52:52 pm »
    Hi, thanks for your work.

    The first thing I see when start the C::B, I get a warning dialog, see below:

    ensure that nothing is left form the old 32 bit version (nor can be found in PATH). Do you still suffer from this problem ?