blob: 0319120319281af983263f7f76effb4157fc667d [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Target Platform Preferences</title>
<link href="../../book.css" rel="stylesheet" type="text/css">
<script type="text/javascript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
<style type="text/css">
<!--
.style1 {
font-size: 18px;
font-weight: bold;
}
.style2 {
font-size: 12pt;
font-weight: bold;
}
-->
</style>
</head>
<body>
<p class="style1">Target Platform Preferences</p>
<p>Target Platform refers to the platform against which you are developing and testing your plug-ins. The target platform encompasses the location of the target, the list of plug-ins constituting the target, the target environment and launching arguments. </p>
<p>&nbsp;</p>
<p class="style2">Target Location</p>
<p>The target location typically denotes the location of an Eclipse installation. When searching the target location for plug-ins, PDE assumes a typical Eclipse installation layout, i.e. plug-ins are expected to be in a <em>plugins/ </em>subdirectory of the target location. Similarly, features are assumed to be in a <em>features/ </em>subdirectory of the target location. </p>
<p><img src="../../images/preferences/target_location.png" alt="Target Location" hspace="30"></p>
<p>Not all targets are Eclipse installations. Therefore PDE is flexible when it comes to locating plug-ins in the target. In the absence of a <em>plugins/</em> subdirectory, PDE assumes the target location itself is the directory where plug-ins are located.</p>
<p>&nbsp;</p>
<p class="style2">Target Definitions</p>
<p>Target Definitions are <em>.target</em> files that encapsulate all aspects of a target (location, content, environment, etc.). </p>
<p>The Pre-defined Targets section of the
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.TargetPlatformPreferencePage)")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong></a>
preference page is initially populated by definitions contributed via the <strong>org.eclipse.pde.core.targets</strong> extension point.</p>
<p><img src="../../images/preferences/target_predefined.png" alt="Target definitions" hspace="30"></p>
<p>You can browse for additional target definitions in the workspace using the <strong>Browse... </strong>button.</p>
<p>To preview the target profile before you apply it, click on the <strong>Target</strong> link. This will open a new window showing the content of the target definition.</p>
<p>To load the target, press the <strong>Load Target</strong> button. This will update all the tabs on the Target Platform preference page based on the content of the selected target definition. </p>
<p>&nbsp;</p>
<p>For more information, refer to the following documents:</p>
<ul>
<li><a href="target_plugins.htm">Target Plug-ins</a></li>
<li><a href="target_env.htm">Target Environment</a></li>
<li><a href="launching_args.htm">Launching Arguments</a></li>
<li><a href="implicit_dependencies.htm">Implicit Dependencies</a></li>
<li><a href="source_code_locations.htm">Source Code Locations</a></li>
</ul>
</body>
</html>