Yeah Derek, I'm in winter park this weekend.
Of course, if you get sufficiently frustrated it'd be easy to put moose under
autotools and just use libmesh as a subpackage, just like we do now with
netcdf... ;-)
Also, what doesn't work today with in-tree builds, for the default netcdf?
The only thing I can think of is contrib/netcdf/Lib may now be
contrib/netcdf/v3, but that's it...
-Ben
On Feb 9, 2013, at 11:45 AM, "Jed Brown" <j...@59a2.org<mailto:j...@59a2.org>>
wrote:
On Sat, Feb 9, 2013 at 11:12 AM, Derek Gaston
<fried...@gmail.com<mailto:fried...@gmail.com>> wrote:
On Feb 8, 2013, at 11:52 PM, Jed Brown <j...@59a2.org<mailto:j...@59a2.org>>
wrote:
> So what do you folks do when you're hacking on both libmesh and moose? Do you
> 'make install' libmesh after every change?
Yes, currently (because of the exodus stuff but that will change).
But before that I was doing in-tree builds when hacking on both.
I've been just using a script that does "make install" for me...
If you include the fact that I can't just build opt or debug
individually
Use a different build directory for debug and opt.
and the make install time... my build and test cycle is
probably 5x longer with libMesh now than before autotools...
Doesn't the 'make install' also overwrite all the headers, implying that all of
moose will also rebuild even if the change in libmesh was restricted to a *.C
file (thus requiring at most re-linking)? Gosh, that doesn't sound fun.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
