When you add libaries via Library Path, they are only compiled into the swf if they are used/referenced in your code. This keeps swf's smaller by only adding Flex code that is needed. For example, why compile into your swf the code for Advanced Data Grid if you never use it.
However, since you don't necessarily reference any of the automation api directly in your app, using the Library Path won't work, because it will be excluded from your swf. To get those automation libraries in there for an external swf to use, you use the "include-libraries" compiler option which ignores if a library is actually used in the code and includes the full library into the swf anyway. --- In [email protected], "shameer.forflex" <shameer.forf...@...> wrote: > > Hi All, > > I want to make a flex application testable using QTP. I am using the same > code for production and testing. In the project properties->Flex Build > Path->Library Path, the auto libs such as automation.swc, > automation_agent.swc etc are added(merged into code), the moment I create the > Project. But to associate the auto libs with the flex application, I have to > add them again as Compiler options or at run time. So can anyone please > explain me the difference between adding these libs in Flex Build > Path->Library Path and adding libraries as Flex Compiler options. > > Thanks, > Shameer >
