News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

The 28 March 2015 build (10158) is out.

Started by killerbot, March 28, 2015, 10:57:08 PM

Previous topic - Next topic

killerbot

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 for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc492-TDM.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_gcc492-TDM.7z

The 28 March 2015 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2015/CB_20150328_rev10158_win32.7z
  - Linux :
   none

The current SDK version is : 1.25.0

Resolved Fixed:


  • CC: Fix infinite loop when traversing headers and there are loops caused by symlinks (ticket #14)
  • CC: fix infinite loop when recursive macro expansion reaches max account
  • compiler: add support for gcc for ADI blackfin
  • Wizard: Fix the Arm wizard to show a proper list of compilers
  • Addr2Line: fixed that path to "addr2line" command is changed with replace operation (in case both, MinGW and the devel folder share one root)
  • added batch build for 64 bit (was missing in SVN), Windows only.
  • CC: work around a failure when handling stringize operator
  • CC: fix handling of struct pointer typedef. (patch from SF user jat1)
  • Thread Search Plugin: fix thread safety issue in ThreadSearchEvent class

Regressions/Confirmed/Annoying/Common bugs:




Jenna

Debian-stable packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc20, fc21, fc22 and rawhide), RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) and RedHat/CentOS 7 packages (only 64-bit at the moment) can be found in my rpm-repo.
I recently switched to copr to build and host my Fedora and CentOS packages.
Instructions how to use it can be found on my server (easier) or on copr (a little more handwork needed).

The revision is 10157, but there are no functional changes between 10157 and 10158.

MortenMacFly

Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

gd_on

Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

stahta01

C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

ollydbg

@Morten: Do you think we need to replace the old binary "src/exchndl.dll" file with the new updated ones in /setup/ folder?
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.

MortenMacFly

Quote from: ollydbg on March 31, 2015, 12:55:30 AM
@Morten: Do you think we need to replace the old binary "src/exchndl.dll" file with the new updated ones in /setup/ folder?
Yes, I'll do it.

Quote from: stahta01 on March 30, 2015, 08:50:33 PM
You appear to be correct I do NOT see the setup version to download under.
Quote from: gd_on on March 30, 2015, 07:39:18 PM
your links does not seem to work. Files are still not arrived on sourceforge ?
Well they have been there but gone??? Weird thing. I've re-uploaded them through SFTP now. Maybe their on-line file manager tool is broken.

So: Feel free to try again, please...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

Melchior

Quote from: MortenMacFly on March 31, 2015, 07:55:33 AM
Quote from: ollydbg on March 31, 2015, 12:55:30 AM
@Morten: Do you think we need to replace the old binary "src/exchndl.dll" file with the new updated ones in /setup/ folder?
Yes, I'll do it.

ohh I love updates ^_^ what setup folder are you talking about..  because I don't see a setup folder in my local copy of C:B svn repo... O_o


ps:
any chance you guys could take a look at that bug report I made a while back on
https://sourceforge.net/p/codeblocks/tickets/133/
(PC Specs)
CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
Motherboard: Asus SABERTOOTH 990FX R2.0
GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
OS: Windows 7 Ultimate 64-bit SP1 (x64)

shurick

Packages for openSUSE (binaries and sources) for 32-bit and 64-bit.
Packages for openSUSE http://codeblocks.esy.es  (binaries and sources) for 32-bit and 64-bit.

MortenMacFly

Checkout Setup instead of Trunk. Check with a Repository Browser, for example the one from sourceforge.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

ToApolytoXaos

Guys, I'm using svn10173 on debian testing 64-bit and have noticed a rather peculiar behavior of auto-completion.

I removed everything from a main.cpp and typed main; the auto-completion popped up the rest of the code and I pressed tab to complete it. Not only it didn't, it placed tab space in its place.

Also, if you type main() { and press enter, instead of completing the bracket, it takes it to 2 spaces indented from left to right...

Any feedback?

cheers.

ollydbg

Quote from: ToApolytoXaos on April 04, 2015, 10:48:44 PM
I removed everything from a main.cpp and typed main; the auto-completion popped up the rest of the code and I pressed tab to complete it.
I did the same steps, and I have "main()" entered by CC.

QuoteNot only it didn't, it placed tab space in its place.
I don't know this sentence.

QuoteAlso, if you type main() { and press enter, instead of completing the bracket, it takes it to 2 spaces indented from left to right...
I don't have this issue, I have the following result:

main(){
}


So, I think I need to know the detailed steps to reproduce this error. Thanks.
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.

ToApolytoXaos

Create an empty project, add a main.cpp file in it, try a simple piece of code, compile it, save the project, and then close it.

Reopen it, press Ctrl-A to highlight all source code, start typing main and wait for 5 seconds; now press the tab to accept the auto-completion suggestion and see that adds space instead of parentheses.

ollydbg

Quote from: ToApolytoXaos on April 05, 2015, 11:43:32 AM
Create an empty project, add a main.cpp file in it, try a simple piece of code, compile it, save the project, and then close it.

Reopen it, press Ctrl-A to highlight all source code, start typing main and wait for 5 seconds; now press the tab to accept the auto-completion suggestion and see that adds space instead of parentheses.
I just did what you described, and I still get the "main()" entered when I hit the TAB key.
I would like ask other guys to conform this issue.
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.

scarphin

Quote from: ToApolytoXaos on April 05, 2015, 11:43:32 AM
Create an empty project, add a main.cpp file in it, try a simple piece of code, compile it, save the project, and then close it.

Reopen it, press Ctrl-A to highlight all source code, start typing main and wait for 5 seconds; now press the tab to accept the auto-completion suggestion and see that adds space instead of parentheses.
Works correctly here.