aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-395549239
I recently pushed changes to allow use of @externs in the source-path.
aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-390072757
A SWC is a package of pre-compiled AS. So once you distribute it, your AS
source files are no longer needed to
aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-389385188
You are correct that an extern represents code that exists at runtime.
However, in Royale, the fact that some code is
aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-389228988
To create a SWC without needing AIR SDK, this should work (worked for me):
`compc
aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-389228988
To create a SWC without needing AIR SDK, this should work (worked for me):
'compc
aharui commented on issue #232: (Feature Request) Support for JS extern output
with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-388905773
Do you have test cases so we can make sure we understand what you are
looking for? I don't think we have any
