The current version of GWT can only run with a 32-bit JVM because GWT depends on SWT, and GWT only bundles the 32-bit version of the SWT libraries that it requires. The next version of GWT will support Out-of-process-hosted-mode, which means that you can use a real browser while debugging your GWT app, instead of the hosted browser. Getting rid of the hosted browser means that GWT will no longer depend on SWT, and you'll be able to use a 64-bit JVM with GWT.
If you want, you can actually build GWT Trunk right now, and try out Out-of-process-hosted-mode. Though we have not really documented it, the version of the plugin that we just released does support Out-of-process-hosted mode. On Fri, Jul 31, 2009 at 1:00 PM, Mauro <[email protected]> wrote: > > 2009/7/31 Rajeev Dayal <[email protected]>: > > You need to use a 32-bit JVM when running GWT. Install a 32-bit JVM, and > > change your project's JDK to use the 32-bit JVM. > > In future versions of GWT, it will no longer be necessary to use a 32-bit > > JVM. > > I have a 64bit platform and I don't want to use 32bit. > Why there isn't GWT for 64 bit? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
