Public code release

These instructions are outdated. See the new instructions!

My code is now in a sufficiently clean state that I can push it out to the world. For anyone who wants to give it a try, here are the instructions that should get you up and running. This assumes that you have GHC, cabal-install, darcs, and git. I tested only on Ubuntu 9.4, but there is no reason why it should not work on Windows as well.

  1. Get my branch of the Scion sources:
    git clone git://github.com/ttencate/scion.git
    (It should also work with nominolo’s original sources.)
  2. Build and install Scion, the library as well as the server program:
    cd lib
    cabal install
    cd ../server
    cabal install
  3. Get Eclipse Galileo (3.5 RC4 or later), the distribution named “Eclipse for RCP/Plug-in Developers”. Extraction equals installation.
  4. Get my branch of the EclipseFP sources:
    darcs get http://code.haskell.org/~ttencate/eclipsefp/
    darcs get http://code.haskell.org/~ttencate/cohatoe/
    (Although Cohatoe is probably going to be removed, this version of EclipseFP still depends on it. Build the Cohatoe server if you like; it segfaults on my system.)
  5. Import all Eclipse projects from these repositories into Eclipse. There are over forty, so the Multi Project Import/Export plugin might come in handy.
  6. Wait for the build to finish, then… Run!
  7. In the new Eclipse window that (hopefully) pops up, set the location of the Scion server via Window, Preferences. If you installed it locally, it should be in ~/.cabal/bin/scion_server. (Eclipse does not understand the tilde, so give the full path to your home directory.)

It’s quite some work to get it all up and running, and I probably forgot a step or two. Making the process easier is not currently a priority, but I envision a complete Eclipse release that is easy to set up and has everything you need to get Haskelling quickly.

If you try these steps, and run into any problems, please let me know, so that I can help you out, and improve the instructions and maybe even the code at the same time.

About these ads

8 Responses to “Public code release”

  1. “Open Definition” and code improvements « EclipseFP GSoC ‘09 Says:

    [...] This may be a trivial feature, but very important: now that the path to my home directory is no longer hard-coded, other people might actually be able to try my code too! Feeling adventurous? See the next post! [...]

  2. Björn Peemöller Says:

    Hi,

    I tried to get it running but the build didn’t finish successfully. I got 232 errors which I can mail to you but the main reason seems to be that some classes are missing:
    - net.sf.eclipsefp.haskell.core.jparser.HaskellLexerTokenTypes
    - net.sf.eclipsefp.haskell.core.jparser.HaskellParser
    - net.sf.eclipsefp.haskell.core.jparser.HaskellLexer

    I just browsed the darcs-repo but did not find them. Are they missing in the repo?

    Cheers,
    Björn

  3. Björn Peemöller Says:

    I tried to build the eclipsefp projects but it seems that there are some classes missing in the repository:
    net.sf.eclipsefp.haskell.core.jparser.HaskellParser
    net.sf.eclipsefp.haskell.core.jparser.HaskellLexer
    net.sf.eclipsefp.haskell.core.jparser.HaskellLexerTokenTypes

    • Thomas Says:

      These classes should be magically generated by antlr when the project is built. This worked out of the box for me, but I can have a look how you can trigger it manually. Don’t have time now, probably later today!

    • Thomas Says:

      Oh, maybe you can try refreshing the net.sf.eclipsefp.haskell.core project? The classes might have appeared on the filesystem without Eclipse noticing?

      • Björn Peemöller Says:

        Thanks, that was the reason. So now I can start testing it :)

  4. New build instructions « EclipseFP GSoC ‘09 Says:

    [...] Wait for the build to fail. Yes, that’s right. It will complain about missing files, because ANTLR generated some that Eclipse doesn’t yet know about. Refresh the net.sf.eclipsefp.haskell.core.jparser project, then wait for the build to succeed. (Thanks to Björn Peemöller for pointing this out!) [...]

    • Thomas ten Cate Says:

      A strange decision for the pingback quote text. Strangely appropriate, too, in a way. Wonder how they do that.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: