That instruction might indeed not be clear to everybody, although it states that the var should point to the player directory. I changed the text a bit to mention that the version should be left out:
"Set PLAYERGLOBAL_HOME to the absolute path of the player directory (not including the version subdirectory). The target-version option controls which PLAYERGLOBAL_HOME subdirectory is used." regards, Christophe 2012/6/5 Om <bigosma...@gmail.com> > Okay, I added the FLASHPLAYER_DEBUGGER to my env. variables list. I am not > using an env.properties file. > > I am getting an error very similar to Justin's error: > > basictests: > [mxmlc] Loading configuration file > C:\p\flex_os\workspace\ApacheFlex\frameworks\flex-config.xml > [mxmlc] > C:\p\flex_os\workspace\ApacheFlex\frameworks\flex-config.xml(62): Error: > unable to open > 'C:\p\flex_os\playerglobal\11.1/11.1/playerglobal.swc' > [mxmlc] > [mxmlc] </external-library-path> > [mxmlc] > [mxmlc] Loading configuration file > C:\p\flex_os\workspace\ApacheFlex\frameworks\tests\basicTests > \BasicTests-config.xml > [mxmlc] Apache Flex Compiler (mxmlc) > [mxmlc] Version 4.6.0 build 0 > [mxmlc] Copyright 2012 The Apache Software Foundation. > [mxmlc] > > BUILD FAILED > c:\p\flex_os\workspace\ApacheFlex\build.xml:1132: mxmlc task failed. > > Looks like PLAYERGLOBAL_HOME has an an unncessary /11.1 at its end. > Removing it fixed that problem for me. But according to the README: > > *3) The Adobe Flash Player playerglobal.swc for 11.1 can be downloaded > from: > > > http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_1.swc > > Use URL above to download playerglobal11_1.swc. Create the > directory, player/11.1 > and copy playerglobal11_1.swc to player/11.1/playerglobal.swc. > > Set PLAYERGLOBAL_HOME to the absolute path of the player directory. > The > target-version option controls which PLAYERGLOBAL_HOME subdirectory > is used. > > We might want to update the README to point PLAYERGLOBAL_HOME to not > include the /{majorversion}.{minorversion} > > On Tue, Jun 5, 2012 at 11:31 AM, Christophe Herreman < > christophe.herre...@gmail.com> wrote: > > > Hi, > > > > running the checkintests target works fine on my windows box. I'm using > > env.properties. > > > > regards, > > Christophe > > > > 2012/6/5 Justin Mclean <jus...@classsoftware.com> > > > > > Hi, > > > > > > > It ran for me last time I tried it. > > > It did for me as well but the build scripts have changed a little since > > > then. :-) > > > > > > What I'm trying to determine if it's just my environment that's not > > > correct configured (quite possibly I've changed something and > forgotten) > > or > > > if the build scripts have an issue. Once I know that I'll going to try > > and > > > get the checkin tests working as part of the Jenkins (on SVN checkin of > > any > > > changes to the SDK). > > > > > > Can anyone who has a clean checkout of the Apache Flex project with no > > > spaces in the path do an "ant checkintests" and see if it works. I'm on > > OSX > > > but if the build scripts have an issue you should get a similar error > on > > > OSX to what I did on windows. > > > > > > Thanks, > > > Justin > > > > > > > > > > -- > > Christophe Herreman > > http://www.herrodius.com > > http://www.springactionscript.org > > http://www.as3commons.org > > > -- Christophe Herreman http://www.herrodius.com http://www.springactionscript.org http://www.as3commons.org
