-
Notifications
You must be signed in to change notification settings - Fork 8
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 failing on Windows: "Not able to resolve vector element?: Continue" #24
Comments
I've made a very quick & dirty attempt at upgrading to autocxx 0.26: Raphiiko@15f874e If someone who's more knowledgeable at Rust could have a look at upgrading this project to autocxx 0.26.0 properly, that would be fantastic. |
Thank you for the detailed report! We have been seeing similar issues in discord. If upgrading to a newer autocxx fixes the issue, I'll try that. |
Note BTW that autocxx is likely willing to support Debug and Copy impls for some basic types like enums: google/autocxx#1322 |
Oh that's great news! That in particular seemed to be the main blocker for being able to upgrade more easily.
Is there a public (OpenVR-related) Discord server that I'm not aware of, or did you just mean Discord in general? I can by now confirm that upgrading autocxx allows me to make new OyasumiVR builds again. |
Discord here being the SlimeVR discord server, as that was the main user of the library |
I reported this on Discord but I found using LLVM/Clang 17 pre-releases work fine, I don't know why as I don't know much about C/C++ and bindings. That at-least allows you to dev build, but I don't know how to get that version in an action workflow. EDIT: I don't know whether the issue is with |
I made a fork similar to Raphiiko's but without the OyasumiVR changes and manual Debug impl to still support thiserror https://github.com/Shays-Forks/ovr_overlay It works for me and compiles on actions 👍 |
Hi! For a while now I've been using (a slightly modified version of) this library in OyasumiVR. I'm running into an issue with building this package that I'm getting rather stuck on, and I'm hoping someone might know why.
The issue
Between now and roughly two days ago, I can no longer seem to build this library in GitHub's Windows runners. I don't have a clue if this is because of an issue with ovr_overlay itself, autocxx, or something completely different, but I am really hoping you might have some idea about what might be going on.
This is the main error that recently started occurring when building this library on one of GitHub's Windows runners:
I'm personally not too experienced with lower level development and languages like rust/c++, so I've got some difficulty figuring out how to start tackling this issue.
What I've tried
Building it locally I don't seem to have a problem, so I'm assuming something changed on GitHub's side.
In an attempt to reproduce it locally, I've verified that I'm building with the exact same Rust version (1.70.0 stable), as well as the same version of clang (16.0.6, target: x86_64-pc-windows-msvc). From what I can tell the referenced version of the openvr submodule is pinned, so I figured that can't be where the issue stems from. I've cleared my target folders, nuked my rust caches, but none of that seems to help to reproduce the issue locally.
On GitHub's runners, I've tried reproducing the issue with the non-modified version of this library (the one on this repository's main branch), and with that I run into the same problem.
As this library is still on autocxx 0.21.x, I've attempted upgrading it to autocxx 0.26.x in the hopes that it might fix my issue. However even just going up to autocxx 0.22.0, I run into build errors that I'm not sure how to solve: For some reason autocxx >0.22 no longer generates Copy and Debug derives on enums, and it does not look like they currently support adding these back?
How to reproduce
In a fork of this repository, I've updated the main-ci.yaml workflow to build on Windows instead of Ubuntu, as follows: https://github.com/Raphiiko/ovr_overlay_oyasumi/blob/build-testing/.github/workflows/main-ci.yml
If you have GitHub run this workflow, as of two days ago, the build will fail. Logs from this build run can be found here: https://github.com/Raphiiko/ovr_overlay_oyasumi/actions/runs/6121221520/job/16614579309
Details & Logs
Error (No backtrace)
Error (Enabled Backtrace)
Error (Full backtrace)
Are there other things I could check for? Other versions of installed tools I might have missed, other dependencies that might have not been as pinned as I thought they were?
If you have any clues for me or any assistance, I'd be very grateful! My thanks in advance.
The text was updated successfully, but these errors were encountered: