Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing .swc's within a Flex Library Project
    text
    copied!<p>I'm trying to set up a production environment for about 10 related assets. Certain elements, visual and otherwise, are going to be shared between the 10 assets. I'm treating each one as its own Pure AS3 project in Flash Builder 4. </p> <p>Each asset has an associated .fla which is outputting a .swc into the libs folder for that asset - the final compilation is going to be done via ant, and the top-level source is the main .as file in each Flash Builder project.</p> <p>Because certain elements are shared between multiple assets, I've created a Flex Library Project in my workspace. This library project has a /src folder with a standard structure, as well as a /lib/ folder in which I'm sticking, for instance, greensock's TweenLite.</p> <p>In addition to the source code and third-party .swc, the Library project also has an FLA which exports a .swc into the /lib/ folder.</p> <p>Here's the problem: I'm not able to see library exports from that .swc in my related projects. In theory, every class I export from the library of the Flex Library Project's .fla should be compiled into the library project's .swc. I'm finding that this is not the case, and I'm not clear why.</p> <p>I'm going to continue digging, but I wanted to throw this up here in case anyone else has run into these issues. Anyone know what I'm doing wrong?</p> <p>EDIT: So apparently my greensock .swc isn't being compiled into the final output either. Yesterday it was. I'm not sure what has changed. I guess my question, distilled down, is this: how can I make sure that .swc files included in the build path for my Flex Library Project have all of their classes included in the final .swc that the FLP generates?</p> <p>EDIT2: I've discovered a sort of a terrible workaround. Right now I've created a single class in my src folder and I'm declaring anything that I want included from any of my .swc's - so for instance, public var tweenLite:TweenLite, public var logo:Logo, etc. I find that if I declare it in one of my source files then I'm able to access it in a related project. Importing it alone is not enough - this means that I would have to manually declare every class I want access to. There must be a better way. What am I missing?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload