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
When debugging source-build for bigger projects (such as runtime) copying the entire working directory into the inner build on every re-build is quite expensive.
One such case when the content of the working directory does not change between re-builds is when the tooling is investigated, rather then the repo itself (i.e. cmake).
An option to skip creation of inner build directory could solve the issue.
The text was updated successfully, but these errors were encountered:
[Triage] This may support incremental builds when set. The downside to this is that any source changes a dev wants to test would need to be made in the inner source. It would be a niche setting but there definitely seems like some scenarios that would greatly benefit from this.
Alternatively a possibly better UX would be an option to disable the use of an inner build/clone all together (e.g. #3072). That however feels like a lot more work. Implementing this is likely a single condition so if it helps the dev workflow today, then it feels worthwhile.
Uh oh!
There was an error while loading. Please reload this page.
When debugging source-build for bigger projects (such as
runtime
) copying the entire working directory into the inner build on every re-build is quite expensive.One such case when the content of the working directory does not change between re-builds is when the tooling is investigated, rather then the repo itself (i.e.
cmake
).An option to skip creation of inner build directory could solve the issue.
The text was updated successfully, but these errors were encountered: