Open kynan opened 7 years ago
Please note that once ecCodes is built in this mode, any subsequent changes to the installed definition/sample files will NOT be picked up
How do does everyone feel about enabling this? @kmuehlbauer @pelson @ocefpaf
I'm very much open, if this improves speed significantly. But there is a drawback. Users won't be able to add/change definitions and tables in their installations. This could turn the package useless in some environments.
True, should this be a dedicated feedstock then?
Maybe we can use a dedicated branch? Maybe @ocefpaf has an idea.
Maybe @ocefpaf has an idea.
Branches are probably better, but we would need to disambiguate the name with a prefix or something similar.
variant/memfs
? @ocefpaf
@kmuehlbauer @ocefpaf I actually want to try this to work around a runtime failure I'm currently trying to debug rather than for performance. If we can agree on a branch naming convention I'll give it a go.
cc @shahramn
@kynan
You could try with a PR first, to see if this will build correctly. Then @ocefpaf might help us to get the package prefixing correct. Then the PR can be diverted to the new branch.
You could try with a PR first, to see if this will build correctly. Then @ocefpaf might help us to get the package prefixing correct. Then the PR can be diverted to the new branch.
Sounds like a plan.
Done! #28
With #127 it is available on windows. Users can add local tables/definitions. Question: Is it only relevant for windows or does also linux/mac builds profit, @shahramn?
As of 0.16.0 ecCodes supports memory based access to definition/sample files:
How do does everyone feel about enabling this? @kmuehlbauer @pelson @ocefpaf