-
Notifications
You must be signed in to change notification settings - Fork 113
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
Add support for static linking of the L0 adapter #1820
Conversation
e552c50
to
38ac63a
Compare
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.
Bindless Images changes LGTM.
@nrspruit can you please take a look? |
@oneapi-src/unified-runtime-level-zero-write @oneapi-src/unified-runtime-maintain This is a nightmare to rebase (I'm not doing it again until I have a full set of approvals :-)), I'd appreciate a prompt review. |
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.
LGTM
d3ab0df
to
1c95ae4
Compare
intel/llvm build is failing with |
1c4d81b
to
8939cfe
Compare
7d8c910
to
2775137
Compare
62b168d
to
e156b61
Compare
This patch adds a cmake option that builds the L0 adapter as a static library and then embeds its in the loader. The mechanim itself is fairly generic and, when a need arises, the same can be done for other adapters.
This option, marked as PUBLIC, is propagated to the targets linked with the 'ur_adapter_level_zero' target when the Level Zero adapter is built as a static library. This led to a STATUS_DLL_NOT_FOUND error when running test binaries on Windows.
e156b61
to
3abe18c
Compare
This patch adds a build-time option that builds the L0 adapter
as a static library and then embeds its in the loader.
The mechanim itself is fairly generic and, when a need arises,
the same can be done for other adapters.