Skip to content

F
FMC ADC 100M 14b 4cha - Software
Commit b03570b3 authored by Federico Vaga's avatar Federico Vaga
Browse files
Options

Makefile: 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 034242ae
Hide whitespace changes
Inline Side-by-side
Showing with 17 additions and 0 deletions
.gitignore
View file @ b03570b3
......@@ -14,6 +14,7 @@
*.a
\#*\#
*.sh
Makefile.specific
# eclipse files
.pydevproject
.cproject
......
lib/Makefile
View file @ b03570b3
# 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 ?= ../zio
LIB = libfmcadc.a
......
libtools/Makefile
View file @ b03570b3
# 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
LIBADC = ../lib/
......
tools/Makefile
View file @ b03570b3
# 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
# user-space tools for spec-fine-delay
M = $(shell /bin/pwd)/../kernel
DESTDIR ?= /usr/local
......
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