GECODE MAKEFILE FOR WINDOWS HOW TO
GECODE MAKEFILE FOR WINDOWS FULL

This also makes it less likely that you'll want to have the makefile itself as a dependency, which makes the set of rules cleaner. It's often useful (not least when testing makefiles!) to provide a clean psuedotarget to remove all of the files that were generated, providing a 'clean slate' from which to start. For example, the rule for main.exe could be much simplified to this: $(CXX) -o $^ $(LDFLAGS) Try to avoid repeating hard-coded names in the production rules. There are a number of changes I'd make to that line, but one is to consolidate $(LIBRARIES) and $(LINK_FLAGS) into a single variable with a standard name, which is LDFLAGS. Your main rule (pardon the pun) does this: $(CXX) $(LIBRARIES) -o main.exe $(objects) glad.o $(LINK_FLAGS) o file from various version control systems. There are rules to create object files from C and C++, but also from Fortran, Pascal, Modula, assembly language, and for trying to check out a. On my machine, that generates 734 lines of output, so there's really quite a number of implicit rules. Since foo.o won't exist (it's an empty subdirectory) it will attempt to find an implicit rule that will allow it to create that file and with the -d option, it will tell you all of the things it's trying.

GECODE MAKEFILE FOR WINDOWS FULL

To see the full list in order on your machine, create an empty subdirectory, navigate to it and execute make -d foo.o. It finds one eventually because main.cpp exists. Looking for an implicit rule for 'main.o'.Īs you can see, after it has identified a needed target ( main.o) it starts looking for implicit rules to create that target.

To expand this a bit, here's what happens when I run make -d to get it to emit more detailed debugging information: Considering target file 'main.exe'.

GECODE MAKEFILE FOR WINDOWS HOW TO

As long as glad.c is in the current directory, and main.cpp is in the current directory, the built-in rules will understand how to create both glad.o using gcc and main.o using g++.

In this particular Makefile, it means that you can entirely omit the rule for glad.o. $(CC) -c $(CFLAGS) $(CPPFLAGS) $< -o result of this is that if you have defined the flags correctly, you can omit an explicit rule and rely instead on the implicit rule. GNU Make already has an implicit rule for creating. The reason for doing that is in the next point. It's good practice to use variables like INCLUDES to keep things tidy, but it would be better if you added that to CFLAGS: CFLAGS += $(INCLUDES) Similarly, use LDFLAGS instead of LINK_FLAGS. For example, use CFLAGS instead of COMPILE_FLAGS and CXXFLAGS which is the same thing, but for invocations of g++ (or more accurately invocations of $(CXX)). There are standard names for some of the variables you're using. We recommend 'Makefile' because it appears prominently near the beginning of a directory listing, right near other important files such as 'README'.

Either will work, but quoting from the GNU Make man page: The names are equivalent, but since you're using GNU Make, you may as well follow its conventions, and one convention is to name it Makefile instead of makefile. With that said, here are some things that may help you improve your makefile: Prefer Makefile to makefile Even when nice tools such as CMake are used, it's very useful to understand how to write one from scratch. Few people are any good at it, and it's a really fundamental tool. I also wonder if there is a more elegant way to handle the fact that glad is actually a C library and has to be compiled with gcc instead of g++, but g++ is used for everything else.įirst of all, good for you for learning how to write a proper makefile. Since this is basically the first makefile I wrote, I could surely use some criticism as to what is good style and what isn't. $(CC) $(COMPILE_FLAGS) $(INCLUDES) -c -o glad.o glad.c $(CXX) $(COMPILE_FLAGS) $(INCLUDES) -c -o $< $(objects): %.o: %.cpp $(headers) makefile $(CXX) $(LIBRARIES) -o main.exe $(objects) glad.o $(LINK_FLAGS)

LINK_FLAGS = -lglfw3 -lopengl32 -lglu32 -lgdi32 This is a makefile I wrote to compile a simple OpenGL test project which is going to use the libraries GLFW and the C library glad.c.

Gecode makefile for windows