-
Notifications
You must be signed in to change notification settings - Fork 537
executorch-the-CMake-target should re-export executorch_core, shouldn't it? #8404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8404
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Cancelled JobsAs of commit aa28e1c with merge base ee7d388 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accept to unblock
@@ -596,7 +596,7 @@ endif() | |||
# any backends. | |||
# | |||
add_library(executorch ${_executorch__srcs}) | |||
target_link_libraries(executorch PRIVATE executorch_core) | |||
target_link_libraries(executorch PUBLIC executorch_core) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not quite sure how this change fixes the error, but looks like CI is green
landing despite two job cancellations for timeout because it seems unlikely this would be related and it's an unbreak |
This seems to fix QNN build failures, and it doesn't make sense to me that every executorch (the CMake target) consumer should also have to explicitly link executorch_core