Difference between revisions of "ECF/Development Guidelines"

From Eclipsepedia

< ECF
Jump to: navigation, search
(Creating the page)
 
m (Installing an Appropriate Foundation 1.1 Execution Environment (Windows/Linux): Grammar)
Line 2: Line 2:
  
 
==Workspace setup==
 
==Workspace setup==
===Installing an Appropriate Foundation 1.1 Execution Environment (Windows/Linux)===
+
===Installing a Foundation 1.1 Execution Environment on Windows/Linux===
 
# Go to [http://www-128.ibm.com/developerworks/websphere/zones/wireless/weme_eval_runtimes.html IBM's WEME evaluation platforms website].
 
# Go to [http://www-128.ibm.com/developerworks/websphere/zones/wireless/weme_eval_runtimes.html IBM's WEME evaluation platforms website].
# Select the appropriate Foundation 1.1 download based on your operating system (Linux or Windows XP).
+
# Select the appropriate Foundation 1.1 download based on your operating system.
# Go through the motions of signing up/logging into an IBM account and then download the .exe or .bin file.
+
# Go through the motions of signing up/logging into an IBM account and then download the .exe (Windows) or .bin (Linux) file.
# Install the downloaded file. On Windows, simply double-click on the executable as you would as usual. On Linux, make sure that the .bin file is executable (invoke a <code>chmod +x</code> on it as necessary). You may not have permissions to write to the default folder it sets itself to, so change it as necessary.
+
# Install the downloaded file. On Windows, simply double-click on the executable as you would for any other program. On Linux, make sure that the .bin file is executable (invoke a <code>chmod +x</code> on it as necessary), and then open it (from the command line or otherwise). You may not have permissions to write to the default folder it sets itself to, so change it as necessary.
 
#Dig inside the installed folder until you find the <code>weme-win-x86-ppro11_6.1.0.20060727-102926.zip</code> zip file (the name will be slightly different on Linux).
 
#Dig inside the installed folder until you find the <code>weme-win-x86-ppro11_6.1.0.20060727-102926.zip</code> zip file (the name will be slightly different on Linux).
#Extract the file to somewhere of your convenience. On Linux, you may need to enter the <code>bin</code> folder and invoke <code>chmod +x</code> on the <code>*.so</code> files and the J9 binaries (such as <code>j9</code>, <code>j9dbserv</code>, etc.).
+
#Extract the file to somewhere of your convenience. Note that it will '''not''' create a new folder, so don't unzip it in a messy folder! ;) On Linux, you may need to enter the <code>bin</code> folder and invoke <code>chmod +x</code> on the <code>*.so</code> files and the J9 binaries (such as <code>j9</code>, <code>j9dbserv</code>, etc.).
 
#Follow the J9 JRE setup instructions specified [http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-debug-home/plugins/org.eclipse.jdt.launching.j9/index.html here]. If you do not find the plug-in after you have reinstalled Eclipse, try again with the <code>-clean</code> argument appended.
 
#Follow the J9 JRE setup instructions specified [http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-debug-home/plugins/org.eclipse.jdt.launching.j9/index.html here]. If you do not find the plug-in after you have reinstalled Eclipse, try again with the <code>-clean</code> argument appended.
 
# Now configure your execution environments by going to Window - Preferences - Java - Execution Environments.
 
# Now configure your execution environments by going to Window - Preferences - Java - Execution Environments.

Revision as of 04:09, 30 October 2006

This document is intended to introduce an interested developer on how to get acquainted with the ECF codebase, filing bugs at Bugzilla, and setting up a workspace with proper execution environments.

Contents

Workspace setup

Installing a Foundation 1.1 Execution Environment on Windows/Linux

  1. Go to IBM's WEME evaluation platforms website.
  2. Select the appropriate Foundation 1.1 download based on your operating system.
  3. Go through the motions of signing up/logging into an IBM account and then download the .exe (Windows) or .bin (Linux) file.
  4. Install the downloaded file. On Windows, simply double-click on the executable as you would for any other program. On Linux, make sure that the .bin file is executable (invoke a chmod +x on it as necessary), and then open it (from the command line or otherwise). You may not have permissions to write to the default folder it sets itself to, so change it as necessary.
  5. Dig inside the installed folder until you find the weme-win-x86-ppro11_6.1.0.20060727-102926.zip zip file (the name will be slightly different on Linux).
  6. Extract the file to somewhere of your convenience. Note that it will not create a new folder, so don't unzip it in a messy folder! ;) On Linux, you may need to enter the bin folder and invoke chmod +x on the *.so files and the J9 binaries (such as j9, j9dbserv, etc.).
  7. Follow the J9 JRE setup instructions specified here. If you do not find the plug-in after you have reinstalled Eclipse, try again with the -clean argument appended.
  8. Now configure your execution environments by going to Window - Preferences - Java - Execution Environments.
  9. Select CDC-1.1/Foundation-1.1 from the left column, you should see your newly installed VM being a [perfect match], click on the checkbox, and then click 'OK'.
  10. That's it!

Setting a Foundation 1.1 Runtime for a Project

  1. Click on your project and access it's properties bringing up its context menu by right-clicking, 'Properties' should be at or near the bottom.
  2. Access the 'Java Build Path' section and click on the 'Libraries' tab.
  3. Click on your existing JRE System Library and remove it.
  4. Click on 'Add Library...', a dialog window should appear.
  5. Select 'JRE System Library', and then go 'Next'. Select the 'Execution Environment' radio button, and then select CDC-1.1/Foundation-1.1 from the combo control, now click 'Finish'.

You can set a plug-in's EE by opening up the MANIFEST.MF file and setting it it in the 'Overview' tab.

See also

Development Conventions and Guidelines

Version Numbering