Allow Vino + CoreML files to be in different directories, also optional switch to disable coreml for testing #3151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All the data files live in one directory - this gets confusing and hard to manage
This PR enables the openvino and coreml data files to be in other places than the same location as the main model
The parameters may be passed via whisper_context_params as path_coreml and path_openvino. If these are not supplied the current normal all-in-one-place scheme remains but if passed then these directories can be anywhere.
Also I added a disable_coreml parameter. This allows you to build with coreml but disable it on demand - useful for testing and debugging. This is a very simple bypass that merely skips over the coreml init function which has the same practical effect of not having coreml at all