Wrap server generated yaml files inside et_operator_library #5777
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.
Summary:
This diff is to make the model config codegen flow work on Edge MLHub by enabling the
et_operator_libraryAPI to take a .yaml file.The code changes in
fbcode/executorch/codegen/codegen.bzlwas copied from a stale diff D61824614 made by Mengwei. That one didn't landed because the owner of SceneX/v5002 model didn't have time to test it.The code changes in
fbcode/executorch/build/fb/clients.bzlis to make auto-generated BUCKs under the directoryfbsource//xplat/executorch_model/...have visibility to theet_operator_libraryAPI.By design, this is the codegen flow:
xplat/executorch_model/build/...that callset_operator_libraryand pass in the .yaml as a parameter;Next I will modify the codegen script so that it creates the .yaml and BUCK in the correct format for this flow to work E2E.
Differential Revision: D63305843