> I have a Petsc 2.3.3-p15 build and a Petsc 3.0.0-p2 build configured > and installed. Is there an easy way to configure libmesh to use either > of the builds rather than compiling two different versions of libmesh > side by side and maintaining this separately. Also I understand that > the directory structure is a little different between these two > versions of petsc and so does this affect the configuration in any way > ?
Not only is the directory structure different between builds (which will effect include paths, link lines, etc...), but the API is different as well. If the API was the same it would be as simple as switching the PETSc dynamic libraries loaded at runtime. Unfortunately the way libMesh deals with the changing API is through CPP macros, hence you effectively need to recompile all PETSc related code when switching PETSc versions. So there is not a convenient way to support multiple PETSc's with one libMesh build. Sorry. -Ben ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
