This went over my head a bit. Currently, when I build Royale (withs wf support), I rsync a “player” folder which has playerglobal.swc into frameworks/libs to allow it to be used for compiling applications. I’m looking to get rid of that step and I’m not sure how we can facilitate that.
Harbs > On May 4, 2023, at 8:53 PM, Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: > > There's a swf.distribution Ant property that normally gets managed > automatically. It get set to true when AIR_HOME is available, and false > when AIR_HOME is not available. The availability of AIR_HOME (and > PLAYERGLOBAL_HOME) is normally how the Ant build determines that it needs > to build a SWF/JS distribution instead of a JS-only distribution. > > As I recall, you can manually enable it with -Dswf.distribution=1 on the > command line (or you can set it in env.properties, if you prefer), and this > will force a SWF/JS distribution even when PLAYERGLOBAL_HOME and AIR_HOME > are not set. When swf.distribution is set, but PLAYERGLOBAL_HOME and > AIR_HOME are not set, it should look for the royale-typedefs versions of > playerglobal.swc and airglobal.swc instead of the Adobe versions. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > > On Thu, May 4, 2023 at 12:20 AM Gabe Harbs <harbs.li...@gmail.com> wrote: > >> What’s the status to compiling player global? I remember Josh doing work >> on creating our own version of player global so we wouldn’t have to rely on >> the downloads from Adobe. >> >> It does not seem to be added as part of the build process. Is there a >> reason why not? >> >> Thanks, >> Harbs
