I'll stake a stab at this, maybe we can isolate the problem...
o Is this your first project w/ GWT in this environment?
If so, please try establishing a baseline by installing and running
the StockWatcher example
o Is SWT the Standard Widget Toolkit?
The sentence "GWT's SWT really does think I'm running on Linux"
implies ownership of SWT by GWT. Isn't SWT a separate library?
Sorry, my previous post (deleted) referenced GWT 1.6
Nevertheless, please set Eclipse aside for the moment and try compiling
any of the samples/
For example, inside the samples/DynaTable/ you should find the
DynaTable-compile and DynaTable-shell scripts. Please try one of the
samples/* *-compile or the *-shell scripts.
> The contents of the log file:
>
> java.lang.RuntimeException: Unexpected exception
> at com.google.appengine.tools.enhancer.Enhancer.execute
>
>
<SNIP>
I have to admit that I don't understand the log. But, it reinforces my
desire to verify the integrity of your GWT installation.
> Step 2, Testing the default project components, resulted in nothing
> being displayed (although the Eclipse console flickered). Assuming
> that something got logged about the problem somewhere, do you know
> where that somewhere would be?
>
> With regard to SWT, I believe that's exactly correct. There are 4
> jnilibs in the toolkit with swt in their name and I presume they
> implement at least part of the Software Widget Toolkit. They are
> clearly carbon and not gtk which makes sense because I'm running on a
> Mac, not Linux. But the error I get using the GWT Designer is no swt-
> pi-gtk-3062 in java.library.path. Also, I don't believe the Designer
> even looks at the GWT Eclipse plugin. The one must-be-set preference
> in the Designer configuration is where in the file system to find the
> toolkit.
>
>
That is a problem. For example, a listing of my 1.5.3 directory shows:
/usr/local/lib/gwt-linux-1.5.3$ ls libswt* -c1
libswt-gtk-3235.so
libswt-mozilla17-profile-gcc3-gtk-3235.so
libswt-mozilla17-profile-gtk-3235.so
libswt-mozilla-gcc3-gtk-3235.so
libswt-mozilla-gtk-3235.so
libswt-pi-gtk-3235.so
So, I can see where Tech Support draws their conclusion. Can you check
the corresponding GWT directory on your installation?
So, how did we get to build.xml (a GWT 1.6 artifact)?
It's good that we've eliminated Eclipse, GWT Eclipse Plugin, Instantiations.
Are you running 1.5 or 1.6 (or both)? I'm wondering if you installed
Linux GWT when you installed the GWT Eclipse plugin.
On Apr 23, 1:33 pm, Rajeev Dayal <rda...@google.com> wrote:If you're on a Mac and you're using GWT, you must use JDK 1.5. To make surethat ant is actually using your 1.5 JDK, can you set the JAVA_HOMEenvironment variable to point to the 1.5 JDK, and try re-running ant hosted?
It seems that GWT 1.6 is there by virtue of Genuitec's MyEclipse.
It also seems that you have the GEP.
Please search for "gwt-user.jar" The search above only looked for
Eclipse-specific stuff. It's possible that there's another GWT 1.6
installation lurking.
At this point I'm torn between removing MyEclipse or removing just the
GWT and GEP. Do you understand enough about Eclipse to install/remove
plugins? If not, I'd nuke MyEclipse.
My advice is to get to a working GWT 1.6 that's independent of
MyEclipse. See http://code.google.com/webtoolkit/versions.html
You don't need MyEclipse's bundled version of GWT that comes with the GEP.
Once you've verified that there are no other unexpected GWT
installations, and either installed a standalone version of GWT1.6 or
verified that MyEclipse is correct and complete, prove the installation
by building the samples,
I want to see a successful build of the samples. This will bolster your
confidence and prepare you for the MyEclipse/Instantions debugging.
I know this bites the big one, but there's too much stuff all at once.
When you download "raw" 1.6 or 1.5, they have nothing to do with
eclipse. So, I'm somewhat confused, and we may be getting closer to
resolving the problem. Did you download those files from
http://code.google.com/webtoolkit/versions.html? If not, please
remove/rename (see the note below) in the eclipse directory. Then
install GWT 1.5 from the webtoolkit site. This should put GWT 1.5 into
some directory like "/usr/local/lib" (or however you manage your
system). It should have absolutely nothing to do with eclipse. You can
tell instantiations to refer to a non-eclipse path for the GWT library
location.
I don't know instantiations. If it provides a work-alike for GEP,
remove GEP (since we prefer instatiations over GEP if instantiations
is a super-set of GEP).
To use instantiations, you should remove all traces of GWT 1.6. I say
this knowing full well that it's possible to point instantiations at
GWT1.5. However, to get things up-and-running, you should start with a
clean slate, in an environment that will move you to using
instantiations with as few distractions as possible.
>
> I removed the plugin but that apparently does not result in actually
> deleting the files. At this point can I simply remove the directory
> com.google.gwt.eclipse.sdkbundle.macosx_1.6.4.v200904062334 and
> everything beneath it without causing a problem in Eclipse? That
> would leave me with only a single 1.6.4 and a 1.5.3, which are the two
> I specifically downloaded from the Google site (http://code.google.com/
> webtoolkit/versions.html). But I don't want to delete the file
> structure until I know whether Eclipse still knows about it at some
> level and if so, how to fix that.
I don't know what eclipse will do. I think some of it depends on how
you installed eclipse, and since you're on OSX, that's unfamiliar
territory for me. On my box, I upgrade/install as root, and work in
eclipse in a regular user account.
I also know that eclipse records information in a user-private directory.
All that being said: when I encounter problems like this (esp. w/
eclipse which is such a pita to configure) I rename the offending
directory. This rename effectively deletes the file, but leaves it
available to recover when eclipse goes belly-up. E.g. rename it to
"com.google.gwt.eclipse.sdkbundle.macosx_1.6.4.v200904062334.delete.me"
I still think that because of the reliance on instantions, you should
forget about GWT 1.6 for now. See the above comment. Concentrate on
getting a successful build of the 1.5 samples in a pristine
environment. Leaving 1.6 out there means an additional step of
verifying that installation.
Congratulations, Rob!
At this point, you should be able to work w/ Instantiations tech
support. You now have correct and complete understanding of what's what
and where on your system.
I'm sure I speak for the rest of the list when I say that we look
forward to seeing what you can do w/ Instantiations.
Cheers,
jec