ml-apps: Fix building different ML apps subsequently #61
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.
Description
When building ML apps, the MLEK downloads model resources for the model specified by a given application.
The FRI integration of the MLEK prevents these resources from being re-donwloaded if they already exist to speed up build time.
However, in the case of a different application being build, model resources have to be re-downloaded as different ML applications use different models.
To allow the re-download of model resources, the generated ML model resources subdirectory is now generated in the CMake build directory.
Building a different application requires triggering a clean build which will also delete the resources specific to a model used by another application.
Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.