On Thu, Aug 30, 2018 at 5:07 PM Roy Stogner <royst...@ices.utexas.edu>
wrote:
>
> On Thu, 30 Aug 2018, Paul T. Bauman wrote:
>
> > I would love to see how it could be sped up. The vast majority of
> > time in make install is spent in linking the library and there's no
> > getting around that.
>
> Looping over directory after directory costs some time, and I've heard
> a non-recursive automake setup would fix that.
>
It could, but I don't think it will make much of a difference, but maybe
I'm underestimating. This is milliseconds compared to several seconds of
linking (in the eyeball norm). Of course if we can do it, we should.
For linking the library, IIRC most modern linkers operate in serial
> unless you explicitly try to tell them to parallelize? That's
> annoying and we could look into that if it bothers people.
>
That would be cool, I didn't know that was a thing.
> I think Derek specifically referred to the re-linking of apps whenever
> the library changes, though. That's definitely more paranoid than it
> needs to be. Presumably to be compatible with static linking and
> weird-HPUX-linkers and whatnot, automake forces a re-link whenever the
> library changes, not just whenever the ABI changes?
Correct. I'm curious to try if it still forces a relink if we only have
shared linking and disabled static linking.
> I prefer
> too-paranoid over not-paranoid-enough, but it might be possible to
> tweak the behavior to fall in-between.
>
At the very least, it should be easy to turn off building the apps at
configure time.
> ---
> 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
