On Jul 20, 2018, at 11:51 AM, sudeep singh <sudeepsingh1...@gmail.com> wrote:
>
> Our application supports iOS, android and windows(UWP).
Xamarin’s standard assumption is that you’re building your application with
all-CLR code, which is why it’s trying to treat the DLL as a .NET assembly.
That in turn means that even once you get past the .a vs .dll problems others
are helping you with, you’re still stuffed because it’s going to create a
native DLL for the platform you built it on, which won’t work on the ARM CPUs
in your iOS and [probably] Android devices. And on macOS, you won’t need a DLL
anyway, you’ll need a .dylib file.
I think the only way to make it work is to cross-compile the library separately
for all four(!) platforms, then use Xamarin’s native code linking functions.
The fourth platform is macOS, since without a native build of the SQLite + SEE
library, you won’t be able to test and debug the application on macOS.
The following thread shows one way to do it which will work for iOS and macOS,
each a separate build:
https://forums.xamarin.com/discussion/37935/native-dylib
Windows native and Android native build and linkage steps will differ.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
