On 5/17/16, 8:02 AM, "Harbs" <[email protected]> wrote:
>Currently, these are the compiler arguments defined for FlexJS:
>
> <compilerArguments passClasspath="true" passMainclass="true"
>passSwcs="true" passRsls="false">
> <argument>-js-output-type=FlexJS</argument>
> <argument>-compiler.mxml.children-as-data=true</argument>
>
> <argument>-compiler.binding-value-change-event=org.apache.flex.events.Va
>lueChangeEvent</argument>
>
> <argument>-compiler.binding-value-change-event-kind=org.apache.flex.even
>ts.ValueChangeEvent</argument>
>
> <argument>-compiler.binding-value-change-event-type=valueChange</argumen
>t>
> <argument>-target-player={playerVersion}</argument>
> </compilerArguments>
>
>There’s quite a few other arguments defined in the ant scripts (and
>different ones for the different targets). I’m also not quite sure how to
>specify different arguments for debug and release builds.
>
>What’s the bare minimum needed in terms of arguments to get it to
>properly compile?
Well, that depends on how they launch the compiler. If they launch our
launch scripts, they shouldn't need to specify anything. If they launch
mxmlc.jar and pass in regular command-line options and it picks up our
flex-config.xml, they also shouldn't need to specify anything. Do you get
console output when they compile? Usually the compiler tells you which
-config.xml files it is using.
-Alex
