Skip to content

make paths key in compile yamls optional #935

Description

@rem1776

Is your feature request related to a problem? Please describe.
The paths key in the compile yamls always needs to start with the same exact name as the component key, since thats where it gets cloned into. This is a bit redundant since both are in the yaml, especially for FMS where it will always be just "FMS".

Pretty minor issue, but can be pretty confusing because if you mess with the casing or use the repository name instead (ie. GFDL_cubed_sphere instead of atmos_drivers), you'll still "compile" that component, it will just create an empty library file and fail later on.

Describe the solution you'd like
ideally paths could be optional, and by default it will compile the entire component repository. I think it should be a way to speed up compilation, not a necessity.

Describe alternatives you've considered
check or append the path to the known source directory. This would break compilations for components that use external files (mom6/sis2), but I think it would be beneficial if each component build was self-contained.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions