Add support for unity builds - #2011

Documentation and unit test are missing.

Wonder if it should be integrated to https://github.com/dcourtois/premake-compilationunit (listed in https://premake.github.io/community/modules/#tool-modules) which does Single compilation unit support.

Documentation and unit test are missing.

If you could point me to where I should be adding those it would be great.

Wonder if it should be integrated to https://github.com/dcourtois/premake-compilationunit (listed in https://premake.github.io/community/modules/#tool-modules) which does Single compilation unit support.

The difference here being that Visual Studio itself does that kind of "Unity/Single Compilation Unit" automatically. For example if you enable it in a project it will generate a file called "unity_<random_suffix>.cpp" that basically does what that module is doing.

I haven't added more flags (honestly because I didn't need them myself) but a more complete set of flags exist for Unity/Jumbo builds that specify how many files should be packed up in one Unity file etc.

That module is more useful in a context where native support for Unity builds doesn't exist.

Documentation and unit test are missing.

If you could point me to where I should be adding those it would be great.

I would say

• UTs should go somewhere in premake-core\modules\vstudio\tests\vc2010
• Doc should be in premake-core\website\docs (premake5 docs-check should pass)

Wonder if it should be integrated to https://github.com/dcourtois/premake-compilationunit (listed in https://premake.github.io/community/modules/#tool-modules) which does Single compilation unit support.

The difference here being that Visual Studio itself does that kind of "Unity/Single Compilation Unit" automatically. For example if you enable it in a project it will generate a file called "unity_<random_suffix>.cpp" that basically does what that module is doing.

That module is more useful in a context where native support for Unity builds doesn't exist.

I meant: use special flag for msvc which can do it natively, but keep the module as is for other actions.

I meant: use special flag for msvc which can do it natively, but keep the module as is for other actions.

I mean you could do that but this feature really should be part of visual studio as this is a native feature on visual studio itself so in essence premake is missing it.

Can you add the documentation so the CI can pass that step?

Missing one more step in the documentation (and maybe this is something we should better document in the contributing doc), but you need to add it to the sidebar.js since it's a new API.

Missing one more step in the documentation (and maybe this is something we should better document in the contributing doc), but you need to add it to the sidebar.js since it's a new API.

yeah sorry about that, been super busy with work and it could be that its written somewhere but I didn't see it.

When I try to use this option I get this error.
attempt to call a nil value (global 'enableunitybuild')

Am I missing something here?

What version of premake are you using?

What version of premake are you using?

Premake 5.0.0-beta2

Currently I managed it by creating my own hook.

Try one of the CI builds. They should have it.