developers/_building.html

<h2>
	<strong>Building</strong> AMP from source.
</h2>

<p>
	This page just got a lot shorter -- we've completely revamped the AMP
	build setup using Buckminster, Hudson and Git. Now you can get your
	entire workspace populated, <i>and install all of your dependencies</i>
	in a few easy steps! The only thing you need to have is familiarity
	with the Eclipse IDE and managing update sites. If you want to be up on
	the absolute latest, experiment with the framework itself, help with
	documentation, or -- best of all -- create patches and fixes for the
	project, building from source is the way to go:
</p>
<ol>
	<li>Get the latest Eclipse Indigo release. (Use the Modeling
		release, or just install the SDK and pick the tools you'll need later.
		You don't need to worry about dependencies themselves, Buckminster
		handles that for you!)</li>
	<li>Install these few features (Help &rarr; Install New
		Software...)
		<ul>
			<li>Buckminster from: <code>http://download.eclipse.org/tools/buckminster/updates-3.7</code>.
				(You don't need the Maven feature.)</li>
			<li>EGit and JGit from the Indigo site Collaboration category.
				(If you're using Eclipse Modeling download, you'll already have
				this.)</li>
			<li>The GEF3D project uses SVN (but not for long!) <code>http://community.polarion.com/projects/subversive/download/eclipse/2.0/indigo-site.</code>
				You'll need the Buckminster Subversive support as well from the site
				above.</li>
		</ul>
	</li>
	<li>Import the target platform and workspace.
		<ul>
			<li>File&rarr;Import..&rarr;Buckminster&rarr;Materialize..</li>
			<li>In the wizard enter: <code>http://git.eclipse.org/c/amp/org.eclipse.amp.git/plain/releng/org.eclipse.amp.releng/releng/amp-platform.cquery</code></li>
			<li>Click Load, wait for that to finish and click Finish.</li>
			<li>Repeat above steps using: <code>http://git.eclipse.org/c/amp/org.eclipse.amp.git/plain/releng/org.eclipse.amp.releng/releng/amp.cquery</code>
			</li>
			<li>Some warnings are expected.</li>
		</ul></li>
</ol>
<p>Optional steps recommended for committers and potential contributors:</p>
<ol>
	<li>Create a target platform in your workspace. You'll need to do
		this <i>before</i> you import your target platform. (The target
		platform is the set of features needed to <i>build</i> the tool as
		opposed to the tools needed to <i>develop</i> the tool. There is a
		difference!)
		<ul>
			<li>File&rarr;New&rarr;Other..&rarr;General&rarr; Project. Name
				it "TP"</li>
			<li>Eclipse&rarr;Preferences &rarr;Plugin-in Development
				&rarr;Target Platform.
			<li>Click Add.., Select "Empty", click Next, and then add the TP
				directory to the new definition. Name it "TP".</li>
			<li>Don't forget to activate your TP by clicking the checkbox.</li>
		</ul>
	</li>
	<li>If you're planning on committing code at some point (you know
		who you are!) don't forget to change the git push settings to
		configure git in preferences and change your push configuration to use
		ssh.</li>
</ol>
<p>
	To try out your source build, just create an Eclipse Application. See
	the <a
		href="http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm">Eclipse
		documentation</a> for more information.
</p>
<ol>
	<li>Select Run &rarr; Run Configurations..</li>
	<li>Select Eclipse Application and click "New Launch
		Configuration".</li>
	<li>The default "All Workspace and Enabled Target Plugins.."
		option is fine. If you want to specify individual plugins, you will
		probably need at least:
		<uL>
			<li>org.eclipse.amp.amf.ide</li>
			<li>org.eclipse.amp.escape.amf.ide</li>
			<li>org.eclipse.amp.amf.ide</li>
			<li>org.eclipse.amp.amf.data.editor</li>
			<li>org.eclipse.amp.amf.paramters.ui</li>
			<li>org.eclipse.amp.amf.testing.ide</li>
			<li>org.eclipse.sdk</li>
		</ul>Then, select the "Add Required Plugins" button.</li>
	<li>Click the Run button.</li>
	<li>A new Eclipse application should launch. Note that you can
		also launch using the Debugger which is helpful for debugging issues
		with AMP models.</li>
</ol>
<p>Problems? Send a note to the amp-developer list or our newsgroup.</p>