> Thinking about it some more, I think to build, for example, the Core.swc,
> we would run CompJSC with one set of settings (different -js-output-type,
> different library paths that point to a JS.swc and HTMLNative.swc) that
> would product JS files, then another run with CompJSC with a different set
> of settings (the ones it uses today) to cross-compile some other AS code
> to produce more JS files. Then somehow we want to compile all of the AS
> into a SWC with library.swf and catalog.xml. I guess chaining will help,
> but I’m thinking you’ll also want to run just one of the compilers as you
> fix bugs in certain areas.
It
is exactly what allows my new implementation, you can pass any valid
js-output-type or FLEXJS_DUAL, if FLEXJS_DUAL it will prepare phase1
only in case of COMPJSC for the compilation appening the output to have a
js/out structure, call COMPJSC, in case of success and FLEXJS_DUAL then
prepare phase2 (include the transpiled JS files, remove js-output-type)
and call COMPC, for the couple MXMLJSC / MXMLC, only chain the compiler
call and remove the js-output-type on phase2.
Does it sound enough ?
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [Falcon.jx] -library-path
> Date: Mon, 1 Jun 2015 22:24:39 +0000
>
>
>
> On 6/1/15, 3:04 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>
> >> BTW, assuming we’ll have Mike’s AS to JS compiler, the JS files will
> >>soon
> >> be generated by running a CompC like tool. I had thoughts of teaching
> >> CompJSC to stuff the JS files into the same swc specified by the -output
> >> option, but ran out of time.
> >
> >I would like to see that happening.
> >
> >1- I didn't follow totally the thread relative to what mike what doing,
> >do you mean it will do all the job that the COMPJSC does when converting
> >AS to JS ?
>
> Thinking about it some more, I think to build, for example, the Core.swc,
> we would run CompJSC with one set of settings (different -js-output-type,
> different library paths that point to a JS.swc and HTMLNative.swc) that
> would product JS files, then another run with CompJSC with a different set
> of settings (the ones it uses today) to cross-compile some other AS code
> to produce more JS files. Then somehow we want to compile all of the AS
> into a SWC with library.swf and catalog.xml. I guess chaining will help,
> but I’m thinking you’ll also want to run just one of the compilers as you
> fix bugs in certain areas.
>
>
> -Alex
>
