Different argument order for library vs. component buildlibs

[billsacks]

This isn't exactly a bug itself, but can contribute to bugs, including one that stumped @jedwards4b and me for a while this week: The order of the command-line arguments to the buildlib script, when called as a subprocess, differs for libraries

cime/scripts/lib/CIME/build.py

Lines 462 to 463 in 4312d85

	run_sub_or_cmd(my_file, [full_lib_path, os.path.join(exeroot, sharedpath), caseroot], 'buildlib',
	[full_lib_path, os.path.join(exeroot, sharedpath), case], logfile=file_build)

vs components

cime/scripts/lib/CIME/build.py

Lines 514 to 515 in 4312d85

	compile_cmd = "MODEL={compclass} COMP_CLASS={compclass} COMP_NAME={compname} {cmd} {caseroot} {libroot} {bldroot} ".\
	format(compclass=compclass, compname=compname, cmd=cmd, caseroot=caseroot, libroot=libroot, bldroot=bldroot)

One implication of this is that the parse_input command in buildlib.py cannot be used for libraries.

Changing the argument order for components would be a pain (requiring coordinated changes in a bunch of repositories). But I wonder if it would be feasible to change the argument order for libraries to match that of components?

Even better would be changing these positional arguments to named arguments – for both libraries and components – but I can't think of a backwards compatible way to do that (so again, it would require coordinated updates in a bunch of repositories).

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.