Building the Feathers SWC binary from source code
Whether you're using the latest unstable version of Feathers or you've made changes to the core Feathers library, you may want to build the Feathers SWC locally.
Feathers source code from Github (the main build target does not use the Flex SDK)
The main build script is
build.xml, located in the root of the source tree. This file is only available if you download the full project source code for Feathers on Github. The build script is not included in the ZIP file that is downloadable from the Feathers website.
Two other files in the same directory,
sdk.properties, set up the environment for the build script. If you need to override any properties from these files, you can create new files named
sdk.local.properties. The build script will automatically detect if these files are present and use their values instead of the defaults.
- Create a file named
sdk.local.propertiesin the same directory as
build.xml. Inside, override the
airsdk.rootproperty to point to the location of your local AIR SDK with ASC 2.0:
airsdk.root = C:/Development/AIR_SDK
Use the path on your local computer rather than the one above. The path above is for a location on Windows, but paths on Macs are supported too. Make sure that you use forward slashes, regardless of which platform you're on.
- build.properties creates a property named
starling.rootthat points to
third-party/starling. From the Starling Framework, copy the contents of
starling/srcinto this directory.
Alternatively, you may create a
build.local.properties file and override the value of
Open a command prompt in the directory where build.xml is located.
Run the command
feathers.swcwill be compiled and placed in an directory named
Most likely, you will only need the
swc target, which simply builds the SWC and does nothing else. There are several targets available that you may find useful.
swccompiles the Feathers SWC.
apigenerates the Feathers API documentation.
helpgenerates the Feathers Help files from Markdown.
testruns the Feathers unit tests.
fullcompiles the SWC, generates the API documentation, and copies all of the supporting files into the
outputdirectory to create a full release build of Feathers.
packagecreates a full release build of Feathers, and then it packages everything into a ZIP file.