Ok, I definitely do not see how to make this work. I don't grasp how the wrapping method here in any way spares the 1.5 runtime environment from having references to text-to-speech things.
A 1.5 user tried my test build and gets a force close. I redoubled my efforts to manually select a 1.5 emulation target, and if my dependency is 1.6 and minSdk=3, it will not show my 1.5 target. If I compile against 1.6 and then try to trick Eclipse by changing it to 1.5 before invoking the debug upon my 1.5 target. Then, it realizes the trick and balks. I am rapidly realizing that I should have separate products for 1.5 and earlier and one for 1.6 and later. That would be an ugly upgrade transition, as I have taken money from all users for a common build. tone On Feb 4, 9:09 am, Eric Carman <[email protected]> wrote: > Hello Tone, > > You definitely have to target the 1.6 (or greater) platform for this > to compile. > > I remember having trouble getting the debugger to attach to the 1.5 > emulator. I don't remember if I was able to do that or if I relied on > Toast/log messages to zero in on my 1.5 specific issues. I'm not near > the proper computer now to test it out. I vaguely recall having to > make sure the 1.5 emulator was the only one running and I had to start > it explicitly before running the application - not sure why that > mattered, but... > > All of this may depend on what version of the SDK you have installed > (1.6, 2.0, ...). Currently I have installed v2.0. > > HTH > > Best Regards, > Eric -- 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
