From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 07:43:59 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBF1E106564A for ; Fri, 22 Apr 2011 07:43:58 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 660C18FC18 for ; Fri, 22 Apr 2011 07:43:57 +0000 (UTC) Received: by bwz12 with SMTP id 12so513212bwz.13 for ; Fri, 22 Apr 2011 00:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=BJXxjyPd+I8B8ux2ISBKtEZWA/WS8fp7/kEsGKDb5hU=; b=FwtC4NByp0YtWunxWczHoprKFQ1L8ly+d4qflTNHhZnvxf6r5LpWEt3PuftAOzJszF tnu32VV6AYq6RsdbUN1fWRmU83UwExcssUPmOjtdNbDeqHoxt+/nUCItOcT62C6nBTG0 orYcfLMMAI0gaJTmGA39/Fqff4+yEYLT1Qhss= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=qGBpoQsaMzLxvliUm4vzk03HyoqTXE2jfk5yLfD0xbS54FmXzmu7WdKO/5FvOurTpN 1qz1bH2spc+4GaPzLPp/3G3r2LmDRS1m+BYfKa05IoNVZymXEEr/YTffUwFKce2tywDB EEBCVTZIAmb5W8VwHGTbh8iKNrpnWBflO98+c= Received: by 10.204.81.203 with SMTP id y11mr716235bkk.124.1303458237090; Fri, 22 Apr 2011 00:43:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.42.21 with HTTP; Fri, 22 Apr 2011 00:43:27 -0700 (PDT) In-Reply-To: <4DB1297E.6090205@telus.net> References: <4DB0F34B.9030008@telus.net> <4DB1297E.6090205@telus.net> From: Chris Rees Date: Fri, 22 Apr 2011 08:43:27 +0100 Message-ID: To: Carl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd@edvax.de, freebsd-questions@freebsd.org Subject: Re: building a port with very long list of build options X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2011 07:43:59 -0000 On 22 April 2011 08:08, Carl wrote: > On 2011-04-21 8:52 PM, Polytropon wrote: >> >> This has been possible and common in the past. For example, >> the many options for the mplayer and mencoder ports could >> be specified in a file, so changing of a port's file was >> not needed. I'm not fully sure this option is still present, >> but at least on v7 it worked. >> >> Create a file Makefile.local in the port's directory and >> specify all your options as desired. This file will be >> sourced when you issue a "make" command and will override >> settings of the regular Makefile (e. g. if you want >> different CFLAGS for _this_ port). The file is to be in >> the known syntax, NAME=3Dvalue. > > Does that solution allow for locating Makefile.local outside the ports tr= ee > so as not to contaminate builds for other targets using the same ports tr= ee? > > On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: >> >> If you read the make manual page , you will see the following option : >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 ... >> >> =A0 =A0 =A0*-f* *makefile* >> =A0 =A0 =A0 =A0 =A0 =A0 Specify a makefile to read instead of the defaul= t one. >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0... >> >> =A0which is used as >> >> make -f your_own_make_file_name >> >> This form will override the Makefile present in the current directory >> and will use the specified make file with name your_own_make_file_name . > > Yes, I did see that, but I interpreted that to mean my make file *replace= s* > the original, in which case I would need to populate my make file not onl= y > with the list of build options I want but also a copy of everything in th= e > original make file. If I'm correct, that doesn't seem to me to be a good > idea from a maintenance perspective. I was hoping for something like the = -f > option that somehow inserted rather than replaced. > Or, at the bottom of your Makefile defining variables (including BATCH=3D yes to skip the OPTIONS dialog), stick the line: .include "Makefile" and use make -f _my_Makefile Chris