Originally written in Processing, Particle Play has been converted to C++ using OpenGL and openFrameworks.

Solution
Under the Groups & Files panel, you'll see a group called Targets. Expand the Targets group and double click on your project name.
Make sure you're in the Build panel.
Under Architectures, change the Base SDK to iPhone Device 3.2 or above.

Problem
OpenFrameworks iPhone projects won't compile, most common issue is a DWARF issue.

Solution
1. Download the mac version of OF.
2. In the mac version, navigate to libs/FreeImage/lib/osx/
3. Copy the file "freeimage.a" to libs/FreeImage/lib/iPhone
4. In the iPhone version, rename "libFreeImage_iphone_universal.a" to "libFreeImage_iphone_universal_iphone.a"
5. Rename "freeimage.a" to "libFreeImage_iphone_universal.a"

/**
 * Adds the universal glow to the display object.
 * @param displayObject The display object to receive the glow.
 * @param container The container to hold the newly created snapshot.GlowMC.PAGE_VECTOR.
 */
public static function addGlow( displayObject:DisplayObject, container:DisplayObjectContainer ):void
{
	// Capture an instance of the displayObject
	var rect:Rectangle = new Rectangle( -1, -1, displayObject.width + 2, displayObject.width + 2 );
	var bmd:BitmapData = new BitmapData( displayObject.width + 2, displayObject.height + 2, true, 0xFF );
	bmd.draw( displayObject, null, null, null, rect, true );
 
	// Apply the Capture
	var bitmap:Bitmap = new Bitmap( bmd );
	var filters:Array = container.filters;
	var glowFilter:GlowFilter = new GlowFilter();
	glowFilter.blurX = glowFilter.blurY = 10;
	glowFilter.inner = false;
	glowFilter.knockout = true;
	glowFilter.strength = 1;
	glowFilter.quality = 2;
	glowFilter.color = 0xFFFFFF;
 
	// Set
	filters[filters.length] = glowFilter;
	bitmap.filters = filters;
	bitmap.blendMode = "add";
	container.addChild( bitmap );
 
	// Clear vars
	rect = null;
	bmd = null;
	bitmap = null;
	filters = null;
	glowFilter = null;
}
 

Also, it's best to add the filter object into a container so the blend mode works properly.

 
<project name="SWC and ASDoc Build" default="main" >

Second, we want to create variables within the script so it makes referencing files and folders easier.

<!-- CREATE THE VARS -->
<property name="FLEX_HOME" value="/Applications/Adobe Flex Builder 3/sdks/4.0.0" />
<property name="asdoc.exe" value="${FLEX_HOME}/bin/asdoc" />
<property name="project.path" value="/Users/Duffy/Desktop/Projects/Clients/INC/Framework" />
<property name="output" value="${project.path}/local" />
<property name="src" value="${project.path}/src" />
<property name="version" value="1.0" />
 
<taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/ant/lib/flexTasks.jar" />
 
<!-- SWC Related -->
<property name="output.swc" value="${output}/swc" />
<property name="swc.title" value="duff" />
 
<!-- AS DOC Related -->
<property name="output.docs" value="${output}/asdocs" />
<property name="doc.title" value="Duff API v.${version}" />
 

Here you'll see I'm referencing where the .exe ("asdoc.exe") and .jar ("flexTasks.tasks") files exist on my machine so ant knows how to use the compiler. I also reference where my project is located, as well as the source folder ("src") and output folders("output.swc" and "output.docs").

Note
I have periods delimit spaces with my variables with ANT, however you can name them however you want: "outputSWC", "output.swc", "output-swc" as examples.

Next, I'm going to tell ANT what functions it'll need to run. First and foremost, I want ANT to not "think" about overwriting files, so I'll delete a directory, then recreate it to save it the trouble. After that's done, I'll have it create the docs and the swc.

 
<target name="main" depends="clean-asdoc-directory, create-docs, clean-swc-directory, generate-swc" />
 
<target name="clean-asdoc-directory" >
   <delete dir="${output.swc}" />
   <mkdir  dir="${output.swc}" />
</target>
 
<!-- runs the asdoc.exe compiler on the source -->
<target name="create-docs" >
    <exec executable="${asdoc.exe}" failonerror="true" >
    	<arg line="-doc-sources '${src}'" />
    	<arg line='-window-title "${doc.title}"'/>
    	<arg line="-main-title '${doc.title}'" />
    	<arg line="-output ${output.docs}" />
    </exec>
	<echo>ASDOC created successfully</echo>
</target>

The first function is "clean-asdoc-directory", which deletes the directory then recreates it. We'll use the same functionality for compiling the SWC. Next, we have it create the documentation by running our ASDoc executable file. Each "arg line" is an argument that's sent to the executable so it receives the required variables. As you can see about, I have many "${}" lines, which are references to the "property" (aka variables) we created above. We also want the executable build to fail if there's any problems at all.

Now, let's compile that swc.

<!-- deletes and recreates the swc directory -->
<target name="clean-swc-directory" >
   <delete dir="${output.swc}" />
   <mkdir  dir="${output.swc}" />
</target>
 
<!-- generate the swc -->
<target name="generate-swc" description="Compile the SWC file">
 
	<fileset id="sources" dir="${src}">
		<include name="**/*.as" />
	</fileset>
<pathconvert property="classes" pathsep=" " refid="sources">
		<chainedmapper>
			<globmapper from="${src}/*" to="*" />
<mapper type="package" from="*.as" to="*" />
		</chainedmapper>
	</pathconvert>
 
	<compc output="${output.swc}/${swc.title}.${version}.swc" include-classes="${classes}">
		<source-path path-element="${src}" />
	</compc>
	<echo>SWC created successfully</echo>
</target>
</project>

The beauty about this "generate-swc" method is that it compiles all .as files within your "src" directory, whereas normally you would either have to manually input each class or each package.
You can download the final result here.