I'm just starting out with GWT but I can't even run the getting started example without getting the following error:
Invalid memory access of location 0x10 eip=0x93624148
I am aware of the "java hosted mode 32 bit" stuff, anyway I tried every combination I could think of and still could not get away with that error.
I tried:
Using the eclipse plugin
Setting all possible jvm switches in eclipse to 1.5
Use the command line tool
Set the java environment to java 5 32 bit in the preference pane, and do all of the previous options again, without success (I checked that effectively "java -version" gives me the right 32 bit jvm)
Any suggestion? I can't believe that something which should be apparently immediate is so difficult ...
Thanks for your help
Best regards
Nicola Montecchio
Seems to be fixed in GWT 2.0.
Alternatively, try using the WebKit Nightly.
Steps here:
http://grack.com/blog/2009/11/16/fix-for-gwt-hosted-mode-crash-with-safari-4-0-4/
See release notes for latest SDK 1.7.1.
You might need to switch to Snow Leopard to get it working.
Update: GWT 2.0 is just out today. Give it a go, even thought I've not seen anything related to Leopard in the change list.
I used gwt a lot on my mac with OS X 10.5 on. It actually worked fine. Have you also set the java class version in the projects facets menu in the project preferences to java 5?
You can also provide which java to use in the launch configuration, you don't need to modify in the Mac OSX preference pane.
I actually upgraded to 10.6 when it came out, and it made life with GW easier.
Hope it helped, if you have any more questions let me know.
Best - István
Related
I have Mac OS X 10.9 and Java SE Runtime Environment (build 1.7.0_17-b02)... I had another version of JEdit (I guess JEdit 4) and Java 6 before and my JEdit was working fine.
Then I upgraded Java to Java 7 because NetBeans7.4 needed to be installed with Java 7 (and I needed this new NetBeans because I had a fatal issue with NetBeans 7.3.1). So anyway, I installed Java 7 and I installed NetBeans 7.4 and my netbeans is working perfectly now, but when I tried to run the JEdit it brought up an alert saying it needs Java SE 6 to run!
I did some search in the net, and it seems that JEdit 4.5 (and I guess JEdit 5.1 too!) should not have any issue with Java 7, So I installed JEdit 5.1.0... I expected that it should work and don't bring up that complain alert BUT it didn't work and brought up "Java SE 6 is needed" complain again ...
I still can run JEdit using this command, but I can't use Cmd+C & Cmd+V shortcuts for copy and paste and it kills me!
java -jar /Applications/jEdit.app/Contents/Resources/Java/jedit.jar
Is there anybody who knows why JEdit 5.1 is complaining about Java 6 and how to fix it?! I really appreciate your help!
https://sourceforge.net/tracker/?func=detail&aid=3615181&group_id=588&atid=100588
After almost 3 months struggling with jEdit I'm ready to give up... I still can't run jEdit like a normal app. What do you suggest to replace my jEdit?! The main feature I need is realtime access to the server files... Most of editors keep a local version of files, so they don't show the changes when they are made in the server side. for example when I switch to a new git branch on server, my netbeans is still showing the branch that I was working before switching, so I need to do a complete download on the project. Any idea?!
#Monica About one year later after your question, I've experienced the same issue with Mountain Lion (according to jEdit's homepage, 5.1.0 is still the current stable version).
I've installed jEdit in /Applications/Dev/ (not /Applications as most people do, I believe; that's not important except for designating the path, see below). I'm using Java 7.
The following works for me from the command line, like for you:
java -jar /Applications/Dev/jEdit.app/Contents/Resources/Java/jedit.jar
So, I used Automator to create a normal MacOS Application named "MyJEdit.app" as in the screenshot. Now I can launch MyJEdit instead of jEdit. Other java flags might be required, for instance to set the memory usage (cf java -help and java -X).
jEdit on Mac OS X and Java 7 is a long story of annoyances, and fine points that Apple did not get quite right up to Java 6, and Oracle still learning about native platform support in the past 1-2 years.
Starting with Jdk-7u40 it works technically quite well, even Retina displays, but jEdit needs to be adapted slightly.
jEdit 5.2 will probably work with Java 7 out of the box, but a few points are still open. See also the tracker item 3615000 at Sourceforge.
Here is a practical proof that it works: Isabelle/jEdit -- it is an application based on jEdit that is bundled differently than official jEdit 5.1.0.
I would like to install ColdFusion Builder 2 Update 1 as a Plug-in for Eclipse 4.3.
The install seems to work without errors but when I attempt to register my license code, I get an error dialog box that says:
"The chosen operation is not enabled."
None of the CFB features appear in Eclipse.
In some of the documentation that I've found it references installing to Eclipse 3.6.
Can CFB 2u1 get installed on Eclipse 4.3? If not, does someone know which version of Eclipse to use for CFB? Hopefully it is something recent or I'm doing something wrong for the install.
I don't know if it matters, but I'm running:
Windows 7 Pro 64-bit
16GB RAM
According to the ColdFusion Builder System Requirements page one needs Eclipse 3.7.1. Having tried to install it on versions later than that, failing, and talking to Adobe about it, they confirmed that one needs that precise version. More recent ones won't do. This is a bit subpar on the part of Adobe, but so be it.
I have done a little work on lazarus' free pascal. So when a client asked me to write an application for a mac, after the initial, "it can't be done" stage. (followed by an asp.net maybe stage) i thought about writing it using lazarus.
Question is. I have only a virtual machine running mac OSX, this means that i do not really want to develop on the mac. However, i just cannot seem to get the applications that i have written in lazarus on windows to work on the mac. I have tried the deployment using the Lazarus Wiki and the MACOS folder is empty and so when i put it on the mac it doesn't run the application.
What is the best way of doing this or am i barking up the wrong tree?
It seems you want to do cross-compiling, which is theoretically possible, but may not be practical, for the reasons mentioned by Marco above.
As an alternative, you could install XCode, FreePascal, and Lazarus on a MacOX machine. You could still do your development and some testing on Windows/Linux. When you hit a certain milestone, you can copy your source code to the Mac and compile your application to test and give to the user.
Even if it were possible to easily cross-compile, there some minor differences between platforms, so (especially if it's a GUI app), you would want to test it on an actual MacOS box before giving it to the client.
I've taken the route described by Noah - and I was incredibly surprised that after about three weeks development on Windows, it took about 10 minutes to get the application running on the Mac.
My route was to install Xcode 4.3 on an old Mac Mini running snow leopard, then install Lazarus using the fink version as described here. This took a while but was done in an evening.
Then I just copied my folder across to the Mac, opened the lpi on the Mac, compiled it. It failed so I removed a windows references, recompiled, and it was working. I was truly amazed.
What linker and assembler do you use to generate binaries? To my best knowledge the linker for recent OS X versions is not available in source.
Afaik what you want (crosscompiling to Mac) is not possible for recent versions (and I've done it for PowerPC myself in the past).
The easiest is to use the Unix "file" command on the binary to see what is generated, and make sure it reads something with "MachO" in it. Easiest is if you have a Linux install (where this command is pretty standard), but versions can be found for windows too (cygwin, mingw and 3rd party)
I would like to play around with the Java SE version of NetBeans on Mac, however I need to still have a running copy of BlueJ on my Mac for a school class. Is it possible to run the "JDK-only" BlueJ and the "Java SE" NetBeans together in harmony?
Try it and see. My Mac maintains several versions of Java although I don't really know what gets used where.
It might be worth looking at this FAQ: http://www.bluej.org/help/faq.html#macjava5
I recently started creating applications for mobile devices and have successfully completed an application for the iPhone. I am now turning my attention to the Blackberry but haven't been able to find a convincing article or website that states that it can be done or a tutorial on how to do so. Can Blackberry apps be developed on Mac OS X? If yes, how do I go about doing so? Can anyone please point me in the right direction as I only have access to a Mac and really want to get this project on the road. Thanks in advance for your help.
UPDATE:
RIM has released a MacOS Eclipse plug-in for Blackberry Development: http://na.blackberry.com/eng/developers/javaappdev/macosx.jsp
While there is no built-in simulator, the plug-in DOES support USB tethered device debugging for the Torch 9800 handhelds. I plan to get one; they are ~$499 w/no contract. With a Torch and the new plug-in, Blackberry development is possible without using a VM. (Finally!)
PREVIOUS POST:
Building on MacOS works well once you set it up. I've had less luck with the simulator. On the whole though, being able to run Eclipse natively in MacOS and flip to a Windows VM only for debugging is a big win in my book.
You can get a MacOS version of preverify (see link below for details). I do my development with Eclipse on MacOS X and use Ant to build BB apps.
This blog is excellent and has many of the details to get you started:
http://www.azizuysal.com/2009/07/blackberry-development-on-mac-os-x.html (original link is dead. The "wayback machine" provides us with the original text content, but images and styling are lost to the sands of time. Still worth a read.)
The tricky part is getting the simulator to work. There is a Wine-based work-around, but on my computer, while the simulator was able to run under Wine, the LCD output was scrambled.
Currently, I build COD files from Mac, and my Ant build process drops them into a directory that is shared with a WinXP VM. I can run the simulator stand-alone in this VM. Debugging is also possible by installing Eclipse inside WinXP and pointing the debug configuration it at the source directories.
I've actually got a bit more magic. I enabled some of the Java 1.5 features by compiling against 1.5 and then translating the bytecode to 1.3 prior to the preverify script. (Blackberry only speaks a barbaric 1.3 java, flashback to circa 1992). It's not a silver bullet as some features still don't work, but it does cut down on the need to make everything an untyped Object reference.
Lately, I've been working on a x-platform framework to allow me to write app code once and build against both Android and Blackberry (both are Java). The Android part was easy. It's just a bitch to debug anything in Blackberry. Someone working at RIM decided that Blackberry didn't need to keep Exception stack traces unless there was a catch(Throwable), and then they could do something bizarre, non-standard, and undocumented (catching Throwable behaves weird). I've only kinda-sorta figured out a hack to get stack traces using JavaLoader.exe without breaking into the debugger, and it's barely worth it.
p.s., I now do x-platform development with a single code-base targeting Android, Blackberry, and Desktop. Desktop is great for testing app functionality, with very little Blackberry on-device testing needed once features work in the desktop 'simulator' (a Swing GUI built for debugging our games).
Even though certain components of the RIM development platform are java-based, such as the JDE - other components such as the preverifier and device simulators are implemented as native Windows executables.
Basically, the easiest way to do it is to install Windows on your Mac using Bootcamp or Parallels and run inside a real Windows environment on your Mac.
However, there are other "hackier" ways to do it using Wine, MacPorts, and a number of other tools - as an example see this blog post