>> Will be easy, but I bet those are not most of the ones which conflict? More >> difficult will be, for example, HAVE_STDLIB_H, which comes indirectly when >> configure looks for <stdlib.h>. Similarly, SIZEOF_INT etc... ? > > I have vague memories of talking about this problem (with John?) at some > point and deciding the solution should be simple: at the end of > libmesh_config.h, each offending entry gets: > > #define LIBMESH_WHATEVER WHATEVER > #undef WHATEVER
For our favorite example, wouldn't that turn into #define HAVE_MPI #undef HAVE_MPI Inside the same file, which is no good for anything outside that file for using the definition? For that to work I think we would need something like #include "libmesh_config.h" ... #include "libmesh_undefs.h" #include "some_other_config.h" #include "libmesh_config.h" ... And then we would need to remove the #ifndef __libmesh_config_h__ #define __libmesh_config_h__ ... include guards from the file. I'll see how far I can get renaming things. -Ben ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
