I was attempting to set it up so that I could just always have a fresh trunk build to include in other projects, but on second thought, maybe it would be better to just use the binary releases, and do the whole SVN library thing for my own internal libraries.
I'm still new to SVN, and eclipse in general, so these were really just some novice questions I guess. I'll figure them out. Thanks, :-) Kevin N. Mike Chambers wrote: > Can you give me an example of one of the apps your are trying to compile? > > Basically: > > 1. create a new flex project pointing to the directory th atcontains the > root of the source for the app > 2. link in (either source, or SWCs) needed to compile the app. If you > link in the source, you want to point to the directory that contains the > "com" directory. > > mike chambers > > [EMAIL PROTECTED] > > Kevin Newman wrote: > >> Hello, >> >> I have been playing with various of the classes stored in SVN at >> http://labs.adobe.com/subversion/flashplatform, >> <http://labs.adobe.com/subversion/flashplatform,> and have some questions >> about what is the best way to check those out, to build them. >> >> So far I have been checking out the trunk of each project (corelib, >> xmlsyndication, flexunit, xmpp, etc.) as a separate Flex Library Project >> using Subclipse. Then I set (what I think are) the appropriate classes >> (all of them?), source paths (src/actionscript3) and library paths >> (other Flex Library Projects) in the properties window (under build >> path) in Flex Builder 2, and have been able to get these to build swc files. >> >> Is that the best way to do this? While I am able to get the swcs, I am >> not able to compile the test applications from within Flex Builder 2 - >> is there a way to do that? >> >> Any help or pointers are appreciated. >> >> Thanks, >> >> Kevin N. >>
