iOS externals prevent testing on Android

[Mark]

Hi,

My guess is that Android and iOS use the same kind of externals, because are both a type of unix. Android finds externals but doesn't know what to do with them and crashes. The reason why this happens is that RunRev seems to have implemented a half-finished linkage system with externals, which works if you know all the ins and outs of the engine but which doesn't work with custom externals and, more importantly, which doesn't check if an external is compatible with the current platform before loading it.

Kind regards,

Mark

[sturgis]

I have a thought *always a bad thing*

While I don't know how to programmatically set the information in the "copy files" pane, i'm sure someone here does.. And if so you can most likely use savingMobileStandalone (check the dictionary) to adjust the settings (either add or remove the copy files setting based on what you're building for) save the stack and go on from there.


While I can't tell you exactly what to tweak, I can tell you that the setting is most likely in the property set cRevStandaloneSettings.

[jacque]

Android externals were almost ready for release when they had to be pulled out for other unrelated reasons. They will be fully implemented soon, but that's the reason why they are incomplete at this point. It might be easier to just remove the external from Android builds for a little while longer.

[Mark]

Thanks Jaque. I think that's exactly what we figured out.

Mark