User forums > Using Code::Blocks

C::B doesn't show g++ as a compiler option (MSWindows)

<< < (2/4) > >>

BlueHazzard:

--- Quote from: OldFangle on January 08, 2015, 09:26:26 pm ---
--- Quote from: stahta01 on January 08, 2015, 09:18:51 pm ---You are on my list of people to ignore.

--- End quote ---

Why?  I'm explaining this as best I can.  I can't build anything with g++ because I can't access it yet.  There's no log, there's nothing to show.  The only compiler error at this point is my inability to understand how to get the g++ compiler on a path so that code::blocks can include it in the selection menu.

Cheers


--- End quote ---

read exactly what stahta01 has written:

--- Quote from: stahta01 on January 08, 2015, 07:01:22 pm ---http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F
Post a full re-build log and you might get some help.
Do NOT and I will just ignore you.

--- End quote ---

I think you are obsess about this gcc and g++ stuff... Many other people use SFML without modifying the tool chain like you want to do...
unless you follow the instructions stahta01 gave you we won't be able to help you....

PS. i think you have installed multiple compilers, or messed somehow with the paths, and installation directories (ex. why is CMake in your c::b folder???)...

greetings

Jenna:
Just to make it clear:
gcc hast two meanings Gnu Compiler Collection and gnu c-compiler.
The first one is the name of the so called toolchain, where all used executables are defined (see "Settings -> Compiler -> ...").
Inside this toolchain the c++-compiler (g++) and the c-compiler (gcc) are defined (and some other linking and debugging related stuff).
Normally it should work out of the box. You might need to adjust the compiler installation directory (at least on windows). If yes, try the "Auto detect"-button.
The executable names might differ on windows you can have e.g. mingw32-g++.exe or mingw64-g++.exe instead of just g++.exe, there might also be some suffix like -dw2 or -sjlj, that depends on you installation.

OldFangle:
Hello everyone

(First of all thanks for the typo alert.  Yeah, g++.exe would be in CodeBlocks\MinGW\ , not CodeBlocks\CMake\  *sigh*)

Next, thank you for helping me understand that the default C::B setting, GCC, is in this case a kind of container in which the presence of g++ is implicit.

If it's already selected that way, then yes, I understand that the next step is to try to Build/Run a project and get a Build Log of the result of the attempt.

I'll get to work on that now.

Cheers, everyone.  Thanks for everyone's attention and time.

OldFangle:
Hello again, here's the Build Log...
>>>
-------------- Build: Debug in 2015-01-06_02 (compiler: GNU GCC Compiler)---------------

mingw32-g++.exe -Wall -fexceptions -DSFML_STATIC -g -ID:\SFML-2.2\include -ID:\SFML-2.2\bin -I"C:\Program Files (x86)\CodeBlocks\MinGW\bin" -I"C:\Program Files (x86)\CodeBlocks\MinGW\mingw32\bin" -ID:\SFML-2.2\include -ID:\SFML-2.2\include\SFML -c D:\_PROJECT_CODING\2015-01-06_02\main.cpp -o obj\Debug\main.o
mingw32-g++.exe -LD:\SFML-2.2\lib -LD:\SFML-2.2\bin -LD:\SFML-2.2\lib -o bin\Debug\2015-01-06_02.exe obj\Debug\main.o   -lsfml-graphics -lsfml-window -lsfml-system
Output file is bin\Debug\2015-01-06_02.exe with size 744.51 KB
Process terminated with status 0 (0 minute(s), 3 second(s))
0 error(s), 0 warning(s) (0 minute(s), 3 second(s))

-------------- Run: Debug in 2015-01-06_02 (compiler: GNU GCC Compiler)---------------

Checking for existence: D:\_PROJECT_CODING\2015-01-06_02\bin\Debug\2015-01-06_02.exe
Executing: "C:\Program Files (x86)\CodeBlocks/cb_console_runner.exe" "D:\_PROJECT_CODING\2015-01-06_02\bin\Debug\2015-01-06_02.exe"  (in D:\_PROJECT_CODING\2015-01-06_02\.)

<<<

...And here's the error message in the pop-up window:
>>>
The procedure entry point _ZSt24__throw_out_of_range_fmtPKcz could not be located in the dynamic link library libstdc++-6.dll
<<<

My rather simple objective is to figure how to help C::B or/and SFML-2.2 find the support files they need.
I'm not perfectly clear on when to use in-house .lib, or else when inclusion of .dll files is unavoidable.
I'm aiming to make some standalone utilities so I've been trying to compile 'statically'.

Thanks again

stahta01:
I suggest using the same compiler to build both the library and the code using the library.

At least you posted the build log and clarified that the error is a run-time error.

Do you know which GCC version/toolchain was used to build the library?

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page