Are you using the remove-circulars compiler option?

> On Dec 14, 2018, at 10:24 AM, Alex Harui <[email protected]> wrote:
> 
> OK.
>  
> Please post a link to the entire output of the compiler including, if 
> possible, the command-line you used.  I won’t have time to look at it right 
> away as I am at the end of my work day.
>  
> Also post links to Client.as, Client.js, OasisClient.as, OasisClient.js, 
> OasisHTML5Launcher.as, OasisHTML5Launcher.js
>  
> And also verify how the compiler “should” find Client.js.  Is Client.as in 
> the source-path or is Client.js in a SWC?
>  
> Thanks,
> -Alex
>  
> From: mrchnk <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Thursday, December 13, 2018 at 10:24 PM
> To: "[email protected]" <[email protected]>
> Subject: Re: Linkage problem for asjs compiler
>  
> Same problem with the nightly build. I also asked about my issue in openfl 
> community. 
> I think that problem may be related to circular dependencies in my code.
> Is there any way that can be handled automatically by royale compiler?
>  
> On Thu, Dec 13, 2018 at 11:23 PM Alex Harui <[email protected] 
> <mailto:[email protected]>> wrote:
>> Hi,
>>  
>> Try a nightly build of Royale.  I think some things have been fixed in the 
>> calculation of dependencies.  I think if you are using npm, you can 
>> uninstall royale and then:
>>  
>> npm install 
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/apache-royale-0.9.6-bin-js.tar.gz
>>  
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-royale-0.9.6-bin-js.tar.gz&data=02%7C01%7Caharui%40adobe.com%7C3bac7cf51d664cb0bb5708d6618cc471%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636803654552259597&sdata=5q6%2FyeITD9Lu2T34gKwYGbo7IyGUQOhfaBH0Wg3aiAA%3D&reserved=0>
>>  
>> No guarantees that will fix your issue, but at least we can eliminate some 
>> possibilities.
>>  
>> HTH,
>> -Alex
>>  
>> From: mrchnk <[email protected] <mailto:[email protected]>>
>> Reply-To: "[email protected] <mailto:[email protected]>" 
>> <[email protected] <mailto:[email protected]>>
>> Date: Thursday, December 13, 2018 at 10:34 AM
>> To: "[email protected] <mailto:[email protected]>" 
>> <[email protected] <mailto:[email protected]>>
>> Subject: Linkage problem for asjs compiler
>>  
>> Greetings! 
>>  
>> I tried to compile a large project using npm distribution of Apache Royale 
>> asjs compiler (@apache-royale/[email protected]). I changed all flash.* 
>> classes to openfl.*. After several hotfixes that project starts to compile.
>>  
>> Here is index.html generated: 
>> https://gist.github.com/mrchnk/4f468d1abb1b02466a0dad43265c4333 
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Fmrchnk%2F4f468d1abb1b02466a0dad43265c4333&data=02%7C01%7Caharui%40adobe.com%7C3bac7cf51d664cb0bb5708d6618cc471%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636803654552269606&sdata=bpozs6vp91IjwOkJvdsZydxn0hXbECl9rNBCyj51tkQ%3D&reserved=0>
>>  
>> The page is loaded with javascript errors:
>> Uncaught Error: Undefined nameToPath for Client
>>     at visitNode (base.js:1356)
>>     at visitNode (base.js:1354)
>>     at Object.goog.writeScripts_ (base.js:1368)
>>     at Object.goog.require (base.js:705)
>>     at (index):1681
>>  
>> (index):1687 Uncaught ReferenceError: OasisHTML5Launcher is not defined
>>     at (index):1687
>>  
>> So Client.as is the superclass of OasisClient.as and is used in main 
>> OasisHTML5Launcher.
>> It is successfully compiled to Client.js and declared as a dependency at 
>> index.html
>> But a link to js file and declaration for that class is missing (I mean 
>> "goog.addDependency('../../../Client.as' ... )")
>>  
>> So how to deal with that? Is it a Royale bug? Are there some guidelines I 
>> missed about my code?
>>  
>> Thanks in advance.
>>  
>> PS: I'm kinda new to mailing lists. So don't hesitate to correct me if I do 
>> something wrong.

Reply via email to