What exactly happens when it fails?
Here's a snippet from my build script. It looks pretty similar (other than
compiling for Flex rather than Royale).
<java jar="${compc}" dir="${flextoolbox.path}" fork="true"
failonerror="true">
<arg line="+flexlib='${flexframework.root}'"/>
<arg line="+configname=air"/>
<arg line="--namespace+=${flextoolbox.namespace},manifest.xml"/>
<arg line="--source-path+='source'"/>
<arg line="--include-namespaces+=${flextoolbox.namespace}"/>
<arg line="--include-sources+='source'"/>
<arg line="--include-stylesheet defaults.css source/defaults.css"/>
<arg line="--external-library-path+='${flexframework.lib}'"/>
<arg line="--external-library-path+='${flexair.lib}'"/>
<arg line="--external-library-path+='${flexmx.lib}'"/>
<arg line="--external-library-path+='${library.output}'"/>
<arg line="--swf-version=${swfversion}"/>
<arg line="--output '${library.output}/flextoolbox.swc'"/>
</java>
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Tue, Sep 22, 2020 at 11:07 AM Yishay Weiss <[email protected]>
wrote:
> Maybe you can share some of your source? This is my ant test project
> which fails.
>
> Thanks.
>
> <project name="MyProject" default="compile" basedir=".">
> <description>
> simple example build file
> </description>
>
> <target name="compile">
> <java jar="c:/dev/flexjs/royale-asjs/lib/compc.jar" fork="true">
> <jvmarg value="-Xmx384m" />
> <jvmarg value="-Dsun.io.useCanonCaches=false" />
> <jvmarg
> value="-Droyalelib=c:/dev/flexjs/royale-asjs/frameworks" />
> <arg value="+configname=flex"/>
> <arg
> value="+royalelib=c:/dev/flexjs/royale-asjs/frameworks"/>
> <arg
> value="-load-config=${basedir}/royale-config.xml"/>
> <arg value="-include-classes=MyClass"/>
> <arg value="-output=My.swc"/>
> <arg value="-source-path=src"/>
> </java>
> </target>
> </project>
>
> <!-- C:\dev\flexjs\royale-asjs\bin\compc.bat "-output=My.swc"
> "-source-path=src" "-include-classes=MyClass" "+configname=flex" -->
>
> From: Josh Tynjala<mailto:[email protected]>
> Sent: Tuesday, September 22, 2020 8:06 PM
> To: Apache Royale Development<mailto:[email protected]>
> Subject: Re: compc - configname
>
> Hmmm... interestingly that's exactly how I was using it.
>
> <arg line="+configname=air"/>
>
> It's possible that the order matters with options with the + character. Try
> to put it before all regular options that start with the - character.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Sep 22, 2020 at 9:40 AM Yishay Weiss <[email protected]>
> wrote:
>
> > Ok, I can confirm adding +configname=flex on the command line does the
> > trick. Now I need to understand why adding <arg
> value=”+configname=flex”/>
> > to
> > <java jar=”…/lib/compc.jar” fork=”true”> doesn’t work in ant...
> >
> >
> > From: Josh Tynjala<mailto:[email protected]>
> > Sent: Tuesday, September 22, 2020 6:43 PM
> > To: Apache Royale Development<mailto:[email protected]>
> > Subject: Re: compc - configname
> >
> > It should be possible to specify +configname=flex with both mxmlc and
> > compc.
> >
> > I just found the build script for an old Flex SWC of mine that uses
> > +configname=air, so if the Royale compc doesn't also support +configname,
> > it's a bug.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Sep 22, 2020 at 7:54 AM Yishay Weiss <[email protected]>
> > wrote:
> >
> > > Hi,
> > >
> > > I can’t figure out how to add configname=flex to compc. Any pointers?
> My
> > > goal is to compile a library that relies on emulation components.
> > >
> > > Thanks.
> > >
> > >
> >
> >
>
>
