Author Topic: The 20 April 2019 build (11628) is out.  (Read 2924 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5149
The 20 April 2019 build (11628) is out.
« on: April 20, 2019, 01:20:49 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.

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_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 20April 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20190420_rev11628_win64.7z
  - Linux :
   none

The current SDK version is : 1.37.0

Resolved Fixed:

  • missing icon images problem fixed
  • UI: Fix missing image after the move of 22x22 images to a separate folder (thanks drzacek for reporting)
  • UI: Fix layout issue in the environment settings dialog (thanks Miguel Gimenez)

Regressions/Confirmed/Annoying/Common bugs:



    Offline Xaviou

    • Regular
    • ***
    • Posts: 288
      • X@v's wxStuff
    Re: The 20 April 2019 build (11628) is out.
    « Reply #1 on: April 20, 2019, 05:04:31 pm »
    Hi

    OS X version of this rev can be downloaded from my Google Drive.

    Debian Stretch (32 and 64 bits) can be installed from my repo.

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

    Offline LETARTARE

    • Regular
    • ***
    • Posts: 366
    • L'ami de l'homme.The friend of man.
    Re: The 20 April 2019 build (11628) is out.
    « Reply #2 on: April 20, 2019, 06:19:23 pm »
    Thank you for this new version.

    Problem with : Vista Business Pack 2 32bits :  TDM-GCC 4.9.2, C::B  : svn11628, wxwidgets2.8,
    with 'void MainFrame::CreateIDE()' at line  758:75

    Quote

        U:\Donnees\Svn_Compile\Cb\Tdm492\cb-11628\src\src\main.cpp:758:75:
        error: cannot pass objects of non-trivially-copyable type 'class wxString' through '...'

    See  http://forums.codeblocks.org/index.php/topic,23212.msg158127.html#msg158127

    Regards.
    C::B  : svn11656, wxwidgets2.8, wx3.0.3 plugins : QtPregen-2.4.3-sdk138
    1-Vista Business Pack 2 32bits :  TDM-GCC- 4.9.2, TDM-GCC-5.1.0.3
    2-OpenSuse-42.3-Leap 64bits :  g++-4.8.5,
    => !! The messages are translated by GOOGLE !!

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11714
      • Travis build status
    Re: The 20 April 2019 build (11628) is out.
    « Reply #3 on: April 20, 2019, 09:00:45 pm »
    LETARTARE: Fixed...
    (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 lp08

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 20 April 2019 build (11628) is out.
    « Reply #4 on: April 29, 2019, 10:00:48 am »
    Where can found the default 64 binary to use this 64-bit Nightly build?

    Offline Xaviou

    • Regular
    • ***
    • Posts: 288
      • X@v's wxStuff
    Re: The 20 April 2019 build (11628) is out.
    « Reply #5 on: April 30, 2019, 06:15:38 pm »
    Where can found the default 64 binary to use this 64-bit Nightly build?
    If you are on Windows, all the needed links are in the first post.

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

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5149
    Re: The 20 April 2019 build (11628) is out.
    « Reply #6 on: May 01, 2019, 10:22:11 am »
    when preparing new nightly , and running update31_64.bat

    Code: [Select]
    zip I/O error: No such file or directory

    zip error: Could not create output file (devel31_64/share/CodeBlocks/resources.zip)
    zip I/O error: No such file or directory

    zip error: Could not create output file (devel31_64/share/CodeBlocks/manager_resources.zip)
    Packing plugins UI bitmaps
    zip I/O error: No such file or directory

    zip error: Could not create output file (devel31_64/share/CodeBlocks/compiler.zip)
    Copying default files


    did something get broken ?


    Note also the incorrect messages, it claims it can not create the SOURCE files, which nicely exist.
    And those file did end up in the output dir tree though.

    Running the script once more, continues to give the same errors.
    « Last Edit: May 01, 2019, 10:26:29 am by killerbot »

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11714
      • Travis build status
    (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: 5149
    Re: The 20 April 2019 build (11628) is out.
    « Reply #8 on: May 11, 2019, 09:48:58 am »
    is this normal on current trunk state ?

    Code: [Select]
    Copy image files from devel31_64\share\CodeBlocks\images\fortranproject to devel31_64\share\CodeBlocks\images\fortranproject
    From devel31_64\share\CodeBlocks\images\fortranproject\16x16 to output31_64\share\CodeBlocks\images\fortranproject\16x16Make dir output31_64\share\CodeBlocks\images\fortranproject\16x16
    From devel31_64\share\CodeBlocks\images\fortranproject\20x20 to output31_64\share\CodeBlocks\images\fortranproject\20x20Make dir output31_64\share\CodeBlocks\images\fortranproject\20x20
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\24x24 to output31_64\share\CodeBlocks\images\fortranproject\24x24Make dir output31_64\share\CodeBlocks\images\fortranproject\24x24
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\28x28 to output31_64\share\CodeBlocks\images\fortranproject\28x28Make dir output31_64\share\CodeBlocks\images\fortranproject\28x28
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\32x32 to output31_64\share\CodeBlocks\images\fortranproject\32x32Make dir output31_64\share\CodeBlocks\images\fortranproject\32x32
    From devel31_64\share\CodeBlocks\images\fortranproject\40x40 to output31_64\share\CodeBlocks\images\fortranproject\40x40Make dir output31_64\share\CodeBlocks\images\fortranproject\40x40
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\48x48 to output31_64\share\CodeBlocks\images\fortranproject\48x48Make dir output31_64\share\CodeBlocks\images\fortranproject\48x48
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\56x56 to output31_64\share\CodeBlocks\images\fortranproject\56x56Make dir output31_64\share\CodeBlocks\images\fortranproject\56x56
    File not found - *.png
    From devel31_64\share\CodeBlocks\images\fortranproject\64x64 to output31_64\share\CodeBlocks\images\fortranproject\64x64Make dir output31_64\share\CodeBlocks\images\fortranproject\64x64
    File not found - *.png

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11714
      • Travis build status
    Re: The 20 April 2019 build (11628) is out.
    « Reply #9 on: May 11, 2019, 03:36:44 pm »
    Probably. FortranProject is an external plugin and it should be updated by darmar to include the new icons.
    (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 darmar

    • Multiple posting newcomer
    • *
    • Posts: 57
    Re: The 20 April 2019 build (11628) is out.
    « Reply #10 on: May 14, 2019, 09:53:56 pm »
    is this normal on current trunk state ?

    Actually I think it is not normal state. Until recently update.bat was not responsible to copy any files from FortranProject plugin. FP plugin has its own update* files which are run as a post-build step during compilation in C::B. In such way I can adjust update* files to FP needs.

    I think, the lines 139-141 in update.bat file should be removed.

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11714
      • Travis build status
    Re: The 20 April 2019 build (11628) is out.
    « Reply #11 on: May 15, 2019, 10:38:23 am »
    It was there when I've started modifying the scripts. I could remove it, but then building night builds would become harder for killerbot. He'll have to remember to run some script...
    (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 Miguel Gimenez

    • Regular
    • ***
    • Posts: 251
    Re: The 20 April 2019 build (11628) is out.
    « Reply #12 on: May 15, 2019, 12:17:50 pm »
    IMHO the FP bats (and others) should only modify the devel folder, leaving output creation/update to the main update.bat.
    This way you can generate a clean output folder without rebuilding the whole workspace.

    Offline darmar

    • Multiple posting newcomer
    • *
    • Posts: 57
    Re: The 20 April 2019 build (11628) is out.
    « Reply #13 on: May 16, 2019, 01:39:36 pm »
    I could remove it, but then building night builds would become harder for killerbot. He'll have to remember to run some script...

    There is no need to run extra script. Required script for FP is run automatically by C::B in the post-build compilation step.

    IMHO the FP bats (and others) should only modify the devel folder, leaving output creation/update to the main update.bat.
    This way you can generate a clean output folder without rebuilding the whole workspace.

    You are right. FP breaks this rule. However, in FP used solution adds some more freedom for me as an "independent" developer. E.g. current problem reported by Killerbot is because update.bat tries to copy folders which are not present and are not used by FP. The use of separate update* files allows me to adjust update* files to specific FP needs.