Export is broken about arcadia

[gregschlom]

Haven't tried, but could this fix it?

File->Build Settings->Player Settings->Other Settings and change "Api compatibility level" from "2.0 Subset" to "2.0".

[nasser]

Closed, as this has been working for a while.

@gregschlom Your point is an important one and is in the README now.

[nasser]

Reopened as it is broken again.

Exported apps complain about default symbol writers, which is a dependency of the out of the compiler. Manually copying in the Mono.CompilerServices.SymbolWriter.dll file fixes that error, but additional errors are thrown relating to namespace lookup. I don't think it can find its own DLL files. We might have to set the runtime loadpath separately.

[nasser]

Reopening because while export technically works, a lot of manual effort is required to get there. We'll call this closed when export is as seamless as exporting a non-Arcadia project. This might depend on conditional compilation or better integrating with Unity's export compile chain.

[timsgardner]

Maybe we should break it into more fine-grained issues? Totally smooth automated export to every platform sounds like a big project, especially considering the complications we're expecting for iOS.

[nasser]

I meant more to call this closed once the manual DLL dance is taken care of. We should open separate issues for platform exports, though.

[nasser]

This should be taken care of, but we need to confirm that it works with the new components architecture

[selfsame]

re: #1 (comment)

In the Editor inspector for DLLs you can toggle the supported platforms allowing you to exclude the non build-able parts of Arcadia. Perhaps this could be automated in compilation via meta:

(ns ^:editor arcadia.repl)

Also wondering why editor namespaces are compiled in the first place, does it speed up the environment load?

[nasser]

Confirmed working export on OSX, Windows, Linux and Android. Closing this for the alpha.