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

hairuoai · « **Reply #15 on:** November 30, 2016, 01:24:07 am »

Quote from: BlueHazzard on November 29, 2016, 07:00:33 pm

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

the build message...

Code

//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 · « **Reply #16 on:** November 30, 2016, 01:54:26 am »

And now what do you want to achieve?

hairuoai · « **Reply #17 on:** November 30, 2016, 02:48:26 am »

Quote from: BlueHazzard on November 30, 2016, 01:54: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

oBFusCATed · « **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.

hairuoai · « **Reply #19 on:** November 30, 2016, 09:06:12 am »

Quote from: oBFusCATed 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.

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...

BlueHazzard · « **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)

Quote from: hairuoai on November 30, 2016, 02:48:26 am

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

//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?

hairuoai · « **Reply #21 on:** December 01, 2016, 01:10:33 am »

Quote from: BlueHazzard 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)

Quote from: hairuoai on November 30, 2016, 02:48:26 am

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

//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.

stahta01 · « **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

--- 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, ,
--

oBFusCATed · « **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.

oBFusCATed · « **Reply #24 on:** December 21, 2016, 12:08:47 pm »

Fixed in rev 10946.

stahta01 · « **Reply #25 on:** December 21, 2016, 10:13:28 pm »

Quote from: oBFusCATed on December 21, 2016, 12:08:47 pm

Fixed in rev 10946.

Thank you.

Tim S.

Xaviou · « **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'

stahta01 · « **Reply #27 on:** December 23, 2016, 08:37:27 pm »

Quote from: Xaviou 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'

What does

Code

wx-config --list

on the command line return?

Tim S.

Xaviou · « **Reply #28 on:** December 23, 2016, 11:49:27 pm »

Quote from: stahta01 on December 23, 2016, 08:37:27 pm

What does
Code
wx-config --list
on the command line return?

Tim S.

Code

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'

stahta01 · « **Reply #29 on:** December 23, 2016, 11:58:30 pm »

Quote from: Xaviou on December 23, 2016, 11:49:27 pm

Quote from: stahta01 on December 23, 2016, 08:37:27 pm
What does
Code
wx-config --list
on the command line return?

Tim S.
Code
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.

Code::Blocks Forums

News:

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

hairuoai

Re: The 20 November 2016 build (10922) is out.

BlueHazzard

Re: The 20 November 2016 build (10922) is out.

hairuoai

Re: The 20 November 2016 build (10922) is out.

oBFusCATed

Re: The 20 November 2016 build (10922) is out.

hairuoai

Re: The 20 November 2016 build (10922) is out.

BlueHazzard

Re: The 20 November 2016 build (10922) is out.

hairuoai

Re: The 20 November 2016 build (10922) is out.

stahta01

Re: The 20 November 2016 build (10922) is out.

oBFusCATed

Re: The 20 November 2016 build (10922) is out.

oBFusCATed

Re: The 20 November 2016 build (10922) is out.

stahta01

Re: The 20 November 2016 build (10922) is out.

Xaviou

Re: The 20 November 2016 build (10922) is out.

stahta01

Re: The 20 November 2016 build (10922) is out.

Xaviou

Re: The 20 November 2016 build (10922) is out.

stahta01

Re: The 20 November 2016 build (10922) is out.