Sorry about that. I'm using 2.8.16, and we just changed it to compile into a lib that is statically linked into the executable (with no DLL) . I encountered a very similar sounding problem, so I thought I would offer our solution.
I guess that sqlite3 is organized differently. I just looked and confirmed that sqlite3.h doesn't seem to have those values defined. -----Original Message----- From: D. Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, August 15, 2005 5:37 PM To: [email protected] Subject: RE: [sqlite] Linking libsqlite statically On Mon, 15 Aug 2005, Aaron Schneider wrote: >>> If you compile and use the header files from the projects, they will >>> add a __declspec(dllimport) to the beginning of the files. In >>> Visual > >>> Studio, this changes the symbol defs, so functions used in your > linked >>> code will not work. >>> >>> To fix it, just change the "#define SQLITE_EXPORT >>> __declspec(dllimport)" to "#define SQLITE_EXPORT" near the top of >>> sqlite.h. >>> >> >> Project? DLL? Visual Studio? I said I was using Linux and g++ > > I know you're not using Visual Studio. But I'm guessing that g++ does > something similar. Make sure that the macro SQLITE_EXPORT is not > equal to __declspec(dllimport), recompile all of the object files, and > see if that works. > But I'm using the libraries that came with my distribution. I didn't compile them myself in the first place, and I shouldn't have to go editing system files just to statically link something. In any event, I checked in sqlite3.h and it doesn't even contain a "#define SQLITE_EXPORT" line. -- David Kettler [EMAIL PROTECTED]
