Add executorch_no_prim_ops target #2970
Closed
+73
−46
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:
Currently
libexecutorch.a
always contain prim ops. This becomes a problem when a binary contains 2 "versions" oflibexecutorch.a
, causing a double registration of the prim ops.For example,
libA.so
depends onlibexecutorch.a
and a binaryB
depends on bothlibA.so
andlibexecutorch.a
. Since bothlibexecutorch.a
andlibA.so
contains prim ops, they will be registered twice.In this PR I created another library
executorch_no_prim_ops
forlibA.so
to depend on.Differential Revision: D55907752