Add an option to use our own version of CUTEst

[amontoison]

@AndrewLister-STFC

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (9467c8c) 88.73% compared to head (b463c2b) 88.71%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #319      +/-   ##
==========================================
- Coverage   88.73%   88.71%   -0.02%     
==========================================
  Files           5        5              
  Lines         790      789       -1     
==========================================
- Hits          701      700       -1     
  Misses         89       89              

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[dpo]

I’m not a big fan of this. The Julia interface could be out of sync with the version of CUTEst that the user has installed. Instead, I would very much prefer that we cook up a way to use the CUTEst JLL from outside Julia.

[amontoison]

This backdoor is not documented and for the developers. It's a way to test new modifications or a new version of a package before that we precompile them with BinaryBuilder.jl / Yggdrasil. It's what we do for HSL.jl, GALAHAD.jl, MUMPS.jl, QRMumps.jl, etc...

[amontoison]

I also try to recompile CUTEst with Yggdrasil (https://github.com/JuliaPackaging/Yggdrasil/pull/7924) for Andrew. He sent me an email for that. He would like to use the single precision version of CUTEst that Nick recently updated with the Julia interface CUTEst.jl.

[dpo]

Then we should at least display @warn messages alerting the user that this usage is not supported and that they’re using an external CUTEst library at their own risk.