Author Topic: The 20 November 2016 build (10922) is out.  (Read 10670 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 4976
The 20 November 2016 build (10922) is out.
« on: November 20, 2016, 05:45:37 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 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:



« Last Edit: November 20, 2016, 09:32:50 pm by jens »

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #1 on: November 20, 2016, 08:19:25 pm »
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/


Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7116
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: The 20 November 2016 build (10922) is out.
« Reply #3 on: November 20, 2016, 09:58:42 pm »
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.

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 4976
Re: The 20 November 2016 build (10922) is out.
« Reply #4 on: November 21, 2016, 07:15:09 am »
thanks for spotting the link mistake.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 4849
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 20 November 2016 build (10922) is out.
« Reply #5 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.
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 BlueHazzard

  • Lives here!
  • ****
  • Posts: 1180
Re: The 20 November 2016 build (10922) is out.
« Reply #6 on: November 21, 2016, 04:08:26 pm »
Quote
applied 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

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 4976
Re: The 20 November 2016 build (10922) is out.
« Reply #7 on: November 21, 2016, 08:08:20 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.

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1180
Re: The 20 November 2016 build (10922) is out.
« Reply #8 on: November 22, 2016, 10:03:07 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...

Offline hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #9 on: November 22, 2016, 11:35:33 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

Offline frankofrank

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 20 November 2016 build (10922) is out.
« Reply #10 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

Offline liaoya

  • Single posting newcomer
  • *
  • Posts: 9
Re: The 20 November 2016 build (10922) is out.
« Reply #11 on: November 25, 2016, 03:33:16 am »
Mcafee VirusScan Enterprise + AntiSpyware Enterprise 8.8 reports a virus in wxspeedbutton.dll on Windws 7 Professional. Would you take a look at it?

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #12 on: November 27, 2016, 11:13:43 am »
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'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #13 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__

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1180
Re: The 20 November 2016 build (10922) is out.
« Reply #14 on: November 29, 2016, 07:00:33 pm »

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

Offline hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #15 on: November 30, 2016, 01:24:07 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

the build message...
Code: [Select]
//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__

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1180
Re: The 20 November 2016 build (10922) is out.
« Reply #16 on: November 30, 2016, 01:54:26 am »
And now what do you want to achieve?

Offline hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #17 on: November 30, 2016, 02:48:26 am »
And now what do you want to achieve?
fix the building message like this:

||=== Build file: "no target" in "no project" (compiler: unknown) ===|

seems it does not recognise the GCC6.2.0 i used

make the codeblocks to detect the compiler version which is working now...in case i want to change another compile version


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #18 on: November 30, 2016, 08:18:40 am »
hairuoal: Do you have a project? If not try to create one and then choose your gcc 6.2 compiler you've set up in the compiler settings. If you don't want to create project you'll have to set a default compiler. I think it is done again in the compiler settings dialog.
<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 hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #19 on: November 30, 2016, 09:06:12 am »
hairuoal: Do you have a project? If not try to create one and then choose your gcc 6.2 compiler you've set up in the compiler settings. If you don't want to create project you'll have to set a default compiler. I think it is done again in the compiler settings dialog.
no,i don't have a project...
if fact,i have already set six compilers:TDM GCC5.1,MinGW Gcc5.3,mingw32 Gcc6.2,LLVM,VC2010and vc2015.....then i found i set a default compiler,and the build message cannot recongnise any of the compiler version...so i think the next version can do something to improve this...

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1180
Re: The 20 November 2016 build (10922) is out.
« Reply #20 on: November 30, 2016, 12:01:40 pm »
Lets try to fix this:
1) Use projects. Codeblocks is made to use Projects, where it stores what compiler to use, the right compiler settings and so on. If you don't use projects you can't debug your program and you will run into many other issues. If you don't use projects where should codeblocks decide what compiler he is using?

2)
fix the building message like this:

||=== Build file: "no target" in "no project" (compiler: unknown) ===|

seems it does not recognise the GCC6.2.0 i used

make the codeblocks to detect the compiler version which is working now...in case i want to change another compile version
Please use code tags for buil log. It is difficult to differentiate between your message and the build log.
Also, if you have compiling problems please read and follow this:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

3) Use a new tiopic. This has nothing to do with the nightly directly, but how you use codeblocks

4)
Code: [Select]
//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__
Is this code from you? Do you want to run this code?



Offline hairuoai

  • Single posting newcomer
  • *
  • Posts: 8
Re: The 20 November 2016 build (10922) is out.
« Reply #21 on: December 01, 2016, 01:10:33 am »
Lets try to fix this:
1) Use projects. Codeblocks is made to use Projects, where it stores what compiler to use, the right compiler settings and so on. If you don't use projects you can't debug your program and you will run into many other issues. If you don't use projects where should codeblocks decide what compiler he is using?

2)
fix the building message like this:

||=== Build file: "no target" in "no project" (compiler: unknown) ===|

seems it does not recognise the GCC6.2.0 i used

make the codeblocks to detect the compiler version which is working now...in case i want to change another compile version
Please use code tags for buil log. It is difficult to differentiate between your message and the build log.
Also, if you have compiling problems please read and follow this:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

3) Use a new tiopic. This has nothing to do with the nightly directly, but how you use codeblocks

4)
Code: [Select]
//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__
Is this code from you? Do you want to run this code?
Thank you ,use project can work.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 5586
    • My Best Post
Re: The 20 November 2016 build (10922) is out.
« Reply #22 on: December 20, 2016, 06:41:14 pm »
Does SVN 10945, build with configure/make on Linux?

I had to add this patch to get configure/make to work on Windows (using MSys2).

Tim S.

Code: [Select]
--- a/configure.ac
+++ b/configure.ac
@@ -373,6 +373,7 @@ CPPFLAGS="$CPPFLAGS -DPIC $CB_TINYXML_CFLAGS"
 CXXFLAGS="$CXXFLAGS $PIC_CFLAGS -fexceptions"
 AC_SUBST(codeblocks_PCH_FLAGS, "$PCH_FLAGS")
 
+m4_include([m4/ax_cxx_compile_stdcxx.m4])
 AX_CXX_COMPILE_STDCXX(11, noext)
 
 dnl AM_PATH_GTK(1.2.7, ,
--

C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #23 on: December 20, 2016, 08:27:40 pm »
Yep, rev 10938 broke this and it worked for me because I have this in globally accessible location.
<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 oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #24 on: December 21, 2016, 12:08:47 pm »
Fixed in rev 10946.
<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 stahta01

  • Lives here!
  • ****
  • Posts: 5586
    • My Best Post
Re: The 20 November 2016 build (10922) is out.
« Reply #25 on: December 21, 2016, 10:13:28 pm »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #26 on: December 23, 2016, 07:17:09 pm »
Hi.

I've found 2 problems on OS X :
  • The Compiler toolbar does'n include the "build target" drop down list
  • It seems that the wx-config call placed in the compiler and linker options are not called

See the attached screenshot : it shows the result of a basic wxWidgets project build (the command line doesn't have any wx-config thing despite it is present in the project build options).

Tested with a basic wxWidgets project and C::B rev 10922 from frankofrank.

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline stahta01

  • Lives here!
  • ****
  • Posts: 5586
    • My Best Post
Re: The 20 November 2016 build (10922) is out.
« Reply #27 on: December 23, 2016, 08:37:27 pm »
Hi.

I've found 2 problems on OS X :
  • The Compiler toolbar does'n include the "build target" drop down list
  • It seems that the wx-config call placed in the compiler and linker options are not called

See the attached screenshot : it shows the result of a basic wxWidgets project build (the command line doesn't have any wx-config thing despite it is present in the project build options).

Tested with a basic wxWidgets project and C::B rev 10922 from frankofrank.

Regards
Xav'

What does
Code: [Select]
wx-config --liston the command line return?

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #28 on: December 23, 2016, 11:49:27 pm »
What does
Code: [Select]
wx-config --liston the command line return?

Tim S.
Code: [Select]
wx-config --list

    Default config is osx_cocoa-unicode-static-3.1

  Default config in /Users/xavier/dev/wx310/build-static will be used for output
wx-config is actually a copy in /usr/local/bin of the one created during the build process in /Users/xavier/dev/wx310/build-static

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline stahta01

  • Lives here!
  • ****
  • Posts: 5586
    • My Best Post
Re: The 20 November 2016 build (10922) is out.
« Reply #29 on: December 23, 2016, 11:58:30 pm »
What does
Code: [Select]
wx-config --liston the command line return?

Tim S.
Code: [Select]
wx-config --list

    Default config is osx_cocoa-unicode-static-3.1

  Default config in /Users/xavier/dev/wx310/build-static will be used for output
wx-config is actually a copy in /usr/local/bin of the one created during the build process in /Users/xavier/dev/wx310/build-static

Regards
Xav'

Your problem might be user or project setting error; because I believe the wizard generated code does NOT work with wx 3.1.

I suggest you post your question in a thread by itself in http://forums.codeblocks.org/index.php/board,3.0.html

Edit: That is for the wx-config not working problem; the display of drop down target I think here is a good as anywhere till a CB Dev Team member says otherwise.

Tim S.
« Last Edit: December 24, 2016, 12:01:27 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #30 on: December 24, 2016, 12:19:41 am »
Well : I think there is nothing in the project file that is "wx-3.1.0" specific.
Here is the content of the project file :
Code: [Select]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="CBTest1" />
<Option pch_mode="2" />
<Option compiler="gcc" />
<Build>
<Target title="Debug">
<Option output="bin/Debug/CBTest1" prefix_auto="1" extension_auto="1" />
<Option object_output="obj/Debug/" />
<Option type="0" />
<Option compiler="gcc" />
<Option projectLinkerOptionsRelation="2" />
<Compiler>
<Add option="-g" />
</Compiler>
<ExtraCommands>
<Add after="/Developer/Tools/Rez -d __DARWIN__ -t APPL Carbon.r -o $(TARGET_OUTPUT_FILE)" />
</ExtraCommands>
</Target>
<Target title="Release">
<Option output="bin/Release/CBTest1" prefix_auto="1" extension_auto="1" />
<Option object_output="obj/Release/" />
<Option type="0" />
<Option compiler="gcc" />
<Option projectLinkerOptionsRelation="2" />
<Compiler>
<Add option="-O2" />
</Compiler>
<Linker>
<Add option="-s" />
</Linker>
<ExtraCommands>
<Add after="/Developer/Tools/Rez -d __DARWIN__ -t APPL Carbon.r -o $(TARGET_OUTPUT_FILE)" />
</ExtraCommands>
</Target>
</Build>
<Compiler>
<Add option="`wx-config --cflags`" />
<Add option="-Wall" />
</Compiler>
<Linker>
<Add option="`wx-config --libs`" />
</Linker>
<Unit filename="CBTest1App.cpp" />
<Unit filename="CBTest1App.h" />
<Unit filename="CBTest1Main.cpp" />
<Unit filename="CBTest1Main.h" />
<Extensions>
<code_completion />
<envvars />
<debugger />
</Extensions>
</Project>
</CodeBlocks_project_file>

As you can see in the screenshot, the compilation command line is a "basic" one (without any wx-config command nor result as it is specified in the project options).

Regards
Xav'
« Last Edit: December 24, 2016, 12:29:31 am by Xaviou »
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #31 on: December 24, 2016, 12:02:45 pm »
Hi.

I've perhaps found the source of the problem : CB doesn't seems to have the full correct $PATH env var.

For this, I've added following "pre-build" command:
Code: [Select]
echo $PATHThe printed result doesn't contain "/usr/local/bin" (witch is where I've placed a copy of wx-config)

$PATH value from Code::Blocks:
/usr/bin:/usr:/bin:/usr/sbin:/sbin

$PATH value from a terminal window:
/Library/Frameworks/Python.framework/Versions/3.5/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

The first diff (Python related) is added from my ".bash_profile", but I don't know where the "/usr/local/bin" one come from.

I've also made a test to see the content of the $PATH var in a GUI application and I've obtained a third different result :
/usr/bin:/bin:/usr/sbin:/sbin
The "/usr" part is not present.

Does someone have any idea on how to modify this env var "system wide" ?

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7116
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: The 20 November 2016 build (10922) is out.
« Reply #32 on: December 24, 2016, 01:01:10 pm »
Hi.

I've perhaps found the source of the problem : CB doesn't seems to have the full correct $PATH env var.

For this, I've added following "pre-build" command:
Code: [Select]
echo $PATHThe printed result doesn't contain "/usr/local/bin" (witch is where I've placed a copy of wx-config)

$PATH value from Code::Blocks:
/usr/bin:/usr:/bin:/usr/sbin:/sbin

$PATH value from a terminal window:
/Library/Frameworks/Python.framework/Versions/3.5/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

The first diff (Python related) is added from my ".bash_profile", but I don't know where the "/usr/local/bin" one come from.

I've also made a test to see the content of the $PATH var in a GUI application and I've obtained a third different result :
/usr/bin:/bin:/usr/sbin:/sbin
The "/usr" part is not present.

Does someone have any idea on how to modify this env var "system wide" ?

Regards
Xav'
If the environment-variables plugin is installed, you can set it in "Settings->Environment->Environment variables".

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #33 on: December 25, 2016, 10:02:20 am »
If the environment-variables plugin is installed, you can set it in "Settings->Environment->Environment variables".
It worked.
I've added "PATH" = "$PATH:/usr/local/bin" to the environment variables plugin, ignored the warning message saying that this variable was already set, and restarted CB and the build process worked fine.

Thank you.

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #34 on: December 26, 2016, 04:43:11 pm »
I think this is the default behaviour of the launcher or the dock.

About the build target combo: Can you check if the auidemo in the wx works correctly on mac. I hope they have added combos in the toolbars in the demo. If they haven't you can probably easily add one.
<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

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #35 on: December 26, 2016, 07:46:10 pm »
Hi
About the build target combo: Can you check if the auidemo in the wx works correctly on mac. I hope they have added combos in the toolbars in the demo.
They did, and it works : see attached screenshot.

Another thing that doesn't work on Mac : the scripted wizard for wxWidgets project add a "post build" command containing :
File wizard.script line 917
Code: [Select]
/Developer/Tools/Rez -d __DARWIN__ -t APPL Carbon.r -o $(TARGET_OUTPUT_FILE)
The "/Developer/Tools/" directory doesn't exists.
I tried removing the full path :
Code: [Select]
Rez -d __DARWIN__ -t APPL Carbon.r -o $(TARGET_OUTPUT_FILE)It worked but the resulting executable can't be runned.
I've searched a little on internet, and it seems that this command remove the "terminal" console for GUI applications (perhaps it has other features that I don't know).
The only thing that I know is that it can be replaced by "SetFile" (as it can be found in wxWidgets minimal sample makefile).
So the correct command to add is :
Code: [Select]
SetFile -t APPL $(TARGET_OUTPUT_FILE)
Perhaps someone can confirm this.

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #36 on: December 26, 2016, 08:07:01 pm »
They did, and it works : see attached screenshot.

Just for confirmation - you're using the same wx libs for cb and auidemo right?

So the correct command to add is :
Code: [Select]
SetFile -t APPL $(TARGET_OUTPUT_FILE)

Patches welcome.
<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 oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #37 on: December 27, 2016, 11:45:18 am »
They did, and it works : see attached screenshot.

Can you try this patch (it is a shot in the dark):
Code: [Select]
diff --git a/src/plugins/compilergcc/compilergcc.cpp b/src/plugins/compilergcc/compilergcc.cpp
index a88716dc8..4354d7279 100644
--- a/src/plugins/compilergcc/compilergcc.cpp
+++ b/src/plugins/compilergcc/compilergcc.cpp
@@ -615,9 +615,9 @@ bool CompilerGCC::BuildToolBar(wxToolBar* toolBar)
     wxString my_16x16 = Manager::isToolBar16x16(toolBar) ? _T("_16x16") : _T("");
     Manager::Get()->AddonToolBar(toolBar,_T("compiler_toolbar")+my_16x16);
     m_pToolTarget = XRCCTRL(*toolBar, "idToolTarget", wxChoice);
+    DoRecreateTargetMenu(); // make sure the tool target combo is up-to-date
     toolBar->Realize();
     toolBar->SetInitialSize();
-    DoRecreateTargetMenu(); // make sure the tool target combo is up-to-date
     return true;
 }

<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

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #38 on: December 27, 2016, 12:18:21 pm »
Hi
They did, and it works : see attached screenshot.

Just for confirmation - you're using the same wx libs for cb and auidemo right?
No : I'm actually using Code::Blocks built by frankofrank with the wx libs included and for auidemo, it is a freshly updated git repo.  :-[

So the correct command to add is :
Code: [Select]
SetFile -t APPL $(TARGET_OUTPUT_FILE)

Patches welcome.

Can you try this patch (it is a shot in the dark):
......
Well... the last time I've tried to build CB on Mac wasn't successfull (it was some months ago).

I think it's time for me to re-try this until it succeed  :P

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline Xaviou

  • Almost regular
  • **
  • Posts: 240
    • X@v's Web
Re: The 20 November 2016 build (10922) is out.
« Reply #39 on: December 27, 2016, 05:06:45 pm »
I think it's time for me to re-try this until it succeed  :P
And of course : it fails...  >:(  => http://forums.codeblocks.org/index.php/topic,21625.0.html

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : http://x.psoud.free.fr/

Offline darmar

  • Multiple posting newcomer
  • *
  • Posts: 37
Re: The 20 November 2016 build (10922) is out.
« Reply #40 on: January 17, 2017, 08:53:02 am »
It seems, that C::B experiencing problems in calltips with highlighting of current variable on Windows.

Some more explanation: current variable under cursor should be highlighted. However on a new system (I mean, default settings of C::B) the calltips are displayed in a single black color. The user can change the color for the calltips on Settings->Environment->Colours. It works. However a new user should find it first.

You can test this problem, by temporally renaming your C::B settings folder on "C:Users\YourName\AppData\Roaming\CodeBlocks" (it is hidden folder) and starting C::B.

I looked for this problem. I think, I found: in file C::B/src/sdk/ccmanager.cpp on lines 292 and 293, Calltips foreground is defined as "DimGray, while Calltips background is defined as "DarkBlue". Problem, that on Windows there are no such colors predefined. Changin them to "GRAY" and "BLUE", solve the problem.

Before: lines 292-293
Code: [Select]
    cmgr->RegisterColour(_("Code completion"), _("Tooltip/Calltip foreground"), wxT("cc_tips_fore"),      wxColour(wxT("DimGrey")));
    cmgr->RegisterColour(_("Code completion"), _("Tooltip/Calltip highlight"),  wxT("cc_tips_highlight"), wxColour(wxT("DarkBlue")));

Chage to:

Code: [Select]

    cmgr->RegisterColour(_("Code completion"), _("Tooltip/Calltip foreground"), wxT("cc_tips_fore"),      wxColour(wxT("GRAY")));
    cmgr->RegisterColour(_("Code completion"), _("Tooltip/Calltip highlight"),  wxT("cc_tips_highlight"), wxColour(wxT("BLUE")));

I did not experience this problem on Linux. I guess, that these colors are predefined on Linux.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 9720
Re: The 20 November 2016 build (10922) is out.
« Reply #41 on: January 17, 2017, 09:05:53 am »
Can you post a patch?
<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 darmar

  • Multiple posting newcomer
  • *
  • Posts: 37
Re: The 20 November 2016 build (10922) is out.
« Reply #42 on: January 17, 2017, 06:17:56 pm »
The patch is attached. I used "BLUE" and "DIM GREY" colors from http://docs.wxwidgets.org/3.1/classwx_colour_database.html