RE: [Libmesh-devel] libmesh_config.h

[KIRK, B. (JSC-E. (NASA) <ben...@na...>]

I think autoheader would break, but we can handle that manually.  We would
need to create the include files manually and use the standard autoconf
@REPLACE@ syntax to create foo.h from foo.h.in

-Ben




-----Original Message-----
From: lib...@li...
[mailto:lib...@li...] On Behalf Of John
Peterson
Sent: Monday, May 09, 2005 9:25 AM
To: lib...@li...
Subject: [Libmesh-devel] libmesh_config.h



Hi,

It occurs to me that the libmesh_config.h file is a
huge bottleneck for compilation.

For example, if I have a working copy of LibMesh and do ./configure
--disable-triangle (or any other contributed
package) this effectively changes the libmesh_config.h
file and forces a recompile of every source that includes
that header (which is a lot).

Some additional granularity should help here (at the cost
of some complexity.)  One basic break-down I can think of is
to use the current directory structure to define multiple
libmesh_foo_config.h files.  For example

libmesh_mesh_config.h
libmesh_fe_config.h
libmesh_contrib_config.h

You can apparently have multiple AC_CONFIG_FILES commands, but I'm not sure
about AC_CONFIG_HEADER.  Anyway if a ton of files change in the near future,
that's what it is :)


-John


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win
an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Libmesh-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libmesh-devel