2008/5/30, Dan Fandrich wrote:

> Agreed--I can envision a user's poorly-configured build system
> picking up curl's config.h instead of the app's correct one.

Indeed.

2008/5/30, Daniel Stenberg wrote:

> How about just build.h ? We're already using our own subdir so it would be
> curl/build.h anyway...

For the very same reason that Dan mentions I prefer a 'curl' prefixed
name that makes the file name unique from other software's potential
build.h

I was also thinking of curldefs.h but I have the feeling that it
'invites' to make changes to it.

I'd rather find a name that transmitted the idea that whatever is in
there is decided by libcurl's build/configuration process and that
neither the user nor the library builder is allowed to change or
further adjust it. I suppose that in the end its better to just make
another note in the inside.

How about curlrules.h with an intentional double meaning ?

-- 
-=[Yang]=-