You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2016/07/14 10:30:36 UTC
[ASJS][Falcon] Things I found regarding the distribution
Hi,
here some things I noticed while building the Maven distribution module:
- It seems that the debugger and the flex-compiler-oem require the swfutils.jar but this doesn't seem to be bundled in the official "nightly" distribution.
- The debugger seems to have a dependency on the closure-compiler, but that is also not bundled in the nightly
- There seems to be a directory "framework/externs" which contains SWCs without the "JS" suffix but the size doesn't match that of the normal Binding.swc in "framework/libs" or the JS version ... so I have no Idea what this is.
- Where does the Halo theme come from? It doesn't seem to be copied as the swc contains a "js" directory.
Well it's my plan to make the distribution produce a minimal something you can define as FDK directory in IntelliJ (or Eclipse) and have it compile.
Chris
AW: [ASJS][Falcon] Things I found regarding the distribution
Posted by Christofer Dutz <ch...@c-ware.de>.
Argh!
Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------
Von: Josh Tynjala <jo...@gmail.com>
Datum: 14.07.16 16:54 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [ASJS][Falcon] Things I found regarding the distribution
I can see in installer.xml, Halo.swc is simply a copy of Binding.swc. This
might seem weird, but Flash Builder requires frameworks/themes/Halo.swc to
exist to consider something a valid Flex SDK. It looks like someone just
chose a SWC at random to trick Flash Builder.
- Josh
On Thu, Jul 14, 2016 at 3:30 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi,
>
>
> here some things I noticed while building the Maven distribution module:
>
> - It seems that the debugger and the flex-compiler-oem require the
> swfutils.jar but this doesn't seem to be bundled in the official "nightly"
> distribution.
>
> - The debugger seems to have a dependency on the closure-compiler, but
> that is also not bundled in the nightly
>
> - There seems to be a directory "framework/externs" which contains SWCs
> without the "JS" suffix but the size doesn't match that of the normal
> Binding.swc in "framework/libs" or the JS version ... so I have no Idea
> what this is.
>
> - Where does the Halo theme come from? It doesn't seem to be copied as the
> swc contains a "js" directory.
>
>
> Well it's my plan to make the distribution produce a minimal something you
> can define as FDK directory in IntelliJ (or Eclipse) and have it compile.
>
>
> Chris
>
>
Re: [ASJS][Falcon] Things I found regarding the distribution
Posted by Alex Harui <ah...@adobe.com>.
On 7/14/16, 7:53 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
>I can see in installer.xml, Halo.swc is simply a copy of Binding.swc. This
>might seem weird, but Flash Builder requires frameworks/themes/Halo.swc to
>exist to consider something a valid Flex SDK. It looks like someone just
>chose a SWC at random to trick Flash Builder.
Yep, there are tricks for the various IDEs. Shouldn't be necessary for a
Maven build.
>On Thu, Jul 14, 2016 at 3:30 AM, Christofer Dutz
><ch...@c-ware.de>
>wrote:
>
>> Hi,
>>
>>
>> here some things I noticed while building the Maven distribution module:
>>
>> - It seems that the debugger and the flex-compiler-oem require the
>> swfutils.jar but this doesn't seem to be bundled in the official
>>"nightly"
>> distribution.
I don't see any mention of swfutils.jar in the ant build.xml for debugger
and flex-compiler-oem. Instead, we copy in the subset of the source of
swfutils from the flex-sdk.
>>
>> - The debugger seems to have a dependency on the closure-compiler, but
>> that is also not bundled in the nightly
The word "closure" or "goog" isn't in the build.xml for the debugger.
What are you seeing? The debugger does call the Flex/FlexJS compiler in
order to handle the print command.
>>
>> - There seems to be a directory "framework/externs" which contains SWCs
>> without the "JS" suffix but the size doesn't match that of the normal
>> Binding.swc in "framework/libs" or the JS version ... so I have no Idea
>> what this is.
Old Ant builds created a frameworks/externs folder. I don't have one in
my repo.
>>
>> Well it's my plan to make the distribution produce a minimal something
>>you
>> can define as FDK directory in IntelliJ (or Eclipse) and have it
>>compile.
For IntelliJ, there might be a few manifest.xml files IJ expects as well.
HTH,
-Alex
Re: [ASJS][Falcon] Things I found regarding the distribution
Posted by Josh Tynjala <jo...@gmail.com>.
I can see in installer.xml, Halo.swc is simply a copy of Binding.swc. This
might seem weird, but Flash Builder requires frameworks/themes/Halo.swc to
exist to consider something a valid Flex SDK. It looks like someone just
chose a SWC at random to trick Flash Builder.
- Josh
On Thu, Jul 14, 2016 at 3:30 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi,
>
>
> here some things I noticed while building the Maven distribution module:
>
> - It seems that the debugger and the flex-compiler-oem require the
> swfutils.jar but this doesn't seem to be bundled in the official "nightly"
> distribution.
>
> - The debugger seems to have a dependency on the closure-compiler, but
> that is also not bundled in the nightly
>
> - There seems to be a directory "framework/externs" which contains SWCs
> without the "JS" suffix but the size doesn't match that of the normal
> Binding.swc in "framework/libs" or the JS version ... so I have no Idea
> what this is.
>
> - Where does the Halo theme come from? It doesn't seem to be copied as the
> swc contains a "js" directory.
>
>
> Well it's my plan to make the distribution produce a minimal something you
> can define as FDK directory in IntelliJ (or Eclipse) and have it compile.
>
>
> Chris
>
>