There are a few Eclipse and CSS configurations available on SLAC file systems.
Eclipse for RCP and RAP Developers, Indigo Service Release 2, with Python plugin:
| No Format |
|---|
/afs/slac/package/eclipse/i386_linux26/3.7.2/eclipse
|
Eclipse Java EE IDE for Web Developers, Indigo Service Release 2
from lcls-builder at:
| No Format |
|---|
/usr/local/bin/eclipse
|
from dev network at:
| No Format |
|---|
/afs/slac/g/lcls/bin/eclipse
|
2004 version at
| No Format |
|---|
/afs/slac/g/glast/applications/eclipse/eclipse-SDK-3.0.1-linux-gtk/eclipse/eclipse
|
[list more that are around?]
Feel free to try the Eclipse CDT C/C++ Development Tool The Eclipse CDT (C/C++ Development Tool) is well suited to IOC development, and easily customized for editing .db/.template/.substitutions files. Even if you never touch the C code, you can do most of your IOC development with this tool. It includes more generally useful features like search and replace in a directory tree for file names or contents (Ctrl-H), regex search/replace, and CVS access. Feel free to try the installation at /afs/slac/u/re/gwbrown/afsbin/eclipse/eclipse. This is not maintained as a site installation. It's easy to download and install your own configuration, where you can try out plugins etc. and untar a clean uninstall if it causes problems. Make sure you've requested a a big afs quota.
...
Download CDT from http://www.eclipse.org/downloads (one of many flavors of eclipse from eclipse.org)
Unzip/ tar -xvf filename
run ./eclipse in the directory created by unzipping
If you're mostly using this workspace for EPICS work, you can change global default settings by going to Window -> Preferences -> C/C++ -> New C/C++ Project Wizard -> Makefile Project. On the Behaviour tab, delete "all" after "Build (Incremental build)", and change "clean" to "distclean".
Or change the settings on individual project settings by right clicking the project name -> Properties.
Click C/C++ Build. Make sure "Generate Makefiles automatically" is unchecked, and Build directory doesn't have any
path past your project name. On the Behaviour tab, delete "all" after "Build (Incremental build)", and change "clean" to "distclean".
If you want Eclipse to know about base, modules, other things, expand C/C++ General, select Paths and Symbols, and
Add... include paths.
For reasonable colorization, I associate most EPICS files with the makefile editor
To transfer file associations, copy
oldWorkspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.runtime.prefs (or use example attached )
into newWorkspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/
Other settings can be transferred similarly, but copying the entire .metadata directory tree will cause problems
Or
Go to Window -> Preferences, expand General->Content Types, expand Text -> Makefile, click Add...
and add everything in configure directory, *.db, *.substitutions, *.template, st.cmd
You can have Eclipse launch external tools and editors. If you find a way of passing command line options, update this. It runs an executable with the selected file name as the only argument. As a workaround, instead of trying to pass command line options to edm, create a launch script that has command line options. Here's an example, ~gwbrown/scripts/eclipseEdm:
| Code Block |
|---|
#! /bin/bash
# Launch edm from eclipse with a few options, since eclipse won't let you add flags to "external tools"
edm -eolc $1&
|
Then in Eclipse, set that script as the editor for *.edl files.
Window -> Preferences -> General -> Editors -> File Associations, Add... File type *.edl, to that Add... Associated editor of your launch script as n External program.
Both Eclipse and VDCT are good about picking up on changes made by other programs to the files you have open, so you can use both at once. You can have Eclipse launch VDCT as an external tools. Navigate from the Run menu -> External Tools -> External Tools Configurations... . Click the rectangle with a + icon ("New launch configuration"), name it something meaningful like vdct, for Location: use /afs/slac/lcls/tools/script/vdct, for Working Directory: use ${project_loc}, and click Apply.
When you start Eclipse, it asks for a workspace. A workspace is just a directory. Give it a directory name, and it will create it if it isn't there already. It will put hidden metadata files and possibly project directories in the workspace directory.
...
Click project name, right click -> New -> Convert to a C/C++ Project
Select Project type "Makefile project", then Toolchains Cross GCC and Linux GCC. Click "Finish".
If you're mostly using this workspace for EPICS work, you can change global default settings by going to Window -> Preferences -> C/C++ -> New C/C++ Project Wizard -> Makefile Project. On the Behaviour tab, delete "all" after "Build (Incremental build)", and change "clean" to "distclean".
Click the hammer icon to run "make"
Check the console tab for errors. The "Problems" tab isn't very reliable.
Note: depending on how this project was created, you may have to change the build default behavior or it will "make all". Click on the project name, right click, select properties. Or change the settings on individual project settings by right clicking the project name -> Properties.
Click C/C++ Build. Make sure "Generate Makefiles automatically" is unchecked, and Build directory doesn't have any
path past your project name. On the Behaviour tab, delete "all" , select the Bahaviour tab. In the text box after "Build (Incremental build)" , and change "clean" to "distclean".
If you want Eclipse to know about base, modules, other things, expand C/C++ General, select Paths and Symbols, and
Add... include paths.
Click the hammer icon to run "make"delete what's there, it should be empty. In the text box after "Clean" put "distclean". Click OK and try building again.
Click the project name, right click -> Clean Project to run "make distclean"
Check the console tab for errors. The "Problems" tab isn't very reliable.
For reasonable colorization, I associate most EPICS files with the makefile editor
To transfer file associations, copy
oldWorkspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.runtime.prefs (or use example attached )
into newWorkspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/
Other settings can be transferred similarly, but copying the entire .metadata directory tree will cause problems
Or
Go to Window -> Preferences, expand General->Content Types, expand Text -> Makefile, click Add...
and add everything in configure directory, *.db, *.substitutions, *.template, st.cmd
You can have Eclipse launch external tools and editors. If you find a way of passing command line options, update this. It runs an executable with the selected file name as the only argument. As a workaround, instead of trying to pass command line options to edm, create a launch script that has command line options. Here's an example, ~gwbrown/scripts/eclipseEdm:
| Code Block |
|---|
#! /bin/bash
# Launch edm from eclipse with a few options, since eclipse won't let you add flags to "external tools"
#export EDMDATAFILES=.:..:BeamLossFiberApp/srcDisplay:../lclsEdm:../blmEdm:../eventEdm
edm -eolc $1&
|
Then in Eclipse, set that script as the editor for *.edl files.
There are a few Eclipse and CSS configurations available on SLAC file systems. They are generally not maintained much, and aren't set up for IOC development, but may be useful for other purposes.
Eclipse for RCP and RAP Developers, Indigo Service Release 2, with Python plugin:
| No Format |
|---|
/afs/slac/package/eclipse/i386_linux26/3.7.2/eclipse
|
Eclipse Java EE IDE for Web Developers, Indigo Service Release 2
from lcls-builder at:
| No Format |
|---|
/usr/local/bin/eclipse
|
from dev network at:
| No Format |
|---|
/afs/slac/g/lcls/bin/eclipse
|
2004 version at
| No Format |
|---|
/afs/slac/g/glast/applications/eclipse/eclipse-SDK-3.0.1-linux-gtk/eclipse/eclipse
|
[list more that are around?]Window -> Preferences -> General -> Editors -> File Associations, Add... File type *.edl, to that Add... Associated editor of your launch script.
