Tom: Thanks for the information and I will be looking at the slideshow soon.
This project was an InDesign plugin project, which, by agreement when I use the SDK, is a C++ project. I could probably fit in all of the Objective-C code you suggest, but (okay, this is a whine) the InDesign SDK is already immensely complex. I will say that I tried using the SQLite3.dylib that comes native with the OS, though I didn't attempt any of the steps you suggest. I got some fascinating results at link time. Two symbols were identified as not being found in three functions (both symbols went missing in all three functions). What makes it interesting is that both functions were used dozens of times in the plugin, but they were identified as missing symbols only in those three functions. By luck (and the help of a Mac aficionado who is also a colleague) we stumbled across a way to get SQLite3 to compile and link without error or warning. How we did it is provided in a previous email sent last evening, but I would be happy to share it again for anyone who finds him(her)self in the same boat. Take care, John > -----Original Message----- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > On Behalf Of BareFeetWare > Sent: Thursday, May 26, 2011 8:54 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] SQLite in Xcode > > On 27/05/2011, at 10:42 AM, Simon Slavin wrote: > > > Tom, John ran across two common problems with SQLite and Xcode: > > > > A) Xcode seems to want to interpret .c and .h files as C++ instead of C. > > B) Confusion common to people who normally program for Windows or non- > Open systems about what combination of files they need: a library, a > framework, C > source, a .h file. > > > > An explanation of these points somewhere would be great. > > I bypassed that whole issue by just using the SQLite framework built into Mac > OSX > and iOS, and by using an SQLite wrapper for Objective C. Then you don't have > to > worry about compiling SQLite source files into your project or even have to > bother > with the low level sqlite3_ C calls. The only code you then have to write is > effectively an nice Objective-C executeQuery: method call, which returns and > array of dictionaries. It's all very straight forward that way. > > The slideshow makes it pretty easy to follow: > http://www.barefeetware.com/sqlite/iosxcode/?ml > > Thanks, > Tom > BareFeetWare > > -- > Comparison of SQLite GUI tools: > http://www.barefeetware.com/sqlite/compare/?ml > > _______________________________________________ > 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
