> it seems that there is a maximum number of *.as or *.mxml > files that can be passed in to the compc command
There shouldn't be. Can you please file a bug on this? > how would I automate the creation of the manifest file? > I dont want to update it each time I create a new file. Sorry, Flex doesn't provide any scripts for automatically generating a manifest. The SDK team maintains our manifests by hand and hasn't find it enough of a burden to bother automating the process. But a manifest has a simple format and you should be able to generate one based on a directory enumeration. You can use Perl, Python, or whatever your favorite scripting language is, and call your script using Ant's <exec> task. Gordon Smith Adobe Flex SDK Team ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of mt1_18 Sent: Tuesday, April 29, 2008 12:34 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: compc and manifest file sorry I meant to say that I am trying to use "ant and compc" not "and and compc" :) --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "mt1_18" <[EMAIL PROTECTED]> wrote: > > I am trying to use and and compc to compile my swc. However, compc > only takes a list of files and not a directory. So I did something > like this hoping it would work: > <compc output="framework.swc"> > <include-sources dir="${FRAMEWORK_ROOT}" > includes="**/*.as **/*.mxml" /> > <source-path path-element="${FRAMEWORK_ROOT}"/> > </compc> > > However it seems that there is a maximum number of *.as or *.mxml > files that can be passed in to the compc command. So from my research > it seems that I need to create a manifest file. But how would I > automate the creation of the manifest file? I dont want to update it > each time I create a new file. I am not too familiar with ant so any > guidance would help. > > Thanks >
