Skip to content
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

Don't link directly to clFinalizeCommandBufferKHR #320

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

jansol
Copy link
Contributor

@jansol jansol commented Dec 17, 2024

It's an extension function so use the runtime function pointer like for the other command buffer functions.

Fixes #292

It's an extension function so use the runtime function pointer like for
the other command buffer functions.
@CLAassistant
Copy link

CLAassistant commented Dec 17, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@bashbaug bashbaug left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this!

I was wondering how we were passing the unit tests with this bug, but it looks like we don't have any tests that finalize a command buffer yet (we do have PR #270, but I'm not sure it would have caught this problem, either). We should add some tests to catch these types of problems.... but not in this PR.

@bashbaug bashbaug merged commit 12a9a65 into KhronosGroup:main Dec 18, 2024
52 checks passed
@jansol jansol deleted the command-buffer-pfn branch December 18, 2024 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CommandBufferKhr::finalizeCommandBuffer() causes link failure
3 participants