mkmf not included in installation

[uramirez8707]

Describe the bug
mkmf is not included in the installation, fre make will fail when trying to use it

To Reproduce
Install fre-cli and attempt to run fre make, it will fail because it cannot find mkmf in the path

Expected behavior
fre-cli should include mkmf (i.e all of its dependencies)

Additional context
You can work around this by cloning mkmf and adding it to your path, or loading fre/bronx-22 if on gaea.

[singhd789]

@uramirez8707 Just fyi, the module for fre/bronx should already be included in the platforms.yaml, as shown here (this needs to be updated) for gaea:

fre-cli/fre/make/tests/AM5_example/yaml_include/platforms.yaml

Line 5 in 12b35f0

modules: [ !join [*INTEL, "/2022.2.1"],"fre/bronx-20",cray-hdf5/1.12.2.3, cray-netcdf/4.9.0.3]

[uramirez8707]

This is still an issue. mkmf needs to be added to the PATH otherwise fre won't work.

[ceblanton]

If mkmf were conda-installable it could be included as a proper dependency. This would be the most direct solution IMO.

[singhd789]

Yes, if someone could make it a conda package, that might be easier

[ilaflott]

export PATH=$PATH:$PWD ?

[singhd789]

Is this not adding it?

https://github.com/NOAA-GFDL/fre-cli/blob/9fa8b27e326fa51b05765059654bd157d03fcbc1/.github/workflows/publish_conda.yml#L18C11-L18C45

[ilaflott]

that line does add it, yes. but that's only for github's CI/CD. When one does a conda install noaa-gfdl::fre-cli, mkmf should be stuck in $PATH as part of the build section of meta.yaml.

Really, it'd be best to add it to $PATH as part of the pip install routine, but that not being there will only affect a dev like me who knows they can band-aid that easily with their own export PATH=blahblah