Guess what! I transferred my GWT app to the Vista 64 on the other side of the dualbooted machine but running 32bit Chrome (no such thing as a 64bit chrome currently), which requires a 32 bit jvm to run oophm. The GWT compilation was a breeze, comparatively. Wow 20 seconds versus 5 - 10 minutes on the same quad core system!?
Then I read, there is some extraneous statement sticking around 64 bit oophm making it wait for a long time (waiting for what I cannot remember). Why is it so easy to have that "extraneous statement" removed in 32 bit oophm but not in the 64 bit? I am thinking very hard that nobody probably would bother to answer this question. In the mean time, I'll try to debugging the app on 32bit Firefox on a 64bit ubuntu. I am reading people doing all sorts of acrobatics to get this "extraneous statement" removed by rebuilding the 64 bit oophm themselves from scratch. (Yet I could not find anyone who has successfully rebuilt 64bit oomph kind enough to share it online so that lazy people like me won't have to do it myself). I am not about to waste my time on such acrobatics. Just debug on 32 bit browser is fine with me. -- 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.
