Build Fortran libraries

adamcpovey commented 2 years ago

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Closes #39

It's possible to keep using the tarballs rather than GitHub for the source, but you'd have to change to the CMake file and that has a slightly different folder structure which will impact the Windows build.
In my local environment, I could build successfully with ctest but could not do that with this repo for reasons I don't understand. Hence, I switched to a cmake; make test arrangement that I think does the same thing but might not.
You will need to check with https://github.com/conda-forge/hdfeos2-feedstock that this doesn't break their builds as h4fc is not output. It's fine for me but, again, my local environment is weird.
I haven't checked the Windows build as I don't have one of those computers. Sorry.
I haven't done the re-rendering requested as the first step of that is "install conda smithy" and I super do not want to touch my root environment at this moment in time (being in the middle of something).

conda-forge-linter commented 2 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

conda-forge-webservices[bot] commented 1 year ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

conda-forge / hdf4-feedstock