cswiger at mac.com
Sun Apr 11 07:59:02 PDT 2004
> 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. ]
More information about the freebsd-ports