aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-440091062
Well, after playing with it a bit, my conclusion is that using Royale JS
output as
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-439787729
I didn't think the .js files we pack in the SWCs could be used as externs.
They
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-439673123
IMO, it will make the SWCs really fat to additionally pack Externs in them.
And it
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-439515961
After thinking about this more, I think we want to add an option to the
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-437565834
I think we should be able to add an "Externs" compiler target (like we have
for SWF
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-437565706
You should be able to pass these options to GCC via the Royale compiler. I
think the
aharui commented on issue #57: Dependency error when extending class and
implementing interface from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-437532076
Interesting. The interface shouldn't be in the requires list. But after we
fix
