Hi Jack, I gave this a quick read, and it makes sense to me.
I do suspect it will be too much for some novice users, for some definition of 'novice', e.g. people who barely know what a compiler is, etc.
Maybe some kind of compatibility matrix of full vs subtoolchains would be interesting, to make it clear which toolchains *can* be combined?
regards, Kenneth On 06/04/2017 06:13, Jack Perdue wrote:
Howdy all, At some point in the past year I blatantly lied to Kenneth by claiming we had a web page that clearly explains to our users what components are in each toolchain while we use a flat (non-hierarchical) module naming scheme. Since then I've/we've made such a page. :) https://hprc.tamu.edu/wiki/index.php/SW:Toolchains Does it make sense to EB builders? Would your users understand it???? What could be done to make it easier for users to grasp? We have LOTS of novice users so its always hard for me (who's been doing UNIX for 30+ years now) to relate what is important. Thanks for any feedback (whether I agree or not),
