Well, I'm developing a library which depends on other third-party libraries. Of course, I just have a "thirdparty" directory in the source tree, and add those swcs to the library path, but the libs directory in an application project is certainly convenient.
In applications that use my library, I also just reference my library project directly from application projects that use it. It was the external library case I was referring to. On Wed, Dec 9, 2009 at 7:11 PM, Romeo Obane <[email protected]> wrote: > > > Guess because you're already in a Flex Library Project :) > > Honestly in my practice, I just delete the "libs" folder and directly > referring to my Library Project. > > > On Thu, Dec 10, 2009 at 7:50 AM, Richard Rodseth <[email protected]>wrote: > >> >> >> Any particular reason that a Flex library project can't have a "libs" >> folder the way an application project can? >> > > >
