From owner-freebsd-hackers Wed Dec 4 13:59:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.8.3/8.7.3) id NAA18094 for hackers-outgoing; Wed, 4 Dec 1996 13:59:23 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA18089 for ; Wed, 4 Dec 1996 13:59:18 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id PAA19735 for ; Wed, 4 Dec 1996 15:32:23 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA24876; Wed, 4 Dec 1996 21:57:51 GMT Message-Id: <199612042157.VAA24876@right.PCS> Date: Wed, 4 Dec 1996 15:57:50 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: hackers@freebsd.org Subject: Exporting environment vars from make? X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a couple of tools that change their behavior depending on the setting of various environment variables, and would like to place the makefiles in control of these tools. However, there doesn't seem to be any way to export arbitrary variables from a makefile, short of putting an 'export' line in every command, which seems kind of klunky. (Putting .MAKEFLAGS in the makefile doesn't count - it doesn't allow overrides from the command line) Is there any reason why there isn't an .EXPORT: directive in bmake, to allow exporting arbitrary variables? -- Jonathan