Thank you Nuno and Joe for your help. I have posted a new version, now called extension-functions.c, which works on external interfaces only and therefore does not require the sqlite3 source code. I have made everything a single C file with instructions as a comment at the top, hence no need for a tarball. I made some revisions so that it will compile without warnings under Mac OS X, which is fussier about unsigned vs. signed chars.
Liam On 9/15/07, Nuno Lucas <[EMAIL PROTECTED]> wrote: > > On 9/14/07, Liam Healy <[EMAIL PROTECTED]> wrote: > > I tried eliminating sqliteInt.h and replacing with explicit declarations > > of i64 and u8. That part worked fine, but func_ext.c also uses > > sqliteMalloc > > void *sqlite3_malloc(int); > void *sqlite3_realloc(void*, int); > void sqlite3_free(void*); > > are the right functions to use (they are in sqlite3.h). > > > which is also defined in sqliteInt.h which led me down a rabbit hole of > > pulling > > more and more from sqliteInt.h, and I still can't eliminate the errors > and > > warnings. As a reminder, I didn't write the original source code, and I > > have > > only the vaguest sense of the meaning and need for these functions. So, > if > > anyone has any insight on how to accomplish the same goal without using > > internal definitions, I'd appreciate hearing about it. > > I attached a patch with the required changes just to compile using > only <sqlite3.h>. > Used the current source code of the extensions on the contrib page. > > This is not enough to create a sqlite module, but at least it compiles > without using the private sqlite headers. > > > Regards, > ~Nuno Lucas > > > > > Liam > >
