You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@royale.apache.org by GitBox <gi...@apache.org> on 2018/05/17 20:50:20 UTC

[GitHub] jgranick opened a new issue #237: (Feature Request) Support -external-library-path using royale-js only

jgranick opened a new issue #237: (Feature Request) Support -external-library-path using royale-js only
URL: https://github.com/apache/royale-asjs/issues/237
 
 
   Thanks to your guys help, we are generating extern SWC files using `royale-js` rather than the `royale-js-swf` package, which has been great -- it installs over CI and automated builds properly, is much smaller, and is closer to our goal -- JS only. Today I noticed one issue, though, building an SWC for a library that relies on a second library. Use of `-external-library-path` triggers the "Warning: Missing built-in Object" message and does not build. I assume that this is because the argument requires the `royale-js-swf` package (currently), but it would be really nice if there was a way for it to work without.
   
   Another option would be something like `-external-source-path` to note a directory of files to use for completion, but not to compile into the SWC. As we have sources and an external SWC available, this would also work for us to exclude these types in the child SWC.
   
   I'm happy to help more if my explanation did not fully make sense, or if there's a way to use the compiler I'm missing :smile:

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services