So, something like this is valid?
<compc
output="${DEPLOY_DIR}/MyComponents.swc"
>
<include-sources dir="${basedir}/components/controls"
includes="*.mxml"/>
<source-path path-element="${basedir}/components/"/>
<directory>true</directory>
</compc>
And both .as files and .mxml files should be included in the library
correct? I am breaking them out into smaller libraries, like you
mentioned.
Thanks.
--- In [email protected], Paul J DeCoursey <[EMAIL PROTECTED]> wrote:
>
> I've been doing this same thing. Are you using the ANT Tasks from the
> Labs? I've found that it works better to break it up into separate
> libraries. Then I use the depends and uptodate options so I don't
> compile unless something has changed. If you are using the ANT tasks
> from the labs you should be able to use filesets with wildcards
(**/*.as
> and **/*.mxml) to catch all the files you need. We are not using the
> ANT Tasks ourseleves but we plan on migrating soon. For now we use
java
> tasks and pass in the jars for the specific compiler, and then we need
> to explicitly set each file we want included in the swc.
>
> pd
>
>
> alehrens wrote:
> >
> > Hi,
> >
> > I'm tinkering with using Ant for our flex build... We have two
> > libraries that contain a good amount of files (say, 25 .as file and 20
> > .mxml files for this example).
> >
> > My questions are:
> >
> > 1. Do I include both types of files in the compc task - to build
> > everything in our library into one .swc?
> > 2. Is there any way to wildcard it or do I have to specify every file
> > out explicitly?
> >
> > aaron
> >
> >
>
