On Mon, 26 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > One thing I'm waffling on is adding a -opt suffix to the > executables. I think I might, and then symlink e.g. > > meshtool -> meshtool-opt > > upon installation.
I like this idea. > Also, potentially the most controversial issue is the contrib stuff. > Because of the aforementioned hassle of creating three rules for > everything, what I have done is set up a single libcontrib.la that > only gets compiled *once* - with optimized flags - and then included > with all three libMesh flavors. If we need debugging information in > there it would be straightforward to do that as needed with > something like > > $ ./configure libmesh_CXXFLAGS="-g" > > and that will do the trick. Alternatively I could set up rules to > compile multiple flavors of everything in contrib too, but I'm not > sure its warranted. It might be. I've seen a few cases where we've triggered bugs in contrib/ libraries, and plenty of cases where bugs in libMesh have manifested as segfaults in contrib/ libraries. Unless we *really* turn up the sanity checking on our interfaces it's going to be useful to have debug/devel-mode libMesh always link to debug/devel mode contrib stuff. If the hassle of multiple targets is just too annoying, maybe direct support in configure isn't the way to go? If I'd just been doing this for myself I'd have simply set up a buildall.sh with something like: for m in $METHODS mkdir $m (cd $m && METHOD=m ../configure $*) end (this is what I had assumed your buildall.sh would be, until I looked inside to find 50 lines of benkirk-specific install_dir, hardcoded compiler names, etc...) ;-) --- Roy ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel