Commit fac95f96 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 f1c5325f
......@@ -4,3 +4,4 @@
*.so
*.pyc
.*.cmd
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
LINUX ?= /lib/modules/$(shell uname -r)/build
......
# 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
CFLAGS = -Wall -ggdb -O2 -I../kernel/include $(EXTRACFLAGS)
PROGS = fru-dump fmc-mem
......
# 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
OBJ=ipmi.o
OUT=libipmi.a
OUT_SO=libipmi.so
......
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