From 94c4250d9f7ca57d9af7a7265fcdec0b4e94e5b3 Mon Sep 17 00:00:00 2001
From: Chris Want <cwant@ualberta.ca>
Date: Sat, 24 May 2003 17:22:18 +0000
Subject: [PATCH] Use of a (not included in cvs) file called user-def.mk to
 override the build variables ... basically a way to override the build
 defaults with less risk of a cvs conflict.

---
 Makefile | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index cae7a9ce859..71f49a7aad9 100644
--- a/Makefile
+++ b/Makefile
@@ -31,11 +31,17 @@
 # Toplevel Makefile for blender. Bounces make to subdirectories.
 # Available targets: 'all' 'debug' 'release'
 
+# If the user wants to override some of the build
+# vars they can put it in the file user-def.mk which
+# will get included if it exists (please do not commit
+# user-def.mk to cvs).
+sinclude user-def.mk
+
 export NANBLENDERHOME=$(shell pwd)
 MAKEFLAGS=-I$(NANBLENDERHOME)/source --no-print-directory
 
 SOURCEDIR = blender
-DIRS = extern intern source po
+DIRS ?= extern intern source po
 include source/nan_subdirs.mk
 
 .PHONY: release