Skip to content

Conversation

@JawadKhan65
Copy link

Description

This PR renames the CMake target executorch to prim_ops_lib for better clarity, as the name more accurately reflects its purpose as the library for primitive operations.

Changes:

  • Renamed executorch target to prim_ops_lib in root CMakeLists.txt
  • Added add_library(executorch ALIAS prim_ops_lib) for backward compatibility
  • Updated executorch-config.cmake to call target_link_options_shared_lib(prim_ops_lib)
  • Removed redundant manual calls to target_link_options_shared_lib in examples and backends:
    • examples/models/llava/CMakeLists.txt
    • examples/devtools/CMakeLists.txt
    • extension/android/CMakeLists.txt
    • backends/cadence/CMakeLists.txt
    • examples/models/llama/CMakeLists.txt

Testing:

  • Verified all changes through code inspection
  • Set up a Python virtual environment and installed dependencies
  • Ran the CMake configuration process to verify that the updated targets work correctly
  • Ensured backward compatibility via the alias mechanism

Benefits:

  • Improved clarity in the codebase
  • More accurate naming that reflects the actual purpose of the library
  • Simplified CMake files in examples by relying on the config file for linking options

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 18, 2025

🔗 Helpful Links

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

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

❌ 218 New Failures, 2 Unrelated Failures

As of commit d162123 with merge base ea4a7fa (image):

NEW FAILURES - The following jobs have failed:

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

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

@facebook-github-bot
Copy link
Contributor

Hi @JawadKhan65!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@JawadKhan65
Copy link
Author

@pytorchbot label "release notes: build"

@pytorch-bot pytorch-bot bot added the release notes: build Changes related to build, including dependency upgrades, build flags, optimizations, etc. label Jun 18, 2025
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot facebook-github-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 Jun 18, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 19, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@JawadKhan65
Copy link
Author

@pytorchbot

@GregoryComer
Copy link
Member

@JawadKhan65 Sorry for the slow response - I know it's a bad look from the framework's perspective. I've triggered CI runs on the PR, and it looks like there are a few remaining tweaks needed. If we can get those resolved, I'll stamp and we can merge it. Thanks!

@GregoryComer
Copy link
Member

Fixes #11761.

@JawadKhan65
Copy link
Author

@larryliu0820 changed

@kirklandsign
Copy link
Contributor

Mind rebasing the patch?

JawadKhan65 and others added 4 commits August 13, 2025 15:40
- Renamed executorch target to prim_ops_lib in CMakeLists.txt
- Added executorch as an alias for backward compatibility
- Updated executorch-config.cmake to use prim_ops_lib
- Removed redundant manual target_link_options_shared_lib calls in examples
- Updated documentation to reflect the new target name
…n up target_link_options_shared_lib, and update CMake as requested
@JawadKhan65 JawadKhan65 force-pushed the rename-executorch-target branch from 2e09b42 to c6643bc Compare August 13, 2025 15:48
@JawadKhan65
Copy link
Author

Mind rebasing the patch?

Rebased on latest main and pushed.

# llama_main: test binary to run llama, with tokenizer and sampler integrated
#

<<<<<<< HEAD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this

Comment on lines 87 to 91
=======
# find `executorch` libraries Same as for gflags
set(executorch_DIR ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/cmake/ExecuTorch)
find_package(executorch CONFIG REQUIRED)
>>>>>>> 4bc106e7a5 (Rename CMake target 'executorch' to 'prim_ops_lib' for clarity)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the rebase

Comment on lines 51 to 58
<<<<<<< HEAD
=======

# If we reach here, ET required libraries are found.
target_link_libraries(executorch INTERFACE executorch_core)
target_link_options_shared_lib(prim_ops_lib)

>>>>>>> 2e09b42180 (Address larryliu0820 review comments: remove duplicate installs, clean up target_link_options_shared_lib, and update CMake as requested)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix this

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

anything else?

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 13, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@zingo zingo added ciflow/trunk module: arm Issues related to arm backend labels Aug 13, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 13, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@kirklandsign
Copy link
Contributor

Hi @JawadKhan65 could you please fix the version control marker? we can retry the CI

@JawadKhan65
Copy link
Author

Hi @JawadKhan65 could you please fix the version control marker? we can retry the CI

is it fine now?

@github-actions
Copy link

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the stale PRs inactive for over 60 days label Oct 14, 2025
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 release notes: build Changes related to build, including dependency upgrades, build flags, optimizations, etc. stale PRs inactive for over 60 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants