>> And use `#include <your-package-name/config.h>' in all other
>> headers that include it.
Ossama> BTW, I do exactly what Alexandre suggests in some of my
Ossama> own packages. It works out quite nicely.
But be careful: if any of the C code in the package itself includes
<your-package-name/config.h> you might be in for a nasty surprise: if
a version is already installed and a user is compiling a new version
from source, that user will pick up the installed .h files which will
not be consistent with the source. I've seen this happen.
- How to install "config.h" Robert Boehne
- Re: How to install "config.h" Ossama Othman
- Re: How to install "config.h" Simon Richter
- Re: How to install "config.h" Alexandre Oliva
- Re: How to install "config.h" Ossama Othman
- Re: How to install "config.h" Robert Boehne
- Re: How to install "config.h" Mark Galassi
- Re: How to install "config.h" Simon Richter
- Re: How to install "config.h&q... Ossama Othman
- Re: How to install "config.h&q... Raja R Harinath
- Re: How to install "config.h" Gary V. Vaughan
- Re: How to install "config.h" Ossama Othman
- Re: How to install "config.h&q... Raja R Harinath
- Re: How to install "config... Ossama Othman
- Re: How to install "config.h&q... Assar Westerlund
- Re: How to install "config... Ossama Othman
- Re: How to install "co... Bob Friesenhahn
