ok, I used a javascsript script to create the manifest file. Now
however when I run the compc command I am getting errors on all the
embedded images:
FileName.as(72): col: 6: Error: unable to resolve /path/to/image.png'
for transcoding
[Embed(source='path/to/image.png')]
I tried using the -include-file fileName
/src/resources/images/fileName.png command but it is still giving this
error.
Any ideas on how to include embedded images in compc?
--- In [email protected], "Bjorn Schultheiss"
<[EMAIL PROTECTED]> wrote:
>
> Automation of the manifest is a nice feature request..
>
> Hopefully we can get it into FB4.
>
> Has anyone logged it yet?
>
>
>
> --- In [email protected], Maciek Sakrejda <msakrejda@> wrote:
> >
> > I don't think that this is a compc issue: if memory serves (from a
> > couple of months ago when I looked at the source), the compc ant task
> > just calls out to the command line compc compiler. The limits are
in the
> > OS's command line length...
> > --
> > Maciek Sakrejda
> > Truviso, Inc.
> > http://www.truviso.com
> >
> > -----Original Message-----
> > From: Gordon Smith <gosmith@>
> > Reply-To: [email protected]
> > To: [email protected]
> > Subject: RE: [flexcoders] Re: compc and manifest file
> > Date: Tue, 29 Apr 2008 15:23:45 -0700
> >
> > > 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: [email protected]
[mailto:[EMAIL PROTECTED] On
> > Behalf Of mt1_18
> > Sent: Tuesday, April 29, 2008 12:34 PM
> > To: [email protected]
> > 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 [email protected], "mt1_18" <mt1_18@> 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
> > >
> >
>
