Search Unity

  1. We would like to hear your feedback about Unity and our products. Click here for more information.
    Dismiss Notice

Cannot build with ILC2PP in 2018.2

Discussion in 'Editor & General Support' started by Boslof, Oct 17, 2018.

  1. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
    Upgraded a project from 5.6.5p4 to 2017.4.13f1 and then to 2018.2.12f1 in order to build with ILCPP2, but I end up with "il2cpp.exe did not run properly!" when building.

    I can build fine with another project in 2018.2, but that one was created in Unity 2018.
     
  2. Xblade-Imperium42

    Xblade-Imperium42

    Joined:
    Jan 12, 2016
    Posts:
    605
    Yep I have this issue too, any word?
     
  3. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    3,778
    It looks like the part of the error message that matters is:

    C:\Program Files\Unity\Hub\Editor\2018.2.12f1\Editor\Data\il2cpp\libil2cpp\il2cpp-config.h(3): fatal error C1083: Cannot open include file: 'assert.h': No such file or directory

    This usually means something is wrong with the Windows SDK installation on the machine, as assert.h should be provided by the Windows SDK.

    I'm rather surprised that a project newly created in Unity 2018.2 builds correctly.

    @Boslof:

    As a sanity check, can you confirm that your project which does not build has all of the same Player Settings options as the one that does build?

    @i42-Xblade

    Can you build a new, empty project with IL2CPP on Unity 2018.2 as well?
     
    indieDoroid likes this.
  4. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
    They have pretty much identical Player Settings. Only difference is Dynamic Batching and Scripting Define Symbols.
     
  5. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
    Tried building the broken one with just an empty scene, but had no luck there either.
     
  6. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
    Copied everything from the assets folder into a blank project created in 2018.2.
    Still has the same problem when trying to build.
     
  7. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    3,778
    If I am understanding this, an empty project with Unity 2018.2 builds correctly. Then the contents of the Assets/ folder, from the project that does not build, when copied into the previously fine empty project, cause the build to fail as shown in the original post?
     
  8. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    6,243
    Is "assert.h" file in "C:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\ucrt" on your machine?
     
  9. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
  10. Xblade-Imperium42

    Xblade-Imperium42

    Joined:
    Jan 12, 2016
    Posts:
    605
    Indeed, it's here for me too, @Tautvydas-Zilys



    Is this because I went from 5.6 >> 2017 >> 2018? Was there some skipped dependency I'm not seeing?
     
  11. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    6,243
    Can we get a bug report on this? I can't tell what's going on without having a repro unfortunately. The include paths look correct in the command line you pasted, and I have no idea what could cause the compiler to not find that file.
     
  12. Boslof

    Boslof

    Joined:
    Aug 21, 2014
    Posts:
    6
    Found out the issue. Our Anti-Cheat Toolkit wasn't up-to-date. Can build fine after updating that.
     
    Xblade-Imperium42 likes this.
  13. Xblade-Imperium42

    Xblade-Imperium42

    Joined:
    Jan 12, 2016
    Posts:
    605
  14. indieDoroid

    indieDoroid

    Joined:
    Jan 25, 2016
    Posts:
    146
    @JoshPeterson Thanks for the SDK hint.. I installed windows 10 sdk and got il2CPP to work.
     
    JoshPeterson likes this.