UPDATE: Not sure I'd say I'd managed to 'solve' the issue as I can't trace exactly what I did to get it to work - but I now have sketches running in an Android emulator! 

Following up on the final lines of the console message ("....Error: This platform has more than one ABI. Please specify one using --abi........at bottom of ensure proper"), I focussed on trying to work out what having more than one ‘ABI’ meant – and what I could do about it….

Here’s a summary of what I think I found out, followed by what I did.
Please feel free to jump in and correct my interpretations…..

Ok….

It seems from this site that an ABI (an Application Binary Interface) can come in various types: an ‘armeabi’, an ‘armeabi-v7a’, a ‘x86’ and a ‘MIPs’…. Android devices all use one or the other and they all appear to be different proprietary alternatives for each other ….

Although from here it seems that the large majority (possibly over 90%) use ARM (possibly as this was developed first…) and Intel Atom x86 and MIPs are relatively recent inclusions…..

You need to create a separate AVD for each ARM or MIPS target you want to test – this is specified by the ‘CPU/ABI’ field in the ‘new AVD’ or ‘edit AVD’ wizard….

It has already been noted here that the Android emulator  plug-in doesn’t work if there are multiple ABIs.

Because the persistent error I was getting kept telling me that my ‘platform had more than one ABI’ but I didn’t know how to use the ‘--abi’ command it suggested, instead I tried uninstalling the Intel x86 Atom System Image from the appropriate Android level (in my case API 10)

I also wiped all the old AVDs and set up a new API 10 AVD without specifying whether ARM or MIPS to see if the system would pick the one that it needed….. 

I launched the emulator and, once that was running, I pressed ‘run in emulator’….

And lo! …… after 3 days going in circles….. it worked!

 

...The only problem is that by doing both changes at once, I can’t be sure which one resolved the problem…

I’ve since reinstalled the Intel x86 Atom System Image without any recurrence of the problem, but ……I also note that I now have TWO AVDs  in my AVD Manager – my original ‘Processing-Android-7’ that I set up and a brand new, apparently Processing generated ‘Processing-0216’ (I’m assuming this is the one that Ben Fry said the system would generate….)

 

However, what’s more, when I open up each in ‘edit AVD’, they both now specify ‘ARM (armeabi)’ in the ‘CPU/ABI’ field (even though I deliberately didn’t specify anything) – but both have a differently laid-out edit panel….

  I’ve no idea which action (uninstalling the Intel x86 Atom System Image or leaving the CPU/ABI field greyed out) prompted the system to kick in and generate the AVD it needed – just glad it did!

 

Just hope this helps someone else avoid losing the same amount of time and sanity trying to resolve this!

 

All best,

Tom 

So just to confirm if anyone else is getting the error for multiple ABI, I was able to solve this problem in the SDK manager by uninstalling the intel x86 image.

Create a new AVD like yours solve my problem, now I can run the sketch in a emulator. Thanks man!

I had just the exact same trouble. Uninstalling the intel x86 image was the way to go.

Just want to confirm.  Uninstalling the "Intel x86 Atom System Image" (API 10) worked for me too. The emulator starts and works fine. Thank you :) !  

just to add too...deleting "Intel x86 Atom System Image" worked for me as well.