On Tue, Jun 02, 2015 at 02:19:59PM +0200, Ian Hinder wrote:
But not disallowed, right?
Not disallowed right now. They would generate warnings. At some point we will disallow it.
I don't want old Kranc-generated thorns to fail to compile and need to be regenerated.
Isn't one of the main points of Kranc-generated thorns that you can easily regenerate them? I would worry more if we would have tens of hand-written thorns with these.
Frank is working on providing shell-script support functions for
There is a ticket (https://trac.einsteintoolkit.org/ticket/1175) and a wiki page (https://docs.einsteintoolkit.org/et-docs/Improving_the_treatment_of_external...) related to this from a while ago.
Good point. However, I don't plan to overhaul the current system right now. I only want to homogenize it a bit - which in turn should make it easier later to implement all the changes proposed there.
Specifically: I am only looking into the "factoring out common code" section, and also not all of that (e.g., I leave building to the scripts, as this usually needs special treatment for each library).
Frank