User forums > Help

Using Irrlicht 1.8.4 with Code::Blocks

(1/1)

ckenyon_17:
I'm having issues with using Irrlicht along with code blocks. I'm running Linux Mint 18.1.

Here are my settings:

Compiler Flags:
---------------------
Produce debugging symbols [-g]
Enable all common compiler warnings (overrides many other settings) [-Wall]
Optimize fully (for speed) [-O3]

Other Options:
---------------------
-fexceptions
-ffast-math

Linker Settings:
---------------------
Link libraries:
---------------------
Irrlicht
GL
GLU
Xxf86vm
Xext
X11

Search Directories:
---------------------
Compiler:
---------------------
../../../../../../opt/irrlicht-1.8.4/include

Linker:
---------------------
../../../../../../opt/irrlicht-1.8.4/lib/Linux

When I build my "main.cpp" file, (which just for a test is the "Hello World" example) everything compiles correctly but when running the file I get "Process terminated with status -1 (0 minute(s), 0 second(s))"

Not sure what I'm doing wrong. If any additional information is needed let me know. Thank you in advance.

BlueHazzard:
use the debugger?
make a clean / build or rebuild?

stahta01:
Uncheck this option!


--- Quote ---Optimize fully (for speed) [-O3]

--- End quote ---

On Windows, the [-O3] option is know to cause bugs.
Note: On Windows, using [-g] and any optimize level is counter to normal.

Tim S.

yvesdm3000:
He's not on windows and I would not think that -O3 would cause this. Maybe the app crashes early on, or the irrlicht library can't load some dependency library?
It's best for starters to disable optimization because that doesn't help debugging.

A good test would be to perform:

ldd path/to/your/test/app

And see if everything resolves. In case you use the dynamic library of irrlicht, do the same on that library.

(I know it doesn't have much to do with C::B but with you compiler)

Yves

BlueHazzard:
and do a error checking on every file irrlicht loads and check for internal errors. This is for sure a programming error and not a problem with codeblocks.

The easiest way to resolve this is simply to hit the red arrow and debug your application

Navigation

[0] Message Index