aharui commented on issue #237: (Feature Request) Support -external-library-path using royale-js only URL: https://github.com/apache/royale-asjs/issues/237#issuecomment-390048844 There are now platform-specific parameters in the compiler. So not just -library-path, but now also -swf-library-path and -js-library-path. Same for -external-library-path, -swf-external-library-path, -js-external-library-path. As you probably can guess, that allows specification of different SWCs per platform. That turns out to be important for using airglobal.swc for SWF and js/libs/js.swc for JS. The logic in the compiler says that when compiling for SWF, if -swf-library-path is used, then ignore the plain -library-path. Same for JS. Not sure if that's the best decision, but is how it works today. So, good or bad, that means you have to consistently use the same parameter in all specifications of your libraries. If you are using frameworks/js-config.xml as a default config, you have open it up and look to see how it specified js/libs/js.swc (which contains the Object definition for JS). Did it use -external-library-path or -js-external-library-path? And then you have to use the same parameter for your "second library" and you have to use += to append your second library otherwise you will be telling the compiler to only use your second library and not js/libs/js.swc. That's the long way of telling you that I'm guessing that you just have to get your compiler options right and it should work. If you are still stuck, post your full set of compiler options.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
