Thanks Jon, that helped a lot. I finally figured it out: I wasn't aware that I could reference other binding projects. I had tried that initially and it didn't help. I was able to remove the reference to maps.jar and osmdroid-android.jar and use the generated bindings instead as references. Then I simply removed a node and it worked. It may be useful to mention that you can resolve jar dependencies by adding the bindings projects as references.
Jeremy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Pryor Sent: Tuesday, September 18, 2012 11:08 AM To: Discussions related to Mono for Android Subject: Re: [mono-android] Battling jar bindings On Sep 18, 2012, at 10:56 AM, "Jeremy A. Kolb - ARA/NED" <[email protected]> wrote: > It's definitely not in this case. I've added the jar to a project in eclipse > and I can see the class that I want so I know that it exists in the jar. Just because it's present doesn't mean that it's bindable, for a variety of reasons (frequently due to tooling limitations...). What would be help would be to enable diagnostic build output, clean + rebuild your Java Bindings Library project, and provide the diagnostic output. Specifically, you're looking for: Tool .*generator.* execution started with arguments: Following that are frequently warnings about types that are being skipped and why they're being skipped. - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
