Also: let me bring up one more huge inefficiency that our users deal with:
METHODS.
Currently METHODS has to be set at configure time - and there is no way to
configure for all the METHODS you want and then only compile a particular
METHOD. This kills new MOOSE users because we want them to be able to run
both opt and dbg... and the only way to to do that is to force them to
compile libMesh twice (which can take a very long time).
That wasn't true in the pre-Automake days - and I wish it weren't true
now. It's definitely something I would change with the new build system.
Derek
On Thu, Aug 30, 2018 at 3:52 PM Roy Stogner <royst...@ices.utexas.edu>
wrote:
>
>
> On Thu, 30 Aug 2018, Derek Gaston wrote:
>
> > However, it's obvious that you're both passionate about these... so
> > I will relent and agree that whatever build system we come up with
> > has to have these features. Fine.
>
> Thanks.
>
> > Can you agree with me that the current build system adds friction
> > for everyone that doesn't use these features?
>
> Yup. I think adding new files is the worst-case scenario, but there's
> flaws (actually, "friction" is the perfect word) in every case.
>
> > I think you guys are so used to how slow and laborious it is that
> > you don't even realize how much better it could be.
>
> No, I remember pre-automake libMesh too, and it was certainly better
> in some ways, just much worse in some others. I still think the move
> to automake was an improvement but we're definitely not at an optimum.
> ---
> Roy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
