Search Unity

[Android, IL2CPP] NDK r13b says "invalid path," NDK r16b complains it isn't r13b

Discussion in 'Editor & General Support' started by FuzzyQuills, Jan 10, 2019.

  1. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,871
    Hello, any idea why IL2CPP specifically needs r13b? I attempted to install the NDK this morning to use IL2CPP, but using r13b fails to build with "invalid path, please pick another folder" while r16b claims Unity NEEDS r13b.

    I made sure to use the 64-bit NDK as well, any idea as to why this is happening? I'm using Unity 2017.4.17

    (Also if this needs to be moved, please do so, this is the first time in a while I've posted here)