Commit 77b72cad authored by Federico Vaga's avatar Federico Vaga

tools: include specific Makefile

Sometimes (expecially in cross-compilation context) t is necessary to use
different environments. Instead of complicate this makefile, include
an external one with user code.

Create a local file named Makefile.specific, and write here your code.
Bear in mind that Makefile.specific will run before the Makefile.
Signed-off-by: Federico Vaga's avatarFederico Vaga <federico.vaga@cern.ch>
parent bf8c29c3
libfmctdc.a
.depend
\ No newline at end of file
.depend
Makefile.specific
\ No newline at end of file
# This is not a kbuild Makefile. It is a plain Makefile so it can be copied
# If it exists includes Makefile.specific. In this Makefile, you should put
# specific Makefile code that you want to run before this. For example,
# build a particular environment.
-include Makefile.specific
#ZIO := $(shell ../scripts/check-submodule zio $(ZIO))
ZIO ?= ../zio
......
......@@ -4,3 +4,4 @@ fmc-tdc-read
fmc-tdc-temperature
fmc-tdc-term
fmc-tdc-time
Makefile.specific
\ No newline at end of file
# If it exists includes Makefile.specific. In this Makefile, you should put
# specific Makefile code that you want to run before this. For example,
# build a particular environment.
-include Makefile.specific
DESTDIR ?= /usr/local/
LIBTDC = ../lib/
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment