News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

The 20 November 2016 build (10922) is out.

Started by killerbot, November 20, 2016, 05:45:37 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_gcc510-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_gcc510-TDM.7z

The 20 November 2016 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2016/CB_20161120_rev10922_win32.7z
  - Linux :
   none

The current SDK version is : 1.30.0

Resolved Fixed:




  • UI: Add multiple select in the "Copy selected to" dialogue (ticket #410, thanks bluehazzard)
  • UI: Disable the Copy to buttons in the Build options dialog if nothing in the list is selected, because these operations do nothing in this case
  • UI: Add multiple select in the "Copy to..." dialog in Search Directories (ticket #410)
  • UI: Fix incorrect usage of size_t (ticket #66)
  • Updated: Copyright year.
  • applied Feature/Patch #421: Add dialog for global variables to "Edit Path" dialog
  • debugger: Make if possible to debug 32bit program with CDB 64bit (ticket #429, thanks debugfanchin)
  • debugger: Fix parsing of backtrace produced by newer CDB's (ticket #430 thanks debugfanchin)

Regressions/Confirmed/Annoying/Common bugs:




Xaviou

My wxWidgets's stuff : [url="https://wxstuff.xaviou.fr/"]https://wxstuff.xaviou.fr/[/url]


Jenna

Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
These packages are build against wxWidgets 3.0 from Debian repos and mght not be as stable than the versions build against wx2.8, but there are no wx2.8 packages available (at least for stable) from official repos.
Please test and give feedback.

Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc23, fc24, fc25 and rawhide), RedHat/CentOS 7 packages (64-bit) can be found in my copr-repo.
Instructions how to use it can be found on my server  or on copr.

killerbot


ollydbg

Hi, killerbot, if possible, can you update a new wx dll file? see my suggestion here: Re: The 25 September 2016 build (10912) is out. 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.

BlueHazzard

Quoteapplied Feature/Patch #421: Add dialog for global variables to "Edit Path" dialog
There i still this (hard) issue open (from White-Tiger) :
https://sourceforge.net/p/codeblocks/tickets/421/#d915

i think the gui code for the path dialog went messed up when "applying" the modified patch

killerbot

Quote from: ollydbg on November 21, 2016, 03:48:32 PM
Hi, killerbot, if possible, can you update a new wx dll file? see my suggestion here: Re: The 25 September 2016 build (10912) is out. Thanks.

Yes, I will do that.

BlueHazzard

Quote from: hairuoai on November 22, 2016, 09:32:34 AM
I used Cb10912 to generate prime number <10000000,it took 34s in my VM win7 with gcc 6.2.0.And VC2015 took 37s.
Then i used CB10922 to do the same thing.gcc 6.2 took 51s,and vc2015 took 37s.why?
Reproducible? Your own build or a nightly?
I don't see any changes in the SVN log that can justify this...

hairuoai

Quote from: BlueHazzard on November 22, 2016, 10:03:07 AM
Quote from: hairuoai on November 22, 2016, 09:32:34 AM
I used Cb10912 to generate prime number <10000000,it took 34s in my VM win7 with gcc 6.2.0.And VC2015 took 37s.
Then i used CB10922 to do the same thing.gcc 6.2 took 51s,and vc2015 took 37s.why?
Reproducible? Your own build or a nightly?
I don't see any changes in the SVN log that can justify this...
maybe just fine,this time 10912 takes 36.067s,10922 takes 37.768.....i was wrong....sorry

frankofrank

Hi!

I build version with wx3.1.0 for Mac OS X 10.11

Code::Blocks svn build  rev 10922 Nov 22 2016, 16:58:58 - wx3.1.0 (Mac OS X, unicode) - 64 bit

http://goo.gl/AKkrfa

Regards
frankofrank

liaoya

Mcafee VirusScan Enterprise + AntiSpyware Enterprise 8.8 reports a virus in wxspeedbutton.dll on Windws 7 Professional. Would you take a look at it?

Xaviou

Quote from: frankofrank on November 23, 2016, 01:18:07 PM
Hi!

I build version with wx3.1.0 for Mac OS X 10.11

Code::Blocks svn build  rev 10922 Nov 22 2016, 16:58:58 - wx3.1.0 (Mac OS X, unicode) - 64 bit

http://goo.gl/AKkrfa

Regards
frankofrank
Works fine : Thank-you for the dmg file...

Regards
Xav'
My wxWidgets's stuff : [url="https://wxstuff.xaviou.fr/"]https://wxstuff.xaviou.fr/[/url]

hairuoai

Build information options  don't show the compiler version? eg,i use gcc 6.2,and it shows unknow...
so will the next nightly builds add few codes can detect the compiler version which is using ?
//MSVC++ 14.0 _MSC_VER == 1900 (Visual Studio 2015)
        //MSVC++ 12.0 _MSC_VER == 1800 (Visual Studio 2013)
        //MSVC++ 11.0 _MSC_VER == 1700 (Visual Studio 2012)
        //MSVC++ 10.0 _MSC_VER == 1600 (Visual Studio 2010)
        //MSVC++ 9.0  _MSC_VER == 1500 (Visual Studio 2008)
        //MSVC++ 8.0  _MSC_VER == 1400 (Visual Studio 2005)
        //MSVC++ 7.1  _MSC_VER == 1310 (Visual Studio 2003)
        //MSVC++ 7.0  _MSC_VER == 1300
        //MSVC++ 6.0  _MSC_VER == 1200
        //MSVC++ 5.0  _MSC_VER == 1100
#ifdef __GNUC__
        printf("\nCompiled by gcc-%d.%d.%d\n", __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__);
#elif _MSC_VER
        // printf("\nCompiled by %d\n", _MSC_VER);
        if (_MSC_VER == 1900)
                printf("\nCompiled by VC2015\n");
        else if (_MSC_VER == 1800)
                printf("\nCompiled by VC2013\n");
        else if (_MSC_VER == 1700)
                printf("\nCompiled by VC2012\n");
        else if (_MSC_VER == 1600)
                printf("\nCompiled by VC2010\n");
        else if (_MSC_VER == 1500)
                printf("\nCompiled by VC2008\n");
        else if (_MSC_VER == 1400)
                printf("\nCompiled by VC2005\n");
        else if (_MSC_VER == 1310)
                printf("\nCompiled by VC2003\n");
        else if (_MSC_VER == 1200)
                printf("\nCompiled by VC6.0");
        else
                printf("\nCompiled by Other VC compiler\n");

#endif // __GNUC__

#ifdef __GLIBC__
        printf("Glibc version :%d \n", __GLIBC__);//C Libraries
#elif __GLIBCXX__
        printf("Glibc version :%d \n", __GLIBCXX__);//C++ Libraries
#endif // __GLIBC__

BlueHazzard


Quote from: hairuoai on November 29, 2016, 08:34:04 AM
Build information options  don't show the compiler version? eg,i use gcc 6.2,and it shows unknow...
so will the next nightly builds add few codes can detect the compiler version which is using ?
//MSVC++ 14.0 _MSC_VER == 1900 (Visual Studio 2015)
        //MSVC++ 12.0 _MSC_VER == 1800 (Visual Studio 2013)
        //MSVC++ 11.0 _MSC_VER == 1700 (Visual Studio 2012)
        //MSVC++ 10.0 _MSC_VER == 1600 (Visual Studio 2010)
        //MSVC++ 9.0  _MSC_VER == 1500 (Visual Studio 2008)
        //MSVC++ 8.0  _MSC_VER == 1400 (Visual Studio 2005)
        //MSVC++ 7.1  _MSC_VER == 1310 (Visual Studio 2003)
        //MSVC++ 7.0  _MSC_VER == 1300
        //MSVC++ 6.0  _MSC_VER == 1200
        //MSVC++ 5.0  _MSC_VER == 1100
#ifdef __GNUC__
        printf("\nCompiled by gcc-%d.%d.%d\n", __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__);
#elif _MSC_VER
        // printf("\nCompiled by %d\n", _MSC_VER);
        if (_MSC_VER == 1900)
                printf("\nCompiled by VC2015\n");
        else if (_MSC_VER == 1800)
                printf("\nCompiled by VC2013\n");
        else if (_MSC_VER == 1700)
                printf("\nCompiled by VC2012\n");
        else if (_MSC_VER == 1600)
                printf("\nCompiled by VC2010\n");
        else if (_MSC_VER == 1500)
                printf("\nCompiled by VC2008\n");
        else if (_MSC_VER == 1400)
                printf("\nCompiled by VC2005\n");
        else if (_MSC_VER == 1310)
                printf("\nCompiled by VC2003\n");
        else if (_MSC_VER == 1200)
                printf("\nCompiled by VC6.0");
        else
                printf("\nCompiled by Other VC compiler\n");

#endif // __GNUC__

#ifdef __GLIBC__
        printf("Glibc version :%d \n", __GLIBC__);//C Libraries
#elif __GLIBCXX__
        printf("Glibc version :%d \n", __GLIBCXX__);//C++ Libraries
#endif // __GLIBC__
What are you talking about? The build log?

and please use code tags if you post code or logs