What happens if you don't specify js-output-type? In theory it should pick FlexJS.
The output looks like it is calling the SWF compiler, not the cross-compiler. -Alex On 5/17/16, 8:30 AM, "Harbs" <[email protected]> wrote: >Here’s the output I’m getting: > >Using: Flex SDK Compiler >Adapter: Flex SDK 4 Compiler Adapter >Starting Full Build of TreeTest-MainModel. >Compiler arguments: > -output > /Users/harbs/Documents/FDT/workspace/TreeTest/bin/TreeTest.swf > +flexlib= > /Users/harbs/Documents/Apache Flex > Dist/FlexJS Nightly/frameworks > --compiler.debug=true > --debug-password= > --compiler.source-path+= > /Users/harbs/Documents/FDT/workspace/TreeTest/src > --compiler.library-path+= > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/player/14.0/playerglobal.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Binding.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Charts.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Collections.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Core.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/DragDrop.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Effects.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Flat.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Formatters.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Graphics.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/HTML.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/HTML5.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Network.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Reflection.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/Storage.swc, > /Users/harbs/Documents/Apache Flex > Dist/FlexJS > Nightly/frameworks/libs/XML.swc > -js-output-type=FlexJS > -compiler.mxml.children-as-data=true > -compiler.binding-value-change-event= > org.apache.flex.events.ValueChangeEvent > -compiler.binding-value-change-event-kind= > org.apache.flex.events.ValueChangeEvent > -compiler.binding-value-change-event-type= > valueChange > -target-player=14.0 > -define=CONFIG::AUTHOR,"harbs" > -define=CONFIG::DEBUG,true > -static-link-runtime-shared-libraries= > true > -- > /Users/harbs/Documents/FDT/workspace/TreeTest/src/TreeTest.mxml > >ERROR Unknown configuration variable 'js-output-type'. > >Pure build time: 48 ms. >Could not create file >/Users/harbs/Documents/FDT/workspace/TreeTest/bin/TreeTest.swf. >Build failed. > >On May 17, 2016, at 6:09 PM, Alex Harui <[email protected]> wrote: > >> >> >> 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.ev >>>en >>> ts.ValueChangeEvent</argument> >>> >>> >>> <argument>-compiler.binding-value-change-event-type=valueChange</argum >>>en >>> 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 >
