Help with a Makefile (IDEs are 4 teh newbz)

[MutantJohn]

Yeah, yeah, yeah, IDEs are good for complex and long code.

But here's a Makefile I have which I modified from a C-syntax Makefile so I have no idea if it's good practice.

Basically, the compiler no longer complains about unused or unitialized values and I want it to because I'm bad a programming like that.

MKFILE    = Makefile


GCC       = g++ -g -O3 -W -Wall -Wextra -lpthread


CSOURCE   = main.cpp
CHEADER   = structures.h
OBJECTS   = ${CSOURCE:.cpp=.o}
EXECBIN   = regulus


all : ${EXECBIN}


${EXECBIN} : ${OBJECTS}
	${GCC} -o $@ ${OBJECTS} -lm


 
%.o : %.c


	${GCC} -c $<




clean :
	- rm ${OBJECTS} ${EXECBIN}




again :
	${MAKE} clean all

[jimblumberg]

You may want to add a few more warning options.

Jim

[MutantJohn]

Lol thank you for the link.

And also, I should've changed line 21 to "%.o : %.cpp" lol :P

[Neo1]

Specifically, i would add -ansi and -pedantic. They make the compiler warn you about using GCC specific extensions, which might mean the code won't work with another compiler.

Unless ofcourse you're purposefully using GCC extensions.

[rcgldr]

Wouldn't you need to include a dependency that shows main.o is dependent on main.cpp and structures.h?

[Salem]

> Basically, the compiler no longer complains about unused or unitialized values and I want it to because I'm bad a programming like that.
If you're bad at programming, how much worse are you at debugging?

Because being silent about potential errors doesn't mean they suddenly vanish.

If you're bad at programming, you should be looking to get maximum help from your tools at every step of the way, and that means turning the warning level up to the max.