Hi Alex, thanks for that update ... I think I'll try with Mavenizing the "generated/sdk" directory and experiment a little with that. As Flashbuilder is able to, hopefully Flexmojos will also be able to work with falcon without any modification (I will have to update the checkers in Flexmojos though to allow a "compiler-falcon" artifact instead of insisting on "compiler", but that should take at most 5 minutes :-)
Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Sonntag, 13. Juli 2014 17:54 An: dev@flex.apache.org Betreff: Re: Mavenizing Falcon Gordon or Darrell might know the real answer. If you build the Falcon repo or unpack a binary package, you should see a compiler/lib folder. In it are the external dependencies require by the build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA. Pretty sure Jburg is need to build, but not to run. Pretty sure Commons-io and Commons-cli is need to run as well as LZMA. Not sure about Antr and Jflex. Might only be build tools. In generated/dist/sdk/lib are the jars that result from the build. They are: Compiler.jar Falcon-asc.jar Falcon-compc.jar Falcon-mxmlc.jar Falcon-optimizer.jar Falcon-swfdump.jar Flex-oem-compiler.jar Pretty sure you want the first 5, although really, I think falcon-asc, falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the optimizer works. The 5 jars can be moved into a lib folder with the compiler/lib jars so they are all in one place. You don't need falcon-swfdump unless you want to dump SWFs, and flex-oem-compiler.jar is only for FB integration. AFAIK, these jars do not have dependencies on the current Flex SDK. When we build up an overlaid SDK we move the current SDK compiler to a bin-legacy and lib-legacy folder, but that's just so folks can revert back if Falcon isn't working. Also, the old SWFDump is much better, IMO. HTH -Alex On 7/13/14 7:42 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > >After my latest Mavenizer and Flexmojos changes seem to compile all of >my Flex projects without problems, I wanted to get started on adding >Falcon support. >Now instead of re-deploying the entire compiler, I would much more like >to have the falcon-compiler depend on the normal compiler by >referencing the falcon libs and adding a dependency on the normal >compiler artifact and exclude the old compiler libs. > >Could someone here on the list please describe me exactly which libs >Falcon consists of and where I can get them from as well as which libs >in the classic sdk are needed? I think being able to switch the >compilers by changing a dependency in maven would make experimenting a lot >easier. > >Chris
