Justin,
On 5/10/12 7 :13PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>
>I not sure that an environment variable is the best to indicate the path
>to playerglobal.swc but it shoudl be placed in prescribed place in the
>SDK folder. Why? Well if you have multiple versions of the Apache SDK
>configured in Flash Builder which use different versions of
>playerglobal.swc it going to make life a little difficult.
I've been doing some FlashBuilder integration work for the FlashBuilder
team. I finally get what you are saying about the playerglobal version.
When you change the target version either thru the IDE or on the command
line, the path to playglobal.swc should automagically change. In
flex-config.xml, rather than the current entries which are
<external-library-path>
<path-element>{playerglobalHome}/playerglobal.swc</path-element>
</external-library-path>
<path-element>{playerglobalHome}</path-element>
the proper entries should be
<external-library-path>
<path-element>{playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMi
norVersion}/playerglobal.swc</path-element>
</external-library-path>
<path-element>{playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMi
norVersion}</path-element>
The compiler replaces playerglobalHome with PLAYERGLOBAL_HOME environment
variable (or with the change I am sitting on the env.PLAYERGLOBAL_HOME
property in env.properties) and it replaces
{targetPlayerMajorVersion} and {targetPlayerMinorVersion} with the
targetVersion.
I think I originally removed the version stuff because it is more
complicated to explain how the directory structure pointed to by
PLAYERGLOBAL_HOME is set up. Minimally you need playerglobal-dir/x.x
where x.x is the value of playerglobal.version in build.properties.
What do you think?
Carol
