Apache flex 如何复制Flash Builder的功能'；ant中的发布工具？

我想构建一个ant脚本，它在Flash Builder 4（Gumbo）项目上执行与

project->Export Release build…

菜单项完全相同的编译操作。我的ant fu相当强大，这不是问题所在，但我不确定该条目到底在做什么

一些细节：

• 我将使用3.xsdk（为了明确起见，比如3.2）来构建它
• 我将在Mac上构建，我可以很高兴地使用ant、make或一些奇怪的shell脚本，如果你这样做的话
• 欢迎您提出任何有用的优化建议
• 该项目包含一些资产，MXML和actionscript源代码，以及几个内置到项目中的.swc（不是RSL'd）

---

有人能提供一个ant build.xml或makefle，用于从一个类似的Flex项目中构建一个release.swf文件吗？

不久前，我在Adobe Flex ant任务中遇到了一些问题，因此我使用了一个exec调用来调用mxmlc编译器，并提供了大量选项，我们就是从那里开始构建的。我对build.xml所做的与FB3（我们所拥有的）所做的并不完全相同，但这可能足以帮助您开始。。。您说您的ant fu相当强大，所以我将跳过大部分构建文件，让您将这些部分组合起来

<!--flex stuff-->
<property name="dir.flex.sdk"                 value="${system.build.flex.sdk}"/>
<property name="dir.flex.home"                value="${dir.abc}/flex/sdks/${dir.flex.sdk}"/>
<property name="dir.flex.projects"            value="${dir.abcd_plat}/webapp/flexprojects/"/>
<property name="dir.modules"                  value="${dir.war}/modules/"/>
<property name="FLEX_HOME"                    value="${dir.flex.home}"/>
<property name="APP_ROOT"                     value="${dir.war}"/>
<property name="flexc.exe"                    value="This should be set in the build-${os.family}.xml file"/>
<property name="asdoc.exe"                    value="This should be set in the build-${os.family}.xml file"/>
<property name="optimizer.exe"                value="This should be set in the build-${os.family}.xml file"/>
<property name="flex.mxmlc"                   value="${dir.flex.home}/bin/${flexc.exe}"/>
<property name="flex.compc"                   value="${dir.flex.home}/bin/${compc.exe}"/>
<property name="flex.asdoc"                   value="${dir.flex.home}/bin/${asdoc.exe}"/>
<property name="flex.optimizer"               value="${dir.flex.home}/bin/${optimizer.exe}"/>
<property name="flex.options.warnings"        value="false"/>
<!--options that are used in common for compiling all .swc and .swf files-->
<property name="flex.meta.1"                  value="-creator 'MyCorp.' -publisher 'MyCorp.'"/>
<property name="flex.meta.2"                  value="-title MegaProduct -description http://ourURL.com"/>
<property name="flex.meta.props"              value="${flex.meta.1} ${flex.meta.2}"/>
<property name="debug.options"                value="-optimize=true -debug=false"/>
<property name="common.flex"                  value="-as3 -target-player=9.0.124 -warnings=${flex.options.warnings}"/>
<property name="license.flex3"                value="(put your own here)"/>
<property name="common.fixed"                 value="-license=flexbuilder3,${license.flex3} -sp ${dir.war} -library-path+=${dir.webinf}/lib"/>
<property name="flex.common.args"             value="${flex.meta.props} ${debug.options} ${common.flex} ${common.fixed}"/>
<!--this is currently unused, but if we make a debug version, this can be set to make a separate output file-->
<property name="swf.suffix"                   value=""/>

<!--=================================================================================
    MACRODEFs
-->
<!--this is used to extract .swf files from 3rd party .swc libraries, in order to do dynamic linking-->
<macrodef name="extract-flex-lib" description="For modularizing flex compilation">
    <attribute name="swc-lib" default="NOT SET"/>

    <sequential>
        <!--use a copy task - it can get the file out of the zip, and rename it at the same time-->
        <copy todir="${dir.war}" preservelastmodified="true">
            <zipfileset src="${dir.webinf}/lib/@{swc-lib}.swc">
                <patternset>
                    <include name="library.swf"/>
                </patternset>
            </zipfileset>
            <mapper type="glob" from="library.swf" to="@{swc-lib}-debug.swf"/>
        </copy>
        <!--run the flex optimizer on the extracted .swf - note the as3 metadata that's kept, it's required-->
        <exec executable="${flex.optimizer}" failonerror="true">
            <arg line="-keep-as3-metadata='Bindable,Managed,ChangeEvent,NonCommittingChangeEvent,Transient'"/>
            <arg line="-input @{swc-lib}-debug.swf -output @{swc-lib}.swf"/>
        </exec>
        <!--delete the unoptimzed swf, don't need it anymore-->
        <delete file="@{swc-lib}-debug.swf"/>
    </sequential>
</macrodef>

<!--this is used to compile our internal flex modules-->
<macrodef name="flexc-mxml" description="For building the flex modules during flex compilation">
    <attribute name="name"        default=""/>
    <attribute name="mxml.args"   default="${flex.common.args} ${module.args}"/>
    <attribute name="sourcePath"  default=""/>
    <attribute name="destPath"    default=""/>

    <sequential>
        <echo message="  Compiling with mxmlc: @{name}"/>
        <exec executable="${flex.mxmlc}" failonerror="true">
            <arg line="@{mxml.args} @{sourcePath} -output @{destPath}"/>
        </exec>
    </sequential>
</macrodef>

<!--this is used to compile our subprojects under abcd_plat/webapp/flexprojects-->
<macrodef name="flexc-subproject" description="For compiling the flex subprojects into .swc files">
    <attribute name="name"        default=""/>
    <attribute name="xtra.args"   default=""/>

    <sequential>
        <echo/>
        <echo message=" Compiling subproject: @{name}"/>
        <xslt in="${dir.flex.projects}/@{name}/.flexLibProperties" out="${dir.flex.projects}/@{name}/src/manifest.xml" style="${dir.war}/build-manifest-style.xsl"/>
        <exec executable="${flex.compc}" failonerror="true">
            <arg line="-load-config+=${dir.flex.projects}/@{name}/include-files.xml"/>
            <arg line="-namespace http://@{name}.ourURL.com ${dir.flex.projects}/@{name}/src/manifest.xml"/>
            <arg line="-include-namespaces http://@{name}.ourURL.com @{xtra.args}"/>
            <arg line="-library-path+=${dir.webinf}/lib -sp ${dir.flex.projects}/@{name}/src -output ${dir.webinf}/lib/@{name}.swc"/>
        </exec>
    </sequential>
</macrodef>


<!--=================================================================================
    This is where all the compilation is done.  The actual work is split among
    several different tasks in order to organize them better.

    This target uses the html-wrapper task defined in flexTasks.jar - see taskdef above.
-->
<target name="flexcompile" depends="flexc-modularize" description="Builds the Flex sources" unless="flexc.notRequired.main">
    <echo message="Compiling MegaProduct Flex application on OS family: ${os.family}"/>
    <echo message="   mxmlc is: ${flex.mxmlc}"/>
    <echo message="   compc is: ${flex.compc}"/>

    <!--compile flex sub-projects first (main application depends on these extra libraries)-->
    <antcall target="flexc-projects"/>

    <!--compile the main MegaProduct application-->
    <antcall target="flexc-main"/>

    <!--compile the foobar stuff, which link against the main app.  these foorbars are modules
     inside a subproject, so they are handled differently from other flex projects and modules-->
    <antcall target="flexc-foorbars"/>

    <!--generate the html wrapper for the .swf-->
    <html-wrapper title="MyCorp MegaProduct" application="app_name" swf="app_name" history="false" template="express-installation"/>
</target>

<target name="flexc-projects">
    <!--the name must match the name of the folder exactly, also they are not in parallel as some depend on others-->
    <flexc-subproject name="Dockable"/>
    <flexc-subproject name="EXRibbon" xtra.args="-source-path+=${dir.flex.projects}/EXRibbon/locale/en_US/"/>
    <!--note: MPLib does some extra stuff with the image dir in order to link against images correctly-->
    <copy todir="${dir.flex.projects}/MPLib/src/image"><fileset dir="${dir.war}/image"/></copy>
    <flexc-subproject name="MPLib"/>
    <delete dir="${dir.flex.projects}/MPLib/src/image"/>
</target>

<target name="flexc-main">
    <!--the link report is used to create the symbols in the main swf, and modules link against it-->
    <property name="link.report"   value="${dir.war}/abc_link_report.xml"/>

    <!--modular.args is set in flexc-modularize.  If not set, this sets it to an empty property-->
    <property name="modular.args"  value=""/>

    <!--set up options specific for the main part and for the modules-->
    <property name="main.args"     value="-link-report=${link.report} ${modular.args}"/>
    <property name="module.args"   value="-load-externs=${link.report}"/>

    <!--compile abc_flex.mxml here-->
    <echo message="Compiling abc_flex application, sub-applications and modules..."/>
    <echo/>
    <flexc-mxml name="abc_flex" mxml.args="${flex.common.args} ${main.args}"
            sourcePath="${dir.war}/abc_flex.mxml" destPath="${dir.war}/abc_flex${swf.suffix}.swf"/>

    <!--compile MPMainSubApplication.mxml sub-application here-->
    <flexc-mxml name="MPMainSubApplication" mxml.args="${flex.common.args} ${main.args}"
            sourcePath="${dir.war}/MPMainSubApplication.mxml" destPath="${dir.war}/MPMainSubApplication.swf"/>

    <!--compile internal modules next - just add new modules to the list here -->
    <parallel>   <!--do in parallel - it goes faster and they don't depend on each other-->
        <property name="dir.module.src" value="${dir.war}/module/"/>
        <flexc-mxml name="module1"      sourcePath="${dir.module.src}/editor/Editor.mxml"          destPath="${dir.module.src}/editor/Editor.swf"          />
        <flexc-mxml name="RunModule"   sourcePath="${dir.module.src}/run/RunModule.mxml"          destPath="${dir.module.src}/run/RunModule.swf"          />
        <!--<flexc-mxml name="JobManager"  sourcePath="${dir.module.src}/jobmanager/JobManager.mxml"  destPath="${dir.module.src}/jobmanager/JobManager.swf"  />-->
        <flexc-mxml name="Editor2"        sourcePath="${dir.module.src}/edit/Editor.mxml"                destPath="${dir.module.src}/edit/Editor.swf"                />
    </parallel>
</target>

注:

我不确定这是否是一个好主意，但我们只是将要包含在Java中间层lib中的.swc文件放在WEB-INF/lib中，所以每当我们向源代码管理添加新的flex lib时，我们都会将其放在那里。编译是在宏中完成的，大多数参数在顶部部分定义为属性。由于我们的应用程序相当大，目标公司将工作分成了两部分；您可能不需要这些，但这是一个在子项目和链接报告中执行模块的示例，并且遵循从主应用程序引用子项目的方式（我认为）。我们的构建机器是linux，所以这就是为什么flexc.exe属性（和其他属性）是这样定义的——它是在运行时设置的。这个答案的名字已经被手工填好了，所以如果你剪切粘贴任何东西，请仔细检查拼写错误

另外，增量编译并没有实际使用；好像有马车。模块化的东西也是如此，所以我没有包括这个目标

---

这一切都是我自己建造的，所以我很自豪，但如果有任何东西看起来不确定或气味难闻，请随时告诉我。谢谢

了解编译器选项的一种快速方法是将此标记添加到编译器选项中：

-将配置文件转储到/drive/to/store/the/xmlfile.xml

这将输出整个ant编译器选项，您可以复制要保留的部分。

HellFire编译器守护程序（/）可以直接从Flex/Flash Builder的编译器调用生成build.xml。这意味着您的ant脚本根据您在Flex/Flash Builder中设置的完全相同的一组编译器设置生成SWC和SWF

此外，请查看此博客：