Skip to content

Move thirdparty under include/liboculus#42

Merged
amarburg merged 1 commit intomainfrom
dev/move_thirdparty_under_include
Oct 8, 2025
Merged

Move thirdparty under include/liboculus#42
amarburg merged 1 commit intomainfrom
dev/move_thirdparty_under_include

Conversation

@amarburg
Copy link
Collaborator

@amarburg amarburg commented Oct 7, 2025

Have thirdparty at the same level as liboculus created some odd naming conflicts where it might not be clear that thirdparty belongs to liboculus. Or a situation where outside code uses a different path than internal code.

By putting thirdparty under include/liboculus we can use a consistent pathing for include files.

@amarburg amarburg self-assigned this Oct 7, 2025
@amarburg
Copy link
Collaborator Author

amarburg commented Oct 7, 2025

NOTE this is a breaking change, it may require changes in downstream users of liboculus.

@amarburg amarburg merged commit cb59e74 into main Oct 8, 2025
6 checks passed
@amarburg amarburg deleted the dev/move_thirdparty_under_include branch October 10, 2025 19:22
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.

1 participant