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

[c++] Fix Windows build regressions and stop using deprecated TileDB APIs #2445

Merged
merged 3 commits into from
Apr 17, 2024

Conversation

teo-tsirpanis
Copy link
Member

Issue and/or context: As part of validating that libtiledbsoma does not use deprecated TileDB APIs, I tried to build it on my Windows machine with a build of TileDB with all deprecated APIs removed from the headers. I encountered a couple of errors and this PR fixes them. I also migrated two deprecated API usages in the tests.

Changes: With an exception in two tests, we mostly replace constructs that caused errors for MSVC with constructs that do not. The deprecated API migration is very straightforward.

Validated by successfully building libtiledbsoma and unit_soma on my local machine and running the tests. To prevent further regressions we should eventually work towards reenabling Windows CI in #1962.

Notes for Reviewer:

@ihnorton ihnorton requested a review from nguyenv April 17, 2024 18:36
Copy link
Member

@nguyenv nguyenv left a comment

Choose a reason for hiding this comment

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

Thank you!

@johnkerl johnkerl merged commit d4138cc into single-cell-data:main Apr 17, 2024
13 checks passed
@johnkerl johnkerl changed the title Fix Windows build regressions and stop using deprecated TileDB APIs. [c++] Fix Windows build regressions and stop using deprecated TileDB APIs Apr 17, 2024
@teo-tsirpanis teo-tsirpanis deleted the windows-build-fix branch April 18, 2024 00:55
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.

3 participants