Well, I think I was able to reproduce your problem. Falcon is looking for
env.properties in a different place and doesn’t use the arg value passéd
in.
I pushed a change to Falcon to fix that. So pull changes to flex-falcon
before trying again and run “ant all”. You may need to add the
<arg value="+env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}”
to other build.xml files although the build now passes for me with what I
think your set up is.
-Alex
On 10/21/15, 1:44 PM, "Harbs" <[email protected]> wrote:
>OK. I’m calling it a night.
>
>Hopefully, I’ll have more success with this tomorrow.
>
>Harbs
>
>On Oct 21, 2015, at 11:41 PM, Alex Harui <[email protected]> wrote:
>
>>
>>
>> On 10/21/15, 1:37 PM, "Harbs" <[email protected]> wrote:
>>
>>> No joy.
>>>
>>> I made this change in that file:
>>> <compc fork="true"
>>> output="${FLEXJS_HOME}/frameworks/libs/Core.swc">
>>> <jvmarg line="${compc.jvm.args}"/>
>>> <load-config filename="compile-config.xml" />
>>> <arg value="+env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}"
>>> />
>>> <arg value="+playerglobal.version=${playerglobal.version}" />
>>> <arg value="+env.AIR_HOME=${env.AIR_HOME}" />
>>> </compc>
>>>
>>>
>>> I’m really confused about where that is defined. The only place I see
>>>it
>>> would be in flex-asjs/installer.xml:
>>
>> I think they are magic tokens in the compiler code. I will try to
>> re-create your scenario.
>>
>> -Alex
>>
>
