Use of a (not included in cvs) file called user-def.mk to override the
authorChris Want <cwant@ualberta.ca>
Sat, 24 May 2003 17:22:18 +0000 (17:22 +0000)
committerChris Want <cwant@ualberta.ca>
Sat, 24 May 2003 17:22:18 +0000 (17:22 +0000)
build variables ... basically a way to override the build
defaults with less risk of a cvs conflict.

Makefile

index cae7a9ce859d1401a7ddf6a8a23db9cceb16a316..71f49a7aad9c607f08018b6a8b3e123537384b2a 100644 (file)
--- a/Makefile
+++ b/Makefile
 # 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