Guillaume Perrot wrote: > Yes, I encountered this problem with v1.0, I resolved it like this : > * Close Eclipse > * Save your files under .android if you want (Optional) > * Remove totally .android (rm -Rf) > * Relaunch eclipse -> the error message should not appear and android > launching will work from eclipse > * Restore your saved files into .android (optional)
Even that (minus the Eclipse parts) wasn't sufficient for me on Linux. I wound up having to make both the .android tree and my SDK tree (under /opt) have 777 permissions before the emulator would launch. Now, 777 might have been overkill, but I was getting frustrated and didn't feel like messing around any further. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.2 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
