When the feature is enabled, you’ll see ‘Unity Build’ options in the C/C++ properties: You can set this as an environment variable or create in your root directory with the following content: To enable experimental unity support, a project needs to have EnableUnitySupport set to ‘true’. Please let us know if it works for you and what can make it easier. In Visual Studio 2017 version 15.8 (Preview 3), we are introducing an experimental unity build support, which makes it easy for new users to adopt unity and allows existing unity users to have better IDE performance. See the following articles about pros and cons of unity builds in CMake and Chromium build: We’ve been impressed with the speed unity builds were adopted, especially in game development, even though combining files together often requires code changes to be able to build without errors and maintain code semantics. Currently there is no easy way to exclude source files from the build and unity files from the IntelliSense parsing, so we do quite a lot of unnecessary work there. Looking at some customer feedback regarding slow IntelliSense, we found that projects often include both source files and unity files including those source files. Just to avoid any confusion – this blog is NOT related to the Unity game engine. Many big codebases use so-called unity (jumbo) builds where many source files are included in one or a few ‘unity’ files for compilation, which makes compiling and linking much faster.
0 kommentar(er)
