blasteroid | shooting game inherited from the classic arcade game | Game Engine library

something like the following makefile contents should do the job

Notes:

1. header files are only needed during the compile step
2. library files are only needed during the link step
3. best to have the first 'target' be 'all' so the makefile can be successfully executed without have to include a 'Blasteroids' parameter
4. having a 'target' 'clean' makes it easy to clear away the items that will be rebuilt
5. any 'target' that does not produce a file of the same name should be listed in a '.PSEUDO' operator
6. the linker processes the linker command line items in the order listed on the command line. Therefore, list the objects, then the directories, then the library 'short' names
7. list the header files at the end of the compile command line
8. use macros (like CC and RM) that contain the full path to the executables so the correct executable is used, other wise the first item found in the $PATH that matches the name will be used.
9. $^ is a built in macro that expands to the recipe dependencies
10. $< is a built in macro that expands to the first dependency
11. $@ is a built in macro that expands to the recipe 'target'
12. the $(SRC:.c=?) statements do character replacement on the extension of the file names contained in the $(SRC) macro
13. the %.o:%.c recipe says for each source file to be compiled into a object file, use this recipe
14. the '-ggdb' is so the maximum debug information will be available to the 'gdb' debugger.
15. this pattern of 'makefile' can be extensively used for other projects with only minor variations. For more flexibility could also insert a recipe for automatically generating the header file dependencies, so would not need to list them individually in the compile recipe, but for now, the following makefile contents will do what you are currently trying to perform

and now the makefile