On Feb 2, 2013, at 1:44 PM, David Knezevic <[email protected]> wrote:
> > On 02/02/2013 02:39 PM, Paul T. Bauman wrote: >> >> You only need 1 copy of the source. libMesh supports VPATH (AKA >> out-of-source) builds so you can have a pristine source. From external >> build directories, you can configure, make, make install. So, you >> could have a libmesh-real-build and libmesh-complex-build. Any changes >> to the source will be automatically picked up and you should just be >> able to type make in each of the build directories. The only exception >> is, I believe, if configure.ac <http://configure.ac> or one of the .m4 >> files change, then you'll need to rebootstrap. > > OK, cool. So I just call configure from the libmesh-real-build directory > and from the libmesh-complex-build directory, and everything should go > through fine? > Absolutely. See the documentation here https://github.com/libMesh/libmesh (towards the bottom) for supporting multiple compilers - the same mechanism can be used for the same compiler with different options. The only caveat is you can't be do in-tree and out-of-tree builds at the same time - it is one or the other. So if you have been doing in-tree builds, you'll get scolded and told you need to do a 'make distclean' in the source directory first. -Ben ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
