And if you just use -output and not -js-output the bin folder will be where you specified -output, and if you specify -output=somefolder\somefile.swf the output will be in somefolder\bin.
The logic is trying to say: 1) If you specify -output as a SWF, we will use the parent folder of the SWF 2) If you specify -output as a folder, we will use that folder 3) If you specify -js-output, we will use that regardless of what you used for -output 4) If you didn't specify -output or -js-output then A) If you have a src folder or src/main/flex folder we will use the parent of src B) Otherwise we will use the parent folder of the main source file. I don't agree that CWD is the right default. For me, I've always had a folder full of test cases and am not always changing folders. I think the regular Flex MXMLC worked this way as well so I didn't want to change that pattern. 4A is just a convenience for those who follow certain common patterns so they don't have to do as much typing on the command line. It might also "do the right thing" for Flash Builder users. I think Maven always specifies the output folder. My 2 cents, -Alex On 6/1/17, 7:48 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >In that case, the SWF will use the -output option: > >mxmlc -output=path/to/MyProject.swf -js-output=. source/MyProject.as > >- Josh > >On Thu, Jun 1, 2017 at 7:30 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > >> Ahh..Ok now it is clear. What about if we have >> -compiler.targets=JSFLEX,SWF - >> So -js-output will be also the place where SWF file will landed? - If >>yes >> in >> that case this param could have different name. >> >> Thanks, >> Piotr >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: http://apache-flex- >> development.2333347.n4.nabble.com/FlexJS-Why-FlexJS- >> compiler-statically-looks-for-src-folder-tp61991p61997.html >> Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >>
