-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Windows builds with precompiled headers enabled fails on 24.08 and 24.11 #3408
Comments
Filed as internal issue #USD-10412 |
@foundry-markf We definitely expect precompiled headers to work on Windows. We have not run into this error in our local CI builds on Visual Studio 2019, and I've also been unable to reproduce this manually using VS2022. That said, it looks like there've been other reports of similar problems, for example #3141 (which was closed in favor of #3204). I'm hoping to merge that one in shortly. Side note: precompiled headers were disabled on Azure CI builds (which are migrating to GitHub Actions) because of problems with disk space on the runners. We should probably revisit this now that we don't have to deal with the extra weight of boost headers. |
Thanks @sunyab. I've tried building the dev branch this morning at commit e45ffe6 and it fails in the same way as described above. However, I manually copy-n-pasted the changes proposed in #3204, and I'm no longer seeing the issue. I'll retest once you've approved and merged in the changes into dev. |
It sounds like the changes in #3204 work to resolve this and 3204 was just merged into dev, so I'm closing this issue! |
Description of Issue
When building on Windows with the default settings, an error like this is seen
However, I note that the CI in this repo has precompiled headers explicitly disabled. I don't have enough information in the Git history to determine if this is due to this issue
https://github.com/PixarAnimationStudios/OpenUSD/blob/release/.github/workflows/buildusd.yml#L177
Is the intent that precompiled headers should work in Windows builds?
Should the CI be updated to reflect that?
There's obviously a workaround at the moment.
Steps to Reproduce
System Information (OS, Hardware)
Windows 10
VisualStudio 2022
Package Versions
N/A
Build Flags
Nothing specific, other than leave the default precompiled headers option for Windows builds.
The text was updated successfully, but these errors were encountered: