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...
//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__
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)
//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?
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.
--- 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, ,
--
What does
on the command line return?
Tim S.
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'
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 :
<?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'
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 (https://sourceforge.net/p/codeblocks/code/HEAD/tree/trunk/src/plugins/scriptedwizard/resources/wxwidgets/wizard.script) line 917
/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 :
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 :
SetFile -t APPL $(TARGET_OUTPUT_FILE)
Perhaps someone can confirm this.
Regards
Xav'
They did, and it works : see attached screenshot.
Can you try this patch (it is a shot in the dark):
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;
}
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
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:
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.