Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
> > Unfortunately, I started the refactoring to make Flex SDK optional > yesterday and don't really want to revert everything or set up another > Eclipse workspace. It will be several days until I get Eclipse working > again, and hopefully it will make this issue go away for future Eclipse >

Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
Alex, I guess it's just you and me? It appears some tests expect the 'old' Flex SDK in FLEX_HOME, while others expect 'royale-asjs'. That's one thing. Another is that the SWC tests are all failing for me, again it seems on assumptions that are no longer valid after the fork and rename. Thanks,

Re: Eclipse Run configuration setup

2017-11-08 Thread Harbs
Sorry that’s above my pay grade. One day I hope to get the project setup in Eclipse and get my feet wet, but I’ve not gotten there yet… Good luck! Harbs > On Nov 8, 2017, at 1:31 PM, Erik de Bruin wrote: > > Harbs, > > Are you talking about the 'ant' build succeeding or

Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
Harbs, Are you talking about the 'ant' build succeeding or about running the tests on the compiler project in Eclipse? Because the ant build succeeds even if a bunch of tests fail, while running the tests in Eclipse will show all errors and failures. Thanks, EdB On Wed, Nov 8, 2017 at

Re: Eclipse Run configuration setup

2017-11-08 Thread Harbs
You need ROYALE_HOME for the royale-asjs repo. The new environment var for the compiler is: ROYALE_COMPILER_REPO I’m pretty sure those are the only two you need. FWIW, my script to set my env vars looks like this (although much of it is probably no longer needed or correct). #!/bin/sh export