You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We did several big improvements to the build times for our samples, but build still take too long. This is an issue for maintainers, and esp. if you work on the framework. Even on a decent CPU a build takes up to 5 Minutes, which is esp. annoying when working on the framework.
For comparison: On m setup (Windows, AMD Ryzen 8 Core CPU) building this repo takes ~5 Minutes, while doing a full rebuilt of my own repo (~70 samples) only takes about 50s.
The text was updated successfully, but these errors were encountered:
I believe it might be worth to switch from git submodules to vcpkg packages to improve build times. I was able o achieve faster build times this way, take for example the fork I created to support this issue.
Probably not gonna happen. We discussed vcpkg in the past, but the samples support (and are used) on platforms where vcpkg is not available.
Can you better elaborate on which platforms vcpkg is not available?
Additionally, the use of Ninja with parallel build is helpful to reduce build times especially for computers with many CPU cores. If you take a look at the fork, Ninja is also setup to build with multiple cores there.
We did several big improvements to the build times for our samples, but build still take too long. This is an issue for maintainers, and esp. if you work on the framework. Even on a decent CPU a build takes up to 5 Minutes, which is esp. annoying when working on the framework.
For comparison: On m setup (Windows, AMD Ryzen 8 Core CPU) building this repo takes ~5 Minutes, while doing a full rebuilt of my own repo (~70 samples) only takes about 50s.
The text was updated successfully, but these errors were encountered: