This should do it: SOURCES = $(wildcard *.cpp) $(wildcard */*.cpp) If you change you mind and want a recursive solution (i.e. to any depth), it can be done but it involves some of the more powerful Make functions. You know, the ones that allow you to do things you really shouldn’t. EDIT: Jack Kelly points … Read more
Have a look here: basically, you define a “toolchain file” that sets things like the system name, paths to compilers and so on. You then call cmake like so: cmake /path/to/src -DCMAKE_TOOLCHAIN_FILE=/path/to/toolchain/foo-bar-baz.cmake
Yes, it is written in a rather obvious way: TARGETS= file1 file2 file3 all: $(TARGETS) file1: dep1 dep2 file2: dep2 dep3 dep4 file3: dep2 dep1 $(TARGETS): cat $^ > $@ UPD. Just to clarify. Generic make rule looks like this: targets… : prerequisites… recipe … Any part of the rule can be omitted. Without the … Read more
I found a solution using the eval function: $(eval variablename=whatever) This works 🙂 (although I may now try to find an easier build system ;)) Thanks everyone for reading and also of course @eriktous for writing!
CMake generated makefiles support the DESTDIR coding convention for makefiles. Thus you can override the default installation location by setting the DESTDIR variable upon invoking make: $ make install DESTDIR=/opt/local There is no need to re-run CMake.
Use a target-specific variable There is one more special feature of target-specific variables: when you define a target-specific variable that variable value is also in effect for all prerequisites of this target, and all their prerequisites, etc. (unless those prerequisites override that variable with their own target-specific variable value). TEXENGINE=pdflatex pdflatex: echo the engine is … Read more
You almost have it right; why did you add the semicolon? To do it on the configure line: ./configure CFLAGS=’-g -O2 -w’ CXXFLAGS=’-g -O2 -w’ To do it on the make line: make CFLAGS=’-g -O2 -w’ CXXFLAGS=’-g -O2 -w’ However, that doesn’t really remove consider all warnings as errors; that removes all warnings. So specifying … Read more
Suppose you were writing an ordinary rule: $(DEST_DIR)/foo : $(SOURCE_DIR)/foo cp $(SOURCE_DIR)/foo $(DEST_DIR)/foo That works, but the redundancy is troublesome. Sooner or later you’ll change $(DEST_DIR)/foo in the preq but forget to change it in the rule. And the rule is hard to read. So we put in an automatic variable: $(DEST_DIR)/foo : $(SOURCE_DIR)/foo cp … Read more
Things have apparently changed. I found the following: Checkmake Mint Of the two, Checkmake has (as of 2018/11) more recent development, but I haven’t tried either.
You have to understand that a makefile is really written in two completely different “languages”, in one file. Recipes (the commands that run compilers, echo, etc.) are written in shell script syntax. The rest of the makefile that is not in a recipe is written in makefile syntax. In order for make to tell the … Read more