Launching from GUI:
Thanks. That helps a lot. Doesn't quite eliminate the problem, but sure makes it a lot easier to manage with quick access to referenced scripts.
Script restructuring:
Some of the scripts are already heavy users of subroutines, but project subs are not really a possibility here, since this exactly the problem we are facing now. To many independent scripts and to much maintenance. I think that in any case, global subroutines is a must and implementing smaller "component" script would simply increase the complexity and not give any noticeable advantage over subs (am I right here?).
I've made a simple .reg file that maps the file location/configuration path to a network share. It should be overcomable to ensure that the fil is registered on all build-related machines before they are used.
|