-external-library-path + = my.swc is the answer, although there is no need to use time-extension libraries. Using this argument, you can specify the code that will be used in compilation, but not placed in swc. Obviously, this excluded code will still be needed if swc is used.
It should be noted that, unlike other arguments, -external-library-path uses + = not =. Using just =, you expand the link to the classes of low-level players and add other external libraries.
If you use FlexTasks w / Ant, your goal might look like this:
<target name="compileToSWC"> <compc output="${bin}/${SWCName}"> <source-path path-element="${src}"/> <include-sources dir="${src}" includes="*"/> <external-library-path file="${thirdparty.libs}/SomeLib.swc" append="true"/> <external-library-path file="${thirdparty.libs}/SomeOtherLib.swc" append="true"/> </compc> </target>
You can also specify the path of the external library to the folder, in which case it will include all the swcs inside. Please note: if you follow the recommendations of Adobe FlexTasks and put the flexTasks.jar file in your libs folder and configure it as a folder using the path of an external library, flexTasks.jar itself will be excluded, which will lead to a build failure. To solve this problem, put the flexTasks.jar file in a separate folder or directly configure swcs in the same way as in the above example.
source share