hard-coded paths

[William Kirkland]

It would be a kludge, but if you were to hard code the path to the
current directory, an alias or wrapper script could eaisly ensure
consistant results upon execution.

	PATH="./lib/configfile"

	alias application="cd /usr/local/application-home; ./application"

On Sun, Apr 11, 2004 at 10:58:31AM -0400, Chuck Swiger wrote:
> 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.
> Constantine wrote: