From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] Add INSTALL file Date: Tue, 21 Oct 2014 11:17:46 +0100 Message-ID: <544632CA.2070702@citrix.com> References: <1413557458-20322-1-git-send-email-olaf@aepfle.de> <5444D19C.3000803@citrix.com> <20141021100145.GB24647@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141021100145.GB24647@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 21/10/14 11:01, Olaf Hering wrote: > On Mon, Oct 20, Andrew Cooper wrote: > >> On 17/10/14 15:50, Olaf Hering wrote: >>> +Variables recognized by make >>> +========================== >> What about some reference to .config in the top level? It is what I use >> for providing most of these parameters in a XenServer build. > Like this? > > In addition to pass variables as make options it is also supported to > create a ".config" file in the toplevel directory. The file will be > sourced by make(1). It should contain the variables in the form > "variable := value". The usage of ":=" is prefered to override earlier > assignments to that variable by make(1). > > > Olaf Thats ok, although I am not sure a description of ":=" is strictly needed - we are not teaching people to use make(1). I think "will be sourced by make(1)" is sufficient to describe that it is a makefile snippet. ~Andrew