From owner-freebsd-ports@FreeBSD.ORG Sun Apr 11 07:59:02 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6824916A4CE for ; Sun, 11 Apr 2004 07:59:02 -0700 (PDT) Received: from out004.verizon.net (out004pub.verizon.net [206.46.170.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0554F43D31 for ; Sun, 11 Apr 2004 07:59:02 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([68.160.247.127]) by out004.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040411145901.TTCB3003.out004.verizon.net@mac.com>; Sun, 11 Apr 2004 09:59:01 -0500 Message-ID: <40795D17.20507@mac.com> Date: Sun, 11 Apr 2004 10:58:31 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Constantine , FreeBSD ports References: <40778608.3040505@rbcmail.ru> In-Reply-To: <40778608.3040505@rbcmail.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [68.160.247.127] at Sun, 11 Apr 2004 09:59:01 -0500 Subject: Re: hard-coded paths X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2004 14:59:02 -0000 Constantine wrote: > I am porting an application that has hard-coded paths for the message > files. They are defined in the Makefile, but still they are hardcoded in > the programme. Is there a way to go around this problem? As it is, the > port will not work on systems with installations different from the one > of compile time. Pre-built packages effectively have hard-coded paths in them regardless, so you may be making more of this issue than you need to. If the Makefile is generated via the common ./configure process, the ports Makefile ought to pass in an appropriate installation prefix if the user has changed it from the default of /usr/local. If the program does something different, use REINPLACE_CMD to update the hardcoded paths in place to whatever $LOCALBASE is set to. [ Perhaps you ought to set "NO_PACKAGE", too. ] -- -Chuck