GWT Firefox 3.6+ plugin on 64bit Fedora 13

Posted by Ktoso on 10/07/2010 – 14:17

Hi again, this time a short code snippet – but a very useful one.

At work I’m working on an Ubuntu 10.4 (love you guys for getting me a PC with Linux without making a fuss about it!) my laptop is on Fedora 13 i586 and my home PC is running Fedora 13 x64. Thank goodnes they’re all linux… ;-) The problem is was that the Google Web Toolkit plugin isn’t working with Firefox 3.6.4 on an x64 system on linux! So… can’t I develop GWT stuff on my super powerful home PC? Of course I can, the only thing I needed to do, is to get the latest sources for the plugin and compile it for myself ;-) Here’s how:

mkdir gwt-source
  1. cd gwt-source
  2. svn checkout http://google-web-toolkit.googlecode.com/svn/trunk/ trunk
  3. svn checkout http://google-web-toolkit.googlecode.com/svn/plugin-sdks/ plugin-sdks
  4. cd trunk/plugins/xpcom
  5. export BROWSER=ff36
  6. export DEFAULT_FIREFOX_LIBS=/usr/lib/xulrunner-devel-1.9.2/sdk/lib/
  7. make clean
  8. make
  9. firefox prebuilt/gwt-dev-plugin.xpi

And we’re done — off to GWT development!

Tags: , , , , ,

This post is under “coding, guide, java” and has 7 respond so far.

7 Responds so far- Add one»

  1. 1. Henrik Abeler Said:

    Thanks a lot, this was extremely helpful!
    Had to add g++, as that is not installed by default, so anyone experiencing compile problems try to install g++

    yum install gcc-c++

  2. 2. Sean Langford Said:

    perfect. Works a treat on my linux amd64 arch workstation. thx!

  3. 3. Julio Faerman Said:

    Worked perfectly for me (Fedora 13 x86_64) thanks

  4. 4. Hernan_ Said:

    Thanks a lot!

  5. 5. John Holland Said:

    This is excellent, it works in Fedora 13 64 bit as well. Thanks for posting this.

  6. 6. Patrick Way Said:

    Worked perfectly (Slackware 13.1 64 bit)

    Thanks a lot!

  7. 7. Charles Butterfield Said:

    Works fine for Fedora-14. Thanks for a GREAT tip.

    Wasn’t sure what the export of DEFAULT_FIREFOX_LIBS was doing, since I do NOT have any such directory on my system, so I skipped that and it still worked. Was I just lucky? What is the point of that env var?

Post a reply