On Sat, 19 Jan 2013, Jed Brown wrote: > This doesn't add to the discussion,
Productive complaints are always helpful. > but I've never been able to stand automake's desire to put binaries > in .libs, to be run via a shell script that mucks with the > environment. That's a libtool thing. You can use automake without libtool, but I'm glad we didn't - libtool got us working again on Cygwin. > Naturally, the first thing I want to do is use a debugger or > valgrind and it feels weird to be manually futzing with the > environment and running programs from .libs/. Let libtool do the futzing/running: "libtool --mode=execute gdb progname" or "libtool --mode=execute valgrind progname" Or for our examples setup, I typically just assume I'll be steadily debugging, and I set: "export LIBMESH_RUN='libtool --mode=execute gdb --args'" --- Roy ------------------------------------------------------------------------------ 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-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
