[Trilinos-Users] -DHAVE_CONFIG_H

[James Willenbring]

Dave,

This is certainly an issue that we could take a look at again.  Historically
the reason we couldn't remove this define was that some headers are
processed during the configure stage.  At least some instances of that
problem have gone away, I don't know if all have gone away.  Having an empty
file could possibly provide a work-around, but I would want to have the team
think that over a little bit before we go ahead with it.

The Bugzilla bug associated with this issue is #195.

Jim

-----Original Message-----
From: trilinos-users-bounces at software.sandia.gov
[mailto:trilinos-users-bounces at software.sandia.gov] On Behalf Of David M.
Gay
Sent: Wednesday, June 06, 2007 4:01 PM
To: trilinos-users at software.sandia.gov
Subject: [Trilinos-Users] -DHAVE_CONFIG_H

What harm would come if HAVE_CONFIG_H were assumed
always to be #defined (and conditional #includes
protected by #ifdef HAVE_CONFIG_H were made unconditional)?
One could always supply empty config.h files if need be.

-- Dave
_______________________________________________
Trilinos-Users mailing list
Trilinos-Users at software.sandia.gov
http://software.sandia.gov/mailman/listinfo/trilinos-users