Re: development work flow

[Russ Allbery]

Bob Friesenhahn <address@hidden> writes:

> In traditional Unix, programs get installed under a specified prefix
> (e.g. /usr/local) and if the program needs additional data files
> (e.g. under /usr/local/share/appname), then the full path to the directory
> containing these files is cached in a config.h file.

Because of the requirements for expansion of shell variables, usually it's
best to not put paths into config.h.  Instead, passing them on the
compiler command line is usually easier.

See info autoconf FAQ 'Defining Directories'

-- 
Russ Allbery (address@hidden)             <http://www.eyrie.org/~eagle/>