From: Lorenzo Z. <za...@ai...> - 2013-08-13 15:24:52
|
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" What's the right way to link then? Thanks Lorenzo On Aug 13, 2013, at 1:28 PM, Lorenzo Zanon wrote: > Hi, > > I re-installed libmesh as you indicated. I didn't use --with-methods="opt" in the configuration though, since I usually run my own code in dbg mode, so I configured with all three methods. > > Now, for running my code, should I copy the Make.common file in ${LIBMESH_ROOT}/installed in my code directory? > > Thanks > Lorenzo > > On Aug 12, 2013, at 6:03 PM, John Peterson wrote: > >> >> >> >> On Mon, Aug 12, 2013 at 9:57 AM, Lorenzo Zanon <za...@ai...> wrote: >> Hello, >> >> To be more specific, my code now is based on libmesh version 0.7.3. I would like to run it with the newest version. >> >> What I tried to do is to copy the Make.common file from libmesh/contrib/ to /libmesh (folder where the new version is), then type into the shell: >> >> Libmesh now uses automake as its build system, so you build libmesh a little bit differently than before. In particular, it's best to build in a separate "build" directory and to use the provided 'make install' target. Then Make.common will be found in your installation dir, and your existing app can use it more or less as it did before. >> >> Here's a simple set of steps to do the build, let us know when you have that working: >> >> (from the directory where you checked out libmesh, call it $LIBMESH_ROOT) >> mkdir build >> mkdir installed >> cd build >> ../configure --with-methods="opt" \ >> --prefix=${LIBMESH_ROOT}/installed >> >> make install >> >> >> >> -- >> John > |