You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In attempting to build netcdf-interfaces as a dependency of inference-engine, I find that fpm 0.8.1 breaks netcdf-interfaces because the following profiles pass -Werror=implicit-interface to gfortran, whereas fpm 0.7.0 passes -Wimplicit-interface:
no --profile
--profile debug
--profile release
What's the best way to adjust for this change in fpm behavior with little or no change to netcdf-interfaces?
Possible Solution
I'm thinking of submitting a pull request against netcdf-interfaces with
An options.rsp file containing fpm options and
A modified README.md adding @options to the fpm command in the build instructions.
On a related note, it might be nice to be able to choose a specific --profile for a specific dependency without impacting the --profile for the rest of the project. Are there better approaches?
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Description
In attempting to build netcdf-interfaces as a dependency of inference-engine, I find that
fpm
0.8.1 breaks netcdf-interfaces because the following profiles pass-Werror=implicit-interface
togfortran
, whereasfpm
0.7.0 passes-Wimplicit-interface
:--profile
--profile debug
--profile release
What's the best way to adjust for this change in
fpm
behavior with little or no change to netcdf-interfaces?Possible Solution
I'm thinking of submitting a pull request against netcdf-interfaces with
options.rsp
file containingfpm
options andREADME.md
adding@options
to thefpm
command in the build instructions.On a related note, it might be nice to be able to choose a specific
--profile
for a specific dependency without impacting the--profile
for the rest of the project. Are there better approaches?Additional Information
No response
The text was updated successfully, but these errors were encountered: