This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Using Eclipse with Frysk
- From: Rick Moseley <rmoseley at redhat dot com>
- To: frysk <frysk at sources dot redhat dot com>
- Date: Wed, 29 Mar 2006 15:02:13 -0600
- Subject: Using Eclipse with Frysk
Hi all,
Someone asked on #frysk the other day about using Eclipse to work on
Frysk and suggested we add some how-to detail to the Frysk webpage. I
told them I was using it, although in a somewhat degraded manner. For a
number of reasons, Eclipse cannot be used to totally build Frysk, but it
can be a great help in writing/modifying any Java code despite what the
emacs pushers say. :)
Here are the steps I use in bringing Frysk into an Eclipse project on an
FC5 system. If someone has a better way, please feel free to chime in.
1) Check out frysk from the website(see http://sourceware.org/frysk for
how to do this)
2) Bring up Eclipse
3) Click on File->New->Java Project->Next
4) Enter your desired project name
5) Select the "Create project from existing source"
6) "Browse..." to the directory where Frysk was imported
7) Select the top level "frysk" directory that came in from CVS
8) Click on "Next"
9) Select the "Libraries" tab at the top of the window
10) Select "Add External JARS..."
11) Browse to /usr/share/java and add the following jars:
cairo1.0.jar (cairo-java)
glade2.12.jar (libglade-java)
glib0.2.jar (glib-java)
gnome2.12.jar (libgnome-java)
gnu.getopt.jar (gnu-getopt)
gtk2.8.jar (libgtk-java)
jdom.jar (jdom)
If you do not have one of the jars listed, you will need to add the
package listed on the right in parentheses that provides it to your
system.
12) Click on "Finish"
You should wind up with a fairly usable project with the Frysk source
code. You can make modifications to the source code and check them back
into the CVS repo, but you will still need to build Frysk from the
command line. I usually have two different Frysk repos checked out, one
I use to build Frysk("build" repo), and another that I use for Eclipse
only("eclipse repo"). I usually do the editing with Eclipse, check it
in, and then go to the "build" repo, do a "cvs update -d" and then
rebuild there. Also, usually, each morning I do a "cvs update -d" in
the eclipse repo to make sure I have the latest source there.
Hope this helps. As I said earlier, if anyone has a better way, please
feel free to add your comments/suggestions.
Rick