CPPFLAGS is supposed to be for flags for the C PreProcessor; CXXFLAGS is for flags for the C++ compiler. The default rules in make (on my machine, at any rate) pass CPPFLAGS to just about everything, CFLAGS is only passed when compiling and linking C, and CXXFLAGS is only passed when compiling and linking C++.
It is actually executing the command, changing the directory to some_directory, however, this is performed in a sub-process shell, and affects neither make nor the shell you’re working from. If you’re looking to perform more tasks within some_directory, you need to add a semi-colon and append the other commands as well. Note that you cannot … Read more
In CMake you can always declare your own compiler language. So in your case you can e.g. do: cmake_minimum_required(VERSION 2.8) project(MakeBarFromFoo NONE) set( CMAKE_FOO_COMPILE_OBJECT “make_bar_from_foo <SOURCE> <OBJECT>” ) file(GLOB SRCS “*.foo”) add_library(my_rule OBJECT ${SRCS}) set_source_files_properties(${SRCS} PROPERTIES LANGUAGE FOO) Then you can simply work with it as you would with other object library targets. But you … Read more
Here’s the Makefile I’ve added to the documentation (currently in review so I’ll post it here) : # Set project directory one level above the Makefile directory. $(CURDIR) is a GNU make variable containing the path to the current working directory PROJDIR := $(realpath $(CURDIR)/..) SOURCEDIR := $(PROJDIR)/Sources BUILDDIR := $(PROJDIR)/Build # Name of the … Read more
In my opinion, directories should not be considered targets of your makefile, either in technical or in design sense. You should create files and if a file creation needs a new directory then quietly create the directory within the rule for the relevant file. If you’re targeting a usual or “patterned” file, just use make‘s … Read more
crti.o is the bootstrap library, generally quite small. It’s usually statically linked into your binary. It should be found in /usr/lib. If you’re running a binary distribution they tend to put all the developer stuff into -dev packages (e.g. libc6-dev) as it’s not needed to run compiled programs, just to build them. You’re not cross-compiling … Read more
Your linker (ld) obviously doesn’t like the order in which make arranges the GCC arguments so you’ll have to change your Makefile a bit: CC=gcc CFLAGS=-Wall LDFLAGS=-lm .PHONY: all all: client .PHONY: clean clean: $(RM) *~ *.o client OBJECTS=client.o client: $(OBJECTS) $(CC) $(CFLAGS) $(OBJECTS) -o client $(LDFLAGS) In the line defining the client target change … Read more
I had it on the Makefile MAPS+=reverse/db.901:550:2001.ip6.arpa lastserial: ${MAPS} ./updateser ${MAPS} It’s because of the : in the file name. I solved this with ——– notice / / v v MAPS+=reverse/db.901\:550\:2001.ip6.arpa lastserial: ${MAPS} ./updateser ${MAPS}
Under Bash (at least), this can be done automatically with tab completion: make spacetabtab
make clean removes any intermediate or output files from your source / build tree. However, it only affects the source / build tree; it does not touch the rest of the filesystem and so will not remove previously installed software. If you’re lucky, running make uninstall will work. It’s up to the library’s authors to … Read more