Skip to content

Rename CMake target executorch to executorch_prim_ops#19624

Draft
kirklandsign wants to merge 1 commit into
mainfrom
cmake/rename-executorch-to-prim-ops
Draft

Rename CMake target executorch to executorch_prim_ops#19624
kirklandsign wants to merge 1 commit into
mainfrom
cmake/rename-executorch-to-prim-ops

Conversation

@kirklandsign
Copy link
Copy Markdown
Contributor

@kirklandsign kirklandsign commented May 18, 2026

Summary

The executorch CMake target only contains 3 prim_ops files (et_copy_index.cpp, et_view.cpp, register_prim_ops.cpp) linked on top of executorch_core. The name executorch was misleading — it suggested the full runtime, but it's just prim_ops registration.

Rename the target to executorch_prim_ops across all CMakeLists.txt and .cmake files. Update the definition-site comment to accurately describe what the target provides. Update the required_lib_list in executorch-config.cmake so find_library looks for the new name.

The CMake package name (find_package(executorch ...)) and project namespace aliases (executorch::backends etc.) are unchanged.

Test plan

CI

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

The `executorch` CMake target only contains 3 prim_ops files
(et_copy_index.cpp, et_view.cpp, register_prim_ops.cpp) linked on top
of executorch_core. The name `executorch` was misleading — it suggested
the full runtime, but it's just prim_ops registration.

Rename the target to `executorch_prim_ops` across all CMakeLists.txt
and .cmake files. Update the definition-site comment to accurately
describe what the target provides. Update the required_lib_list in
executorch-config.cmake so find_library looks for the new name.

The CMake package name (`find_package(executorch ...)`) and project
namespace aliases (`executorch::backends` etc.) are unchanged.
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 18, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19624

Note: Links to docs will display an error until the docs builds have been completed.

❗ 2 Active SEVs

There are 2 currently active SEVs. If your PR is affected, please view them below:

❌ 11 New Failures, 1 Pending, 6 Unrelated Failures, 6 Unclassified Failures

As of commit 4315f91 with merge base c4ec988 (image):

NEW FAILURES - The following jobs have failed:

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 18, 2026
@github-actions github-actions Bot added ciflow/trunk module: arm Issues related to arm backend labels May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: arm Issues related to arm backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant