Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
The places to look for compiler command options:
1) Settings->Compiler -> Select your compiler from the drop down menu
1.1) Compiler settings -> Compiler flags
1.2) Compiler settings -> Other compiler options
2) With an open project Project -> Build options
2.1) Select the project name on the left -> Compiler settings->Compiler flag
2.2) Select the project name on the left -> Compiler settings->Other compiler options
2.3) Select the Build target name on the left -> Compiler settings-> Compiler flag
2.4) Select the Build target name on the left -> Compiler settings-> Other compiler options
2
Help / Re: problem with "File/New/File..."
« Last post by BlueHazzard on Today at 08:20:00 am »
Can you please exactly describe the failing steps and the outcome? I am not sure if i understand the issue...

If you can reproduce this, please post a step by step list. Something like this:
1) Open codeblocks
2) Crete a new project
3) Add file XY by clicking Project->Add
ecc...

Thank you!
3
Help / Re: problem with "File/New/File..."
« Last post by nenin on Today at 07:56:11 am »
Quote
Have you compared full build logs for working and non working builds?
It not related to build, it is situation, when C::B makes the wrong path to new file in project. I dont try even build it because compiler gone crazy when such path was offered. 
Quote
Are you sure there aren't differences in global compiler options?
This installation (which is working) is a clone from defected one from my workstation, ~1 month fresh,   including C::B profile and whole mingw. Nothing was changed in global scope.
I suspect that something wrong might be in default.conf, but cannot find anything.
4
Using Code::Blocks / Incorrect forced command line compiler option
« Last post by Condor on Today at 07:26:32 am »
Attempting to switch from 17.12 to 20.03 but initial testing fails. Installed setup version that includes mingw on Windows 10. Initial test of HelloWorld failed because the Toolchain executables in compiler settings had incomplete filenames - apparently mingw now includes processor type as part of the filename. For example, gcc is x86_64-w64-mingw32-gcc.exe whereas Code::Blocks expects the older / shorter gcc.exe filename.

With that issue fixed, at least Code::Blocks found the compiler.

HelloWorld still would not compile. The problem appears to be in the that Code::Blocks insists on trying to force the compiler to the C++20 standard with an incorrect command line option. Even with the Settings > Compiler > Global compiler settings > Compiler flags checkmark in the "Have g++ follow the C++17 ICO C++17 language standard" there is still a command line option of  -std=c++20 included when I look at the Build log. There is also a command line option for -std=c++17

This may actually be two problems: 1) why is there a command line option for a c++ standard that is not specified in the Code::Blocks drop down menu? and 2) apparently, if I did want to have c++20 as the language standard, mingw wants the format to be "-std=c++2a" - I get this from the compiler error message in the Build log window - x86_64-w64-mingw32-g++.exe: error: unrecognized command line option '-std=c++20'; did you mean '-std=c++2a'?


There may be some setup item where that -std=c++20 gets pulled into the command line / makefile... but I cannot find it.

Thanks for any suggestions

Here is the complete command line generated, including the erroneous -std command

x86_64-w64-mingw32-g++.exe -fexceptions -Weffc++ -pedantic-errors -pedantic -Wextra -Wall -std=c++17 -g -std=c++20 -Weffc++ -pedantic-errors -Wextra -Wall -std=gnu++17 -Wsign-conversion -Werror  -c E:\Personal\learning\CPP_CodeBlocks\NewProject1\main.cpp -o obj\Debug\main.o
5
Plugins development / Re: Keybinder v2 notes/problems
« Last post by oBFusCATed on Today at 01:32:17 am »
I don't know what you've done, but the last commit broke the eol characters in git. They are now the windows style on linux. This is something which must not happen. Can you try to fix it? I suppose the same problem is happening with svn.
6
Using Code::Blocks / Re: Code::Blocks colors
« Last post by oBFusCATed on Yesterday at 11:59:49 pm »
3. Now GTK4 is in development. This API could be proposed as it might be useful to other apps and IDEs.
You can try. :)
7
Plugins development / Re: Keybinder v2 notes/problems
« Last post by Pecan on Yesterday at 11:57:51 pm »
Code: [Select]
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .libs/cbkeybinder.o: in function `cbKeyBinder::cbKeyBinder()':
/var/tmp/portage/dev-util/codeblocks-9999-r24/work/codeblocks-9999/src/plugins/contrib/keybinder/cbkeybinder.cpp:75: undefined reference to `vtable for cbKeyBinder'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .libs/cbkeybinder.o: in function `cbKeyBinder::~cbKeyBinder()':
/var/tmp/portage/dev-util/codeblocks-9999-r24/work/codeblocks-9999/src/plugins/contrib/keybinder/cbkeybinder.cpp:87: undefined reference to `vtable for cbKeyBinder'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .libs/cbkeybinder.o: in function `cbKeyBinder::CreateKeyBindDefaultFile(bool)':
/var/tmp/portage/dev-util/codeblocks-9999-r24/work/codeblocks-9999/src/plugins/contrib/keybinder/cbkeybinder.cpp:478: undefined reference to `cbKeyBinder::GetTempOldFmtMnuScanFilename()'

My build failed with this. Also the build on travis has failed too https://travis-ci.org/github/obfuscated/codeblocks_sf/builds/671985456

I'm working on it.
8
Using Code::Blocks / Re: Code::Blocks colors
« Last post by mimi89999 on Yesterday at 11:35:58 pm »
3. Now GTK4 is in development. This API could be proposed as it might be useful to other apps and IDEs.
GTK is not the only backend. I saw C:B on Windows and it's equally ugly. Since those platforms are supported, it must be drawn anyway and OS X also has a dark theme.
9
Help / Re: codeblocks.exe - Entry point not found
« Last post by GianBlocks on Yesterday at 11:25:06 pm »
What OS are you running? Is it 64bit?

Sorry. Guess I should've added that info before.
I'm running 64bit Windows 8.1.
10
Help / Re: codeblocks.exe - Entry point not found
« Last post by oBFusCATed on Yesterday at 11:20:43 pm »
What OS are you running? Is it 64bit?
Pages: [1] 2 3 4 5 6 ... 10