Re: CPPFLAGS and config.h needed by dependent projects?

[Nate Bargmann]

* On 2013 31 Jul 08:03 -0500, LRN wrote:
> On 31.07.2013 16:17, Daniel Pocock wrote:

> > Should we be distributing a config script, e.g. bin/xxx-config that can
> > emit CPPFLAGS?
> Either that, or distribute a .pc file for pkg-config (and appropriate
> .m4 for dependent projects to use, if you don't have these already).

I'll concur as the Hamlib project only installs the public headers, none
of which depend on config.h, and a hamlib.pc and hamlib.m4 file.  I have
yet to receive a request from any of our consumers to know what *FLAGS
were used.  To be clear, the only binaries the project provide are for
Windows and the free OS distributions build their own binaries.

As I understand it, config.h is a snapshot of the build system at
configure time.  After a few upgrades of the build system it may well be
out of date and require a configure run to update it.  We've tried to
adhere to a policy that the public API should not depend on a localized
configuration.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us