From owner-freebsd-ports@FreeBSD.ORG Wed Sep 26 12:22:09 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96263106566B for ; Wed, 26 Sep 2012 12:22:09 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id F0F728FC0A for ; Wed, 26 Sep 2012 12:22:08 +0000 (UTC) Received: from rufus.webfusion.com (mail.heartinternet.co.uk [79.170.40.31]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q8QCLmrZ014555 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Sep 2012 13:21:49 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q8QCLmrZ014555 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1348662109; bh=VeaPKUAGXvXvc5TH1D5VtCzATVv6iSbqJnN3k4b/IBo=; h=Date:From:To:CC:Subject:References:In-Reply-To:Content-Type: Message-ID:Mime-Version; b=noimTseJ8AO2syKrOB88BKGV4ioSEMj9Cx1pcQXQe0cnxA9ISLXjUXQCs/E6wuE0P 8j2fBzUnaBj/pQTtZIDICob5s9vdPc/cDXUSJRAmMVNSZJLfh+mxh1pk45Akypv87X nGjjyo2ax6+35bX6oXADbAnj7kDKDxAXxLMZo/Gw= X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host mail.heartinternet.co.uk [79.170.40.31] claimed to be rufus.webfusion.com Message-ID: <5062F35C.6050607@infracaninophile.co.uk> Date: Wed, 26 Sep 2012 13:21:48 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: mexas@bristol.ac.uk References: <201209261206.q8QC6Umb072888@mech-cluster241.men.bris.ac.uk> In-Reply-To: <201209261206.q8QC6Umb072888@mech-cluster241.men.bris.ac.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.6 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_ALL, DKIM_SIGNED,SPF_FAIL,T_DKIM_INVALID autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-ports@freebsd.org Subject: Re: do I need to specify explicity what to install for make install to work? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2012 12:22:09 -0000 On 26/09/2012 13:06, Anton Shterenlikht wrote: > I was updating my port until I got to > > make: don't know how to make install. Stop > *** [do-install] Error code 2 > > and I realised that I don't really understand > the sequence of commands involved in "make install". > I've looked through the porter's handbook, > but still not clear. > > I see lots of post-install targets in > Makefiles, but never just "install". > I presume it should be pulled into by > .include > > Still, if I have a set of source files, > generated object files, and just one > executable I want to install, I probably > have to specify somewhere in the Makefile > the name of this executable, right? > > Or are PLIST_FILES and PLIST_DIRS used > to let make know what to install? The ports 'make install' generally does one of two things: either it runs appropriate make install commands from $WRKDIR -- ie. what the ported software provides itself -- or it has a list of files, directories etc. from within $WRKDIR which it copies into place itself, which is usually only done if the ported software doesn't provide its own installation routines. As I recall, if you don't provide an explicit install target yourself, the default is to run 'make install' from $WRKDIR. PLIST_FILES, PLIST_DOCS or the pkg-plist file don't tell the ports what to install. Instead, they document what the installation process should be installing, and so what files to include in a pkg tarball and what to delete at pkg deinstallation time. Hence the effort required to make sure your plist is accurate. Cheers, Matthew