Sent from my iPhone
On Nov 24, 2012, at 1:00 PM, Roy Stogner wrote:
> For comparison's sake, "what we had previously" was a state in which
> every few months I'd have to manually wipe and rebuild contrib/
> because our Makefiles got confused by a compiler change, and every
> few years I'd have t
On Sat, 24 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote:
$ ./configure METHODS="opt dbg devel"
and have it create a subdirectory for each, the only catch then is a
$ make
will *always* recurse into each. In fact, I can add that alongside
what is already there - but letting METHODS trump METHO
On Nov 24, 2012, at 9:49 AM, Vikram Garg wrote:
> Just think a separate document might make things clearer for users. Once they
> get comfortable with libMesh up and running, they can start exploring the new
> options.
Fully agree. I just want to get some group consensus on how we think our
Might be good if we have one page document with the release notes on the
new build system ? It can include the simplest, most straightforward way of
getting libMesh up and running as before. And then it can also include the
newer features of the system and how they can be useful.
Just think a sepa
On Nov 21, 2012, at 8:07 PM, Paul T. Bauman wrote:
> The only difference between this and the former build system is the extra
> cd's (minor annoyance) and make install (nice new feature, IMHO, that was not
> present in the previous build system).
>
>> Then I go make a change to libMesh and n
