From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 08:02:44 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 069DA106566C for ; Fri, 22 Apr 2011 08:02:44 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id AE8428FC1A for ; Fri, 22 Apr 2011 08:02:43 +0000 (UTC) Received: by qwc9 with SMTP id 9so238833qwc.13 for ; Fri, 22 Apr 2011 01:02:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=aHUwWc4Esc8DlwgzwJ0wZxchPO8BMcqEHk37Ux5pi4c=; b=VPAMuBD493iJoOVIWV383tjGTPkfux5U8ROHVKKbDjelI6QkN3Hl//6XzW1uK4iRuV GDgWnGwc9hqusIP0mvx65LORvunYQa2oYan7ybDqJupImt5EQeZuxqn4kW3iGT9d+62F oX8EIbgbUNJ3j/vkK8M0d76/BLQP/wmapNF/c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=oocBp1tmSEAIoYz+o8+K6BgXacqBznQLCKhMrnT8mFK5ZrB2fYYfKCQMegtQHD1HJN QHq3xbTQvicDsPjdAwN/FQfCioiDtVgj7kwToNTJb1nCb7TBJ8bG0Q3ssXjZ9OElI0ib u47IfPHyD1xQBDAPNZKJOuxC1z1ieAtBecjFQ= MIME-Version: 1.0 Received: by 10.224.76.84 with SMTP id b20mr623987qak.161.1303459362705; Fri, 22 Apr 2011 01:02:42 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Fri, 22 Apr 2011 01:02:42 -0700 (PDT) In-Reply-To: <4DB1297E.6090205@telus.net> References: <4DB0F34B.9030008@telus.net> <4DB1297E.6090205@telus.net> Date: Fri, 22 Apr 2011 04:02:42 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Carl Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2011 08:02:44 -0000 On Fri, Apr 22, 2011 at 3:08 AM, 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=value. >> > > Does that solution allow for locating Makefile.local outside the ports tree > so as not to contaminate builds for other targets using the same ports tree? > > On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: > >> If you read the make manual page , you will see the following option : >> >> ... >> >> *-f* *makefile* >> Specify a makefile to read instead of the default one. >> >> ... >> >> which 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 *replaces* > the original, in which case I would need to populate my make file not only > with the list of build options I want but also a copy of everything in the > 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. > > Carl / K0802647 > Please study make manual page in detail . There are many more commands to be applicable , for example ( .include ) which you may use to include the original make file name Makefile at any suitable point in your own make file . Also studying the currently used Makefile files in FreeBSD may give many ideas to apply . Thank you very much . Mehmet Erol Sanliturk