NDK issues when working with UE4 and UE5

Development Platform & Builds Mobile
, ,
1

Hi,

we have mobile projects that are still in UE4 and are also working on one UE5.1 project. We currently have the problem that we always have to manually change the NDK version in project settings for each project when packaging a project that uses UE4 or UE5. It seems the same NDK path is used by both UE4 and UE5 which is extremely annoying. We tried it on several pc’s and the problem remains. For some strange reason UE4 and UE5 share the same project settings for NDK / SDK paths.

Is there any way to split both up so they use their own NDK path?

2

If you working with powershell commandline tool, a convenient work around is setting a temporarily environment variable for current run, with command “$Env:{Name} = {Value}”,
for us we using $Env:NDKRoot = “{our_NDK_r25b_location}” to temporarily setup the NDKRoot for current UE5 android build job in CI under windows10+powershell.
There should be similar ways to setup temporarily environment variable for command line prompt(Windows) and unix bash, should be able to work around this issue.