Re: ***UNCHECKED*** Re: Trouble building compiler

2018-10-28 Thread Carlos Rovira
Hi, I think I'm suffering this problem now. Today make "ant all" as always and unexpectedly the process fail very soon trying to build the compiler. I check this thread and commented environment vars related to FLASH_PLAYER #export PLAYERGLOBAL_HOME=~/Dev/Flash/Player #export

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-08-06 Thread Harbs
Interesting. My variables are set without quotes, but I am escaping the spaces. I’m pretty sure that’s necessary in a shell script. > On Aug 6, 2018, at 6:07 AM, Alex Harui wrote: > > FWIW, I ran into the same or similar problem today. For me, quotes around > the entry in env.properties: >

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-08-05 Thread Alex Harui
FWIW, I ran into the same or similar problem today. For me, quotes around the entry in env.properties: FLASHPLAYER_DEBUGGER='/Users/aharui/adobe/flashplayer/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger' Resulted in the FLASHPLAYER_DEBUGGER not being found and the tests

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-07-26 Thread Alex Harui
In general, if "ant all" fails in the compiler, try running "ant" directly in royale-compiler. Same for royale-typedefs. HTH, -Alex On 7/26/18, 2:00 AM, "Harbs" wrote: I’m running ant all from royale-asjs. I’m not sure when I’m going to have the time to work on this, but I’ll

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-07-26 Thread Harbs
I’m running ant all from royale-asjs. I’m not sure when I’m going to have the time to work on this, but I’ll look into it more when I do… > On Jul 26, 2018, at 10:35 AM, Alex Harui wrote: > > If you don't get errors in the output for compiling the Date tests without > the Flash variables,

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-07-25 Thread Alex Harui
I took a closer look. If you are getting ASDateTest failures, you will need to open compiler/target/junit-reports/TEST-as.ASDateTests.xml and see what the failure is. The compile errors in the output are expected and should not cause test failures. If you are having a problem with

Re: ***UNCHECKED*** Re: Trouble building compiler

2018-07-25 Thread Harbs
I rolled back royale-typedefs to before the Date changes to enable my compilation. It does seem to me like we need to figure this out though… Harbs > On Jul 25, 2018, at 9:59 AM, Harbs wrote: > > I tried without environment vars and that might have made a difference. I’ > using these

***UNCHECKED*** Re: Trouble building compiler

2018-07-25 Thread Harbs
I tried without environment vars and that might have made a difference. I’ using these normally: export ROYALE_COMPILER_REPO=/Apache/royale-compiler export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player export

Re: Trouble building compiler

2018-07-25 Thread Harbs
Weird. I ran ant all again and it’s no longer getting this error, but it’s failing again on the Date tests (4 failures). > On Jul 25, 2018, at 9:43 AM, Harbs wrote: > > Yes I did, but it looks like that does not clear the files in the typedefs > repo. > > I just manually deleted all the

Re: Trouble building compiler

2018-07-25 Thread Harbs
Yes I did, but it looks like that does not clear the files in the typedefs repo. I just manually deleted all the target folders in typedefs and now I’m getting a new error: externc: [java] Unknown tag:field-readonly [java] 0.362347459 seconds [java]

Re: Trouble building compiler

2018-07-24 Thread Alex Harui
Did you run "ant wipe-all" in royale-compiler? On 7/24/18, 10:47 AM, "Harbs" wrote: I’m currently getting the following errors:

Trouble building compiler

2018-07-24 Thread Harbs
I’m currently getting the following errors: https://paste.apache.org/3Wpg It looks like the Date tests are causing problems. Any ideas why? Harbs