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

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: 1082
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: 9649
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: 1082
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: 5528
    • 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: 9649
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: 9649
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: 5528
    • 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: 5528
    • 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: 5528
    • 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