Sounds like a FALCON_HOME environment variable is pointing to a folder in a flex-falcon repo. It needs to point to the FlexJS SDK.
-Alex On 10/13/14, 6:11 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >Okay, I fixed that. It appears that FlexJS 0.0.2's js\bin\mxmlc.bat has a >hardcoded path to "C:\Windows\System32\java.exe". I replaced that with >"@java" and that error went away. > >Now, I am getting: >Using Falcon codebase: >C:\p\flexroot\git\flex-falcon\compiler\generated\dist\sdk >Using Flex SDK: C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 >Bit)\sdks\ApacheFlex4.13.0_AIR15_FP15 >Unable to access jarfile >C:\p\flexroot\git\flex-falcon\compiler\generated\dist\sdk\js\lib\mxmlc.jar > >There is no 'js' folder under flex-falcon\compiler\generated\dist\sdk\ > >When I looked inside js/bin/mxmlc.bat, there is a reference to >"%FALCON_HOME%\js\lib\mxmlc.jar" Again, no such path exists. > >I looked around, there is a "%FALCON_HOME%\lib\falcon-mxmlc.jar". So, I >fixed mxmlc.bat to point to this instead. > >Now, I am getting this error: > >command line >Error: unknown configuration variable 'js-output-type'. > >So, I removed this from mxmlc.bat. Now I get this: > >Using Falcon codebase: >C:\p\flexroot\git\flex-falcon\compiler\generated\dist\sdk >Using Flex SDK: C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 >Bit)\sdks\ApacheFlex4.13.0_AIR15_FP15 >using FlashBuilder Project Files >FlashBuilder settings: > -locale > en_US > -source-path+=C:\p\flexroot\git\flex-asjs\examples\FlexJSTest_SVG/src > -compiler.accessible=true > >-output=C:\p\flexroot\git\flex-asjs\examples\FlexJSTest_SVG/bin-release/Fl >exJSTest_SVG.swf > >-library-path+=C:\p\flexroot\git\flex-asjs\examples\FlexJSTest_SVG/libs > -library-path+=/FlexJSJX/bin/FlexJSJX.swc > -library-path+=/FlexJSUI/bin/FlexJSUI.swc > -sdk-js-lib=C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 >Bit)\sdks\ApacheFlex4.13.0_AIR15_FP15\frameworks\js\FlexJS\src > -fb > >C:\p\flexroot\git\flex-asjs\examples\FlexJSTest_SVG/src/FlexJSTest_SVG.mxm >l > >command line >Error: unknown configuration variable 'sdk-js-lib'. > >So, I removed this from mxmlc.bat. Now, I get this: > >Using Falcon codebase: >C:\p\flexroot\git\flex-falcon\compiler\generated\dist\sdk >Using Flex SDK: C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 >Bit)\sdks\ApacheFlex4.13.0_AIR15_FP15 >Apache Flex MXML and ActionScript Compiler (mxmlc) >Version 0.0.3 build 0 > >mxmlc [options] [defaultVar] >Use 'mxmlc -help' for more information. > > >That's it, no errors or anything. I do see a bin-debug directory for the >swf build, but no bin directory for the js-release and js-debug builds. > >I am out of ideas now. > >Thanks, >Om > > > >On Mon, Oct 13, 2014 at 5:42 PM, OmPrakash Muppirala ><bigosma...@gmail.com> >wrote: > >> I am setting up the FlexJS dev environment from scratch. I have run >>into >> a few compile issues so far. I have fixed them and checked them in. >> >> Now I am trying to build an app from Flash Builder. I have the project >> set up, pointing to a FlexJS installation version 0.0.2 which was >>installed >> using the Installer. Also, I have two project references to FlexJSUI >>and >> FlexJSJX. So far, so good. No compile errors. >> >> Now, I am trying to build the project using the external tool -> FlexJS >> (FalconJX Release and Debug Build). I am getting this error: >> >> Using Falcon codebase: >> C:\p\flexroot\git\flex-falcon\compiler\generated\dist\sdk >> Using Flex SDK: C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 >> Bit)\sdks\ApacheFlex4.13.0_AIR15_FP15 >> '"C:\Windows\System32\java.exe"' is not recognized as an internal or >> external command, >> operable program or batch file. >> >> I do have java installed, JAVA_HOME set and JAVA_HOME/bin added to PATH. >> Java seems to be working fine via the command prompt: >> >> C:\p\flexroot\git\flex-asjs\examples\FlexJSTest_SVG>java -version >> java version "1.8.0_20" >> Java(TM) SE Runtime Environment (build 1.8.0_20-b26) >> Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) >> >> Anyone has any idea what's going wrong? This used to work without >> problems in my earlier/similar set up. >> >> Thanks, >> Om >>
