You do not appear to understand the intent of Sqlite. It is an open source software library which can be comiled to siuit unique application requirements. Decide what features you want to use and set the conditional compilation flags accordingly and com;pile it to all the platforms you intend to use. You will then get exactly what you want.
W Allan Edwards wrote: > I also emailed the mono project guys about this because they utilize the > ado.net code that I am having issues with on top of sqlite on linux. > > My what I have gathered, you compile your .net app with the managed only libs > from the ado.net provider for sqlite. Then on windows that code interops > with the sqlite library on windows (and this works). After you move your > code over to linux, you run the assemblies under the mono .net run time and > it loads the sqlite lib available to it on linux. In fact, the app actually > works against sqlite until that meta call is called... So I know that the > sqlite native lib must be getting loaded by the mono runtime on linux > successfully. But of course, it is the one wihtout that method, then the > runtime explodes and I get that import message. > > FYI.... > > http://sqlite.phxsoftware.com/ > > From: silicon_pla...@hotmail.com > To: sqlite-users@sqlite.org > Subject: RE: [sqlite] Question on missing Entry Point for Sqlite 3 > Date: Sun, 8 Feb 2009 22:47:33 -0600 > > > > > > > > > > >> That doesn't make any sense. (you sound like all my old girlfriends) Did >> you mean sqlite3.c? If you define the >> same thing multiple times in the same compilation then the compiler >> usually complains. >> > > - I downloaded the sqlite-amalgamation-3.6.10.tar.gz > - exploded the archive on my drive > - .configure > - grepped for that define > - changed the sqlite.c file in the most appropriate spot I could find > - make > - sudo make install > - copied by build into where I believed the lib was getting picked up from by > the mono ado.net provider > - run my ap... CRAPPPPPPPPP!!!!! > > -------------------------------------- > > >> I would fix the provider to catch the entrypoint not found exception and >> gracefully deal with the issue. >> > > I agree with you on this. I have emailed those guys. > > --------------------------------------- > > >> If not doing that then I would build a private copy of SQLite using >> configure: >> >> ./configure CFLAGS=-DSQLITE_ENABLE_COLUMN_METADATA \ >> --prefix=/usr/local/customsqlite --disable-tcl >> make install >> >> > > I believe I will go with the special compilation, then figure out how to for > sure make my compile of sqlite get loaded by the ado.net provide on the mono > side. > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > > >> Date: Sun, 8 Feb 2009 20:18:31 -0800 >> From: rog...@rogerbinns.com >> To: sqlite-users@sqlite.org >> Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3 >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> W Allan Edwards wrote: >> >>> By preprocessor do you mean #define? >>> >> It is a #define if in C source and -D if a compiler argument. >> >> >>> I did a search in my sqlite.c file for >>> >>> SQLITE_ENABLE_COLUMN_METADATA.. then I #defined above them ALL! >>> >> That doesn't make any sense. Did you mean sqlite3.c? If you define the >> same thing multiple times in the same compilation then the compiler >> usually complains. >> >> >>> Instead of telling me this was incorrect... >>> >> The SQLite documentation and my messages gave the precise terminology >> and accurate answer. We have no idea how you are deciding to install >> SQLite as there are several ways to make use of SQLite. Mind reading is >> not available on this list. Generally you should ask if after >> researching and trying you don't know. You'll find this helpful: >> >> http://www.catb.org/~esr/faqs/smart-questions.html >> >> >>> why not tell me what your approach might be? >>> >> I would fix the provider to catch the entrypoint not found exception and >> gracefully deal with the issue. >> >> If not doing that, then I would make the provider use a static compile >> of SQLite (ie directly including the amalgamation with whatever flags >> needed which would then not use the system SQLite and just work. >> >> If not doing that then I would find the Linux distribution package and >> rebuild the package to include the functionality. >> >> If not doing that then I would build a private copy of SQLite using >> configure: >> >> ./configure CFLAGS=-DSQLITE_ENABLE_COLUMN_METADATA \ >> --prefix=/usr/local/customsqlite --disable-tcl >> make install >> >> And if that won't work then I'd dump the provider for a piece of decent >> software. >> >> Roger >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.9 (GNU/Linux) >> >> iEYEARECAAYFAkmPrpMACgkQmOOfHg372QTo6QCg2SPTOFCcfqSXnYHV3GMq5pL3 >> v7MAn2Ettj55wGDoZas9xqz7aS65zSJf >> =ZQxO >> -----END PGP SIGNATURE----- >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
