On Tue, 13 Aug 2013, John Peterson wrote:
> On Tue, Aug 13, 2013 at 9:24 AM, Lorenzo Zanon > <[email protected]>wrote: > >> Actually in the Makefile "old version" the path to Make.common is >> LIBMESH_DIR/Make.common, so I set LIBMESH_DIR=LIBMESH_ROOT/installed then >> typed "make" from my example's directory. The Make.common file is found but >> there's still something wrong, since I'm getting a compile error: >> >> ex23aa.C(29): catastrophic error: cannot open source file "libmesh.h" >> > > The header files have moved. So you need to prepend libmesh to all your > headers, > > #include "libmesh/libmesh.h" > > for example. We also have a "--enable-legacy-include-paths" configure option that should make headers visible in both old and new paths. Also, if this change is affecting your code you might also need (in the short term) to configure with --enable-legacy-using-namespace; otherwise you'll need to make sure all your code either uses namespace-qualified identifiers (e.g. "libMesh::Elem" instead of just "Elem") or has its own "using declarations" to pull the identifiers it needs into the current namespace. In the long term, "libmesh/point.h" is better than "point.h" and "libMesh::Point" is better than "Point" at avoiding naming conflicts with other third party libraries, so you should try to update application codes accordingly, but we've tried to make the transition a little less painful. --- Roy ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
