On Fri, Jun 18, 2010 at 5:50 AM, P T Withington <[email protected]>wrote:
> I'm here. > > I think the right solution is that the compiler needs to notice the > external includes (whether from the main app or from an lzo) and emit the > class files for them. Then it calls the flex compiler with all those > classes and the lzo swc. I hope the swc can link against straight up class > files and that it is not limited to linking against another swc? > yes, it can link against the source files if they are sitting there. > > If you did not have lzos in the picture, every referenced class (whether in > the components or the webtop sdk) would get written out and then you would > call the flex compiler. All that should change in the lzo case is that the > classes in the webtop sdk are in a swc instead of separate class files. So, > I'm thinking some accounting must have gotten lost in the lzo? Normally the > lzo lists the external includes it needs and the compiler automatically > picks those up and emits the respecitive classes. Maybe the code path that > notices the swc is skipping the step of noticing the external includes in > the lzo header? > I'll check and see what it is doing with the external classes in the lzx phase of the compiler. > > On 2010-06-18, at 01:08, Henry Minsky wrote: > > > I need to discuss with you how to best get the webtop lzo's to work for > > swf10, given that they are trying to > > reference stuff out of the components/lz tree. > > > > Im going to try again to compile both lz/* and base/* into a single swf10 > > lzo file (which will make a .swc library file inside it). > > Theoretically they should be able to just compile their library then. > > > > If for some reason we have a problem making an lzo out of the whole > > components set, I'm wondering if we want to have the compiler emit as3 > > files for every class it sees in any external <include> files (i.e., > sutff > > inlcluded from outside of the library home directory). > > That way when the flex compc library compiler runs, it will have all the > > class definitions to link against. > > > > > > > > > > > > > > -- > > Henry Minsky > > Software Architect > > [email protected] > > -- Henry Minsky Software Architect [email protected]
