On Mon, Feb 28, 2011 at 3:47 PM, Vijay S. Mahadevan <[email protected]> wrote: > Hi all, > > While using libMesh configured with Petsc using both debug and > optimized versions (by means of different PETSC_ARCH variables), will > it not be easier to take the PETSC_DIR and PETSC_ARCH information from > the environment configuration of the shell directly instead of > hard-coding this in Make.common ? I ask because I had to switch from > debugging enabled Petsc to the optimized version for timing studies > and it took me couple of hours before I realized that the environment > setting did not matter at all.
Hi Vijay, I confess that even with dbg builds of libmesh, I use the optimized PETSc libraries... therefore the PETSC_ARCH and PETSC_DIR that gets set at configure time is truly constant in my builds. One reason for this is that even optimized PETSc builds have some debugging information available in them... Another is that dbg petsc builds can run significantly slower, and you aren't really debugging petsc after all (I hope) but the inputs to it from libmesh. > Is this the standard behavior of the configuration script ? If so, how > do you deal with switching say the Petsc, Slepc builds ? Also, does it > make sense to comment out these two lines and let "make" get these > from the shell directly ? I did this manually and it worked but I feel > like I am doing something that was not intended. > > If you have suggestions on the best way to have this flexibility, I > would love to hear it. I would suggest maintaining 2 separate builds of libmesh: 1.) libmesh opt+dbg linking against optimized PETSc 2.) libmesh opt+dbg linking against debug PETSc If you are doing development in the optimized PETSc directory and want to try the changes with a debug PETSc, I'd use rsync to locally keep the sources and headers in sync. -- John ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
