* Werner Koch <[email protected]> [120927 14:11]:
> On Wed, 26 Sep 2012 20:58, [email protected] said:
>
> > file, but is it a good practice to have an installed header file whose
> > content varies from an architecture to another?
>
> Yes, that is imho fine and much easier to maintain than fragile
> #ifdefs. Some libraries install a generic file and one system specific -
> which is a similar approach.
#ifdefs might be fragile, but non-generic header files are quite
fragile, too, and can have ugly side-effects with cross-compiling
and other cases. As long as there is a specific case like working
around some very unusual environment, just checking for that with
an ifdef can be quite a robust solution.
Bernhard R. Link
