(IL2CPP for Windows) Can we build GameAssembly.dll manually?

Unity Engine
1

Now that we have IL2CPP for Windows desktop on 2018.1 beta, I’m curious on how to build GameAssembly.dll manually for it, preferably with VS2017 solution. Right now the build process is completely hidden from the user unless there’s some build error, would be nice if it wouldn’t be such a “black box”.

This is relevant to a bug discussed here: Vote for Windows Standalone with Scripting Backend IL2CPP (MUCH better script performance) as you can’t currently add your custom c++ files into IL2CPP build on windows. This bug could be worked around with a manual build. But even when the mentioned bug gets fixed, this would be beneficial for projects that have lots of native code as well.

Would be nice if IL2CPP left VS solution after build for easier debugging and allowing manual changes. (I’m aware there are still symbols for GameAssembly.dll and you can breakpoint the generated code but you need to drag the relevant files into VS manually or create a new solution on your own if you want to do this).

2

Hi, we actually aim to make standalone player with il2cpp work similarly as UWP does (you build from Unity, then you get a VS project you can build afterwards), but we haven’t done it yet due to lack of time, and we wanted to ship standalone player with IL2CPP sooner rather than later.

1 Like
3

Ah, that sounds good, looking forward to it then :slight_smile: