Build: fix pre-compiled header files for MSVC/Ninja#3204
Build: fix pre-compiled header files for MSVC/Ninja#3204pixar-oss merged 3 commits intoPixarAnimationStudios:devfrom
Conversation
| @@ -72,7 +72,7 @@ option(PXR_ENABLE_GL_SUPPORT "Enable OpenGL based components" ON) | |||
|
|
|||
| # Precompiled headers are a win on Windows, not on gcc. | |||
There was a problem hiding this comment.
can we also revise the comment to not say Windows, but rather "msvc with msbuild"
There was a problem hiding this comment.
Maybe just remove this comment - or do the homework and measure this properly :-)
I did a quick stopwatch comarison... msvc/ninja with PCH took about 5min and without PCH about 6min... so we could also just say "... are a win with MSVC ..."
There was a problem hiding this comment.
On another note - I've been using sccache with windows msvc USD builds recently, and been pretty happy with it so far. Haven't done any time comparisons, but rebuilds feel faster - particularly if you switch branches and come back, so a lot of stuff has updated timestamps but hasn't actually changed.
|
thanks for noticing this |
…ory for the output pch file exists
…e properties AFTER adding them to the target otherwise the custom command is not triggered
1de720e to
4f089c3
Compare
You are welcome. I took another look and found the actual bugs. There was a missing directory and wrong cmake command order when PCH was enabled. I reused this PR and force pushed. |
|
A note for CLion users, do not get confused (like I did) by output like this in the CMake window: This is an artifact of the CLion "intellisense" and not related to the USD build system... |
… compilation errors)
|
Thanks, this looks ready for an internal review. |
|
Btw, I tried to run the tests, there are over 100 failing out of 600 - is this exepected on |
|
Filed as internal issue #USD-9931 |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@mistafunk Our internal CI is currently showing no failures, so I would not expect anything like that. I also can't imagine anything specific to this change that would be causing that either. Do you have an example of a failing test you could share here? I'd bet they're all failing for the same reason. |
|
I'll close my PR3141, since it looks like this fixes that and does a bit more as well! |
|
I cannot reproduce the linux build failure locally... is the pipeline timeout too low? |
|
There is also #3120 that fixes this same issue. |
Description of Change(s)