Hi Kevin,
My recommended workflow for FlexJS is to build a SWF first and debug it
because the Flash Player VM and the IDE’s debugger should make that a
pretty fast edit/compile/debug cycle. So typically, you want to build the
SWF first by either integrating bin/mxmlc into the IDE or calling it
directly.
Then, once you think you’ve debugged your logic, you can take the longer
trip of cross-compiling your code by running js/bin/mxmlc.
So, for IntelliJ for now, you might need both.
FlashBuilder does not use bin/mxmlc so that’s probably why chmod is
needed. Feel free to file a bug and/or submit a patch to the install
script for that.
There might be a bug for how SCRIPT_HOME works in js/bin/mxmlc so if you
have a patch for that, that would be great as well.
Are you otherwise up and running?
Thanks,
-Alex
On 5/11/15, 4:33 AM, "kevin.godell" <kevin.god...@gmail.com> wrote:
>Thanks Alex. I had already installed the flexjs nightly and was trying to
>setup external tools on intellij. I was trying to mimic the launch config
>settings found in /ide/flashbuilder which was targeting sdk/js/bin/mxmlc.
>When running the external tool on intellij(after updating to java 1.7)
>there
>were complaints about not being able to access some files. So, I assumed
>that falcon was not included.
>
>The contents of the launch config found in /ide/flashbuilder:
><launchConfiguration
>type='org.eclipse.ui.externaltools.ProgramLaunchConfigurationType'>
><booleanAttribute key='org.eclipse.debug.core.appendEnvironmentVariables'
>value='false'/>
><listAttribute key='org.eclipse.debug.ui.favoriteGroups'>
><listEntry value='org.eclipse.ui.externaltools.launchGroup'/>
></listAttribute>
><stringAttribute
>key='org.eclipse.ui.externaltools.ATTR_LAUNCH_CONFIGURATION_BUILD_SCOPE'
>value='${project}'/>
><stringAttribute key='org.eclipse.ui.externaltools.ATTR_LOCATION'
>value='/Users/kevinGodell/Documents/flexjs0.0.3-nightly_air-17/js/bin/mxml
>c'/>
><stringAttribute key='org.eclipse.ui.externaltools.ATTR_TOOL_ARGUMENTS'
>value='-fb "${project_loc}"'/>
></launchConfiguration>
>
>When setting up an external tool, should I target /js/bin/mxmlc or
>/bin/mxmlc? I tried targeting /bin/mxmlc and had to chmod 744 the file
>because it did not have execute permissions and intellij could not run it.
>When I target /js/bin/mxmlc, I get warnings about some files not found:
>Error: Unable to access jarfile /../lib/mxmlc.jar
>
>I changed a little in the mxmlc to "$SCRIPT_HOME../lib/mxmlc.jar" from
>"$SCRIPT_HOME/../lib/mxmlc.jar" and the error warning went away.
>
>I guess the important thing that I need to clear up is which mxmlc
>location
>should I target, the one in /js/bin or in /bin?
>
>Thanks for the help.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/Falcon-FalconJX-insta
>llation-broken-tp41165p46398.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
