Planned to discard makefile completely and move to codeblocks project, but it provides options on what features to include. Codeblocks can't do that by himself.

It's possible to use codeblocks with makefiles though.

Can't wait to use a real debugger, instead of inserting printf everywhere. Learning codeblocks just for that.

By options I mean things like those:

It's possible to use codeblocks with makefiles though.

Can't wait to use a real debugger, instead of inserting printf everywhere. Learning codeblocks just for that.

By options I mean things like those:

Code:

DP_CDDA?=enabled DP_VIDEO_CAPTURE?=enabled DP_LINK_ZLIB?=dlopen DP_LINK_JPEG?=shared DP_LINK_ODE?=dlopen DP_LINK_CRYPTO?=dlopen DP_LINK_CRYPTO_RIJNDAEL?=dlopen # athlon optimizations #CPUOPTIMIZATIONS?=-march=athlon # athlon xp optimizations #CPUOPTIMIZATIONS?=-march=athlon-xp # athlon 64 optimizations #CPUOPTIMIZATIONS?=-march=athlon64 -m32 # Pentium 3 optimizations #CPUOPTIMIZATIONS?=-march=pentium3 # Pentium 4 optimizations #CPUOPTIMIZATIONS?=-march=pentium4 # 686 (Pentium Pro/II) optimizations #CPUOPTIMIZATIONS?=-march=i686 # No specific CPU (386 compatible) #CPUOPTIMIZATIONS?= # Experimental #CPUOPTIMIZATIONS?=-fno-math-errno -ffinite-math-only -fno-rounding-math -fno-signaling-nans -fassociative-math -freciprocal-math -fno-signed-zeros -fno-trapping-math # Normal CPUOPTIMIZATIONS?=-fno-math-errno -ffinite-math-only -fno-rounding-math -fno-signaling-nans -fno-trapping-math # NOTE: *never* *ever* use the -ffast-math or -funsafe-math-optimizations flag

## Comment