Date: Sun, 11 Apr 2004 10:58:31 -0400 From: Chuck Swiger <cswiger@mac.com> To: Constantine <cnst@rbcmail.ru>, FreeBSD ports <ports@FreeBSD.org> Subject: Re: hard-coded paths Message-ID: <40795D17.20507@mac.com> In-Reply-To: <40778608.3040505@rbcmail.ru> References: <40778608.3040505@rbcmail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40795D17.20507>