On Sun, 13 Mar 2011, Roy Stogner wrote: > We'd like to support that configuration (or any similar > name conflicts) eventually, but IIRC nobody wanted to go through the > trouble of making it work until it was actually needed...
No, wait: nobody wanted to go through the trouble of making it *easy* until it was actually needed. But you can compile after adding -DLIBMESH_REQUIRE_SEPARATE_NAMESPACE to your CPPFLAGS and the result should build with PETSc-with-sieve. You might want to add --with-shared to your PETSc configure options, and you will need to manually handle the namespaces in your user code rather than relying on the "using namespace libMesh;" that would otherwise have been on by default. --- Roy ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
