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 <christofer.d...@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 > >
