My PLAYERGLOBAL_HOME does not point inside a flex-sdk repo. It really shouldn't. We allowed it because some folks wanted to point to an Apache Flex IDE configuration, but Apache Flex works fine when developing without an IDE by pointing PLAYERGLOBAL_HOME elsewhere. And that's safer since you won't accidentally commit non-Apache bits.
In Royale, I think we need to change the build to not need a flex-sdk repo at all and treat Apache Flex as an upstream dependency and work from the latest releases. My 2 cents, -Alex On 9/28/17, 8:45 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> >> That path to playerglobal should not be in flex-sdk. > > >I was talking about the path in the PLAYERGLOBAL_HOME environment >variable. >That must point to the Flex SDK directory, but in the current procedure in >the READme, that doesn't exist yet. I'm rewriting the READme (and adding >helper targets in build.xml) to make the task of a dev-ready Royale >install a bit more streamlined. > >EdB > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. >https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data= >02%7C01%7C%7C698eeb29b0384082767f08d506880e57%7Cfa7b1b5a7b34438794aed2c178 >decee1%7C0%7C0%7C636422103789712683&sdata=7V8hdN06uzMXy2Bgrmgt9wWmL%2Fig%2 >BMYTwGtsRKXPYbs%3D&reserved=0
