Can someone clarify this point please? I mean, if I want to compile sqlite in a way that it should be able to load extensions, SQLITE_CORE could be defined or not? Or if it doesn't matter, what is its role?
Thanks. --- Marco Bambini http://www.sqlabs.net http://www.sqlabs.net/blog/ http://www.sqlabs.net/realsqlserver/ On Jul 30, 2008, at 3:45 PM, Mihai Limbasan wrote: > Kevin Tang wrote: >> Dear all, >> >> After I upgrade to SQLite 3.6.0, I found that I must add >> "SQLITE_CORE" in >> PreProcessor to build my program. >> >> What is the "SQLITE_CORE" use for?? >> >> Thanks, >> Kevin Tang. >> >> > When defined, SQLITE_CORE prevents the redefinition of some API > functions in sqlite3ext.h. From that file: > > /* > ** The following macros redefine the API routines so that they are > ** redirected throught the global sqlite3_api structure. > ** > ** This header file is also used by the loadext.c source file > ** (part of the main SQLite library - not an extension) so that > ** it can get access to the sqlite3_api_routines structure > ** definition. But the main library does not want to redefine > ** the API. So the redefinition macros are only valid if the > ** SQLITE_CORE macros is undefined. > */ > > _______________________________________________ > 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
