Hey, (and apologies if there's a better place to ask these sorts of questions)
I'm adding some Build Platforms for a current project; in particular, they're console platforms, and so their scripting backend can only be set to IL2CPP. Since this is a constant, I'd like to avoid seeing "Mono/IL2CPP" specified in the SUB editor window; likewise, I'd like to avoid that being a component of the build output folder hierarchy – e.g., where Windows might have Debug\PC\Windows x64\IL2CPP\{game stuff}, I'd like to simply have Debug\{Platform}\{Architecture}\{game stuff}.
However, if I omit setting up scriptingBackends in the build platform's Init() method, it looks like the build platform gets set to Mono by default, and still shows up in the above places (even though I think the builds are still being correctly forced to IL2CPP anyway).
Is there a way to get SUB to completely omit the scripting backend as a component of both the configuration names in the editor window, and in the build output folder hierarchy?
Hey, (and apologies if there's a better place to ask these sorts of questions)
I'm adding some Build Platforms for a current project; in particular, they're console platforms, and so their scripting backend can only be set to IL2CPP. Since this is a constant, I'd like to avoid seeing "Mono/IL2CPP" specified in the SUB editor window; likewise, I'd like to avoid that being a component of the build output folder hierarchy – e.g., where Windows might have
Debug\PC\Windows x64\IL2CPP\{game stuff}, I'd like to simply haveDebug\{Platform}\{Architecture}\{game stuff}.However, if I omit setting up
scriptingBackendsin the build platform'sInit()method, it looks like the build platform gets set to Mono by default, and still shows up in the above places (even though I think the builds are still being correctly forced to IL2CPP anyway).Is there a way to get SUB to completely omit the scripting backend as a component of both the configuration names in the editor window, and in the build output folder hierarchy?