-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
build(cmake): Make monolithic libs be built inside Velox's own binary directory when being used as a subproject #12144
Conversation
✅ Deploy Preview for meta-velox canceled.
|
cc @assignUser thank you |
@xiaoxmeng has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
CI is red and I can't see the reason. Any suggestions? Thanks! |
4638ba3
to
7eecf69
Compare
The issue is unrelated, pyvelox currently fails to build #12185 |
@assignUser Thanks. I mean the other job from my previous commit was failing, the job name was |
Ah as the name says that's a meta internal job, if it's something you have to address the meta employee landing the pr will let you know. |
@xiaoxmeng has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@xiaoxmeng merged this pull request in 9fd0b0f. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Similar to #12128, currently when Velox is imported as a subproject of another project, the monolithic libs
libvelox.a
/libvelox.so
will be generated in root project's binary directory which is sub-optimal.The patch fixes the issue so the libs will be generated inside Velox's binary directory.