NCAR/ccpp-framework

Use absolute paths to dependency source code files

Closed this issue · 1 comments

Description

The paths to dependencies in the generated ccpp_datatable.xml file are relative to the folder that holds the scheme files that need them. Because they are included in a separate dependencies element, decoupled from their source scheme, it is difficult to determine the absolute path to these files and include them in the build.

e.g.,:

<ccpp_datatable>
  ...
  <dependencies>
    <dependency>micm/micm.F90</dependency>
  </dependencies>
  ...
</ccpp_datatable>

Solution

Generate absolute paths for dependencies instead. e.g.,:

<ccpp_datatable>
  ...
  <dependencies>
    <dependency>/glade/work/me/CAM-SIMA/somewhere/micm/micm.F90</dependency>
  </dependencies>
  ...
</ccpp_datatable>

This would also be consistent with other paths in this file, which are absolute.

@peverwhee @nusbaume - did I miss anything?

Alternatives (optional)

Alternatively, users could try to infer the absolute paths from other information in ccpp_datatable.xml, but I couldn't figure out a straightfoward way to do this.

Related to (optional)

none

closing this as it was addressed in #576