Hello, Turns out, the main error I was experiencing was due to a native library. The ABI for libcom_couchbase_touchdb_TDCollateJSON.so was set to armeabi and this does not automatically copy the lib to armeabi-v7a. The core TouchDB project now compiles and it seems that it is able to create/delete databases.
I will check the binding generator warnings as you suggested. Thanks Atsushi Narayan -----Original Message----- From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Atsushi Eno Sent: July-04-12 3:08 AM To: Discussions related to Mono for Android Subject: Re: [mono-android] TouchDB-Monodroid Hello, Narayan Sainaney wrote: > > Hello, > > I am trying to create a Monodroid wrapper for the TouchDB project > available here (https://github.com/couchbaselabs/TouchDB-Android/) > cool :) > TouchDB is a lightweight embedded database that supports sync to cloud > based couchbase DB's such as http://www.iriscouch.com > > I am just now learning about Java Bindings projects in Monodroid and > figured I might as well do so on an open source project. The > TouchDB-Monodroid project is available to everyone at: > http://github.com/nsainaney/TouchDB-Monodroid. > > I have already run into some issues. The TDListener class in > TouchDB-Android-Listener project exposes the following constructor: > > public TDListener(TDServer server, int port) { > > this.server = server; > > this.httpServer = new TDHTTPServer(); > > this.httpServer.setServer(server); > > this.httpServer.setListener(this); > > this.httpServer.setPort(port); > > } > > However, the Binding Project generates: > > protected TDListener (IntPtr javaReference, JniHandleOwnership > transfer) : base (javaReference, transfer) {} > This is a mandatory generation for any MfA binding class that interoperates with java objects. Take it as an infrastructure member. > > The TDHTTPServer and TDHTTPServlet classes are not mapped. I am > assuming I'm missing some sort of reference however, I have all the > appropriate ReferenceJars so I'm not entirely sure what's wrong. > There are couple of possibilities for this kind of "missing types". We have explained many of them in our troubleshooting list. http://docs.xamarin.com/android/tutorials/Binding_a_Java_Library_%28.jar%29#Troublshooting_Bindings The build output (likely) contains a lot of binding generator warnings that will help you find the reason why they are missing. Atsushi Eno _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
