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.next.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_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:
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'
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.next.codeblocks.org/index.php/topic,23212.msg158127.html#msg158127 (http://forums.next.codeblocks.org/index.php/topic,23212.msg158127.html#msg158127)
Regards.
LETARTARE: Fixed...
Where can found the default 64 binary to use this 64-bit Nightly build?
Quote from: lp08 on April 29, 2019, 10:00:48 AM
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'
when preparing new nightly , and running update31_64.bat
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.
http://forums.next.codeblocks.org/index.php/topic,23250.msg158348.html#msg158348
is this normal on current trunk state ?
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
Probably. FortranProject is an external plugin and it should be updated by darmar to include the new icons.
Quote from: killerbot on May 11, 2019, 09:48:58 AM
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.
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...
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.
Quote from: oBFusCATed on May 15, 2019, 10:38:23 AM
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.
Quote from: Miguel Gimenez 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.
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.
Able to build Win10 64-bit versions of CB through SVN 11700. Builds of SVN 11701,11702, 11703 and 11707 all fail with the same error.
Build Log:
-------------- Build: tinyXML in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: AutoRevision in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: ConsoleRunner in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: Squirrel in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: Squirrel std lib in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: SqPlus in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
Target is up to date.
-------------- Build: scintilla in Code::Blocks wx3.1.x (64 bit) (compiler: Mingw gcc 8.1.0 x64)---------------
x86_64-w64-mingw32-g++.exe -Wall -g -pipe -mthreads -m64 -fmessage-length=0 -fexceptions -std=gnu++11 -DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DcbDEBUG -DNOPCH -DwxUSE_UNICODE -D_WIN64 -D__WX__ -DWINVER=0x0501 -DLINK_LEXERS -DSCI_LEXER -DWXMAKINGDLL_SCI -IC:\wxWidgets-3.1.2\lib\gcc_dll64\mswu -IC:\wxWidgets-3.1.2\include -Isdk\wxscintilla\include -Iinclude\tinyxml -Isdk\wxscintilla\src\scintilla\include -Isdk\wxscintilla\src\scintilla\src -Isdk\wxscintilla\src\scintilla\lexlib -c C:\Projects\Codeblocks\src\sdk\wxscintilla\src\PlatWX.cpp -o .objs31_64\sdk\wxscintilla\src\PlatWX.o
C:\Projects\Codeblocks\src\sdk\wxscintilla\src\PlatWX.cpp:59:6: error: #error "You need to have Direct2D capable wxWidget build to build Code::Blocks. We want to support fonts with ligatures!!!"
#error "You need to have Direct2D capable wxWidget build to build Code::Blocks. We want to support fonts with ligatures!!!"
^~~~~
Process terminated with status 1 (0 minute(s), 20 second(s))
1 error(s), 0 warning(s) (0 minute(s), 20 second(s))
CPP Source:
WXplat.cpp
========================================
#if wxCHECK_VERSION(3, 1, 0) && defined(__WXMSW__) && !defined(HAVE_DIRECTWRITE_TECHNOLOGY)
#error "You need to have Direct2D capable wxWidget build to build Code::Blocks. We want to support fonts with ligatures!!!"
#endif // wxCHECK_VERSION(3, 1, 0) && defined(__WXMSW__) && !defined(HAVE_DIRECTWRITE_TECHNOLOGY)
========================================
Any ideas as to why this is happening now? wxWidgets version hasn't changed since 12/10/2018.
Regards,
Frank
@Frank_CB: See here: http://forums.next.codeblocks.org/index.php/topic,23291.0.html
@oBFusCATed: Thank you! I'll update setup.h and rebuild all of my local wxWidgets libaries!