Closed thempc closed 7 months ago
Hi @thempc - we only test and support MSVC on Windows is that not an option for you?
On Linux we support Clang, see the platform readme, but you may have to update some build configuration settings/defines to make Clang work on Windows.
Hey @preist-nvidia, thanks for the quick reply. MSVC is technically an option, however we've chosen clang for multiple other reasons. If this isn't something supported then of course feel free to close this issue, I just assumed you might wish to know as it used to work before.
We'll be fine with adjusting the code locally to make it work. If appreciated we can make a pull request with it later.
Yes, always best to let us know! And we do need to state more clearly what compilers we support on Win.
Please don't worry about the PR for now, I'd ping you if it becomes relevant. Thank you very much for offering!
Closing with this.
It may still be worth noting that Microsoft (vendor of MSVC) recommends against accessing the fields of __m128
directly:
https://learn.microsoft.com/en-us/cpp/cpp/m128?view=msvc-170
You should not access the
__m128
fields directly.
There's only a handful places where PhysX does this (grep '\.m128_'
), so it may be worth fixing regardless of intended clang compatibility.
Versions
PhysX v5.3.1 Windows 11 Visual Studio Community 2022 - Version 17.8.5
Additional Info
I'm in the process of upgrading from 4.1 to 5.3.1, this wasn't an issue in the 4.1 release.
Steps to Trigger Behavior
Code Snippet to Reproduce Behavior
Expected Behavior
It's expected the code compiles without issues.
Actual Behavior
The code will fail to compile and gives the following errors: