This isn't quite what I'm looking for. I understand that resulting binaries are endian dependent, and the database file itself is endian portable after version 3. What I'm really asking (though not as clearly as I had hoped ;-)) is whether or not the sqlite source code is endian dependent.
If it is, I assume that configure/make work some "magic" to generate sources for the target endian platform. If the source is endian independent, I expect that I could use the pure c source provided for windows users and let xcode target mactel, ppc or universal during compilation. A quick search through the sqlite source release led me to believe that the source may be coded around endian issues. I guess what I'm looking for is affirmation or denial of my cursory reading. If the source is endian dependent, how does sqlite configure and/or make determine the endian nature of the platform on which it is building? What does it change? If I know these things, I suspect that I can build a project that either runs configure as part of the process, or does the same things that make/configure do to make endian-ness correct. If these aren't documented somewhere, I can reverse engineer configure/make, but I was hoping that someone here might have the answers. Thanks again! Pat -----Original Message----- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Monday, July 03, 2006 10:04 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] endian-specific code in pure c source release? Sqlite data is endian agnostic, but the executables are, like any executables, dependent upon the endian nature of the host processor. Just compile the Sqlite library for each platform and share the data. On platforms other than Windows use configure, otherwise use the prepared windows source. If you make any extensions to Sqlite, such as your own functions, they will be platform independent. By using the regular Sqlite source distribution you will be able to upgrade easily, and not have your application rev-locked. Pat Wibbeler wrote: > For a couple of reasons: > * I'd like to use xcode to build a universal binary. If I run > ./configure, I imagine that any endian specific code that is fixed using > configure will be set to whatever platform I run configure on (i386 or > ppc). > * I already have the packaged source for a windows build using visual > studio and I'd like to use the same sources if possible to avoid > confusion. > > Pat > > > -----Original Message----- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Monday, July 03, 2006 9:24 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] endian-specific code in pure c source release? > > Why not use the regular source and run configure? > > Pat Wibbeler wrote: > >>I'd like to build an xcode project for sqlite. One straightforward >>approach is to take the sqlite-source-3_3_6.zip "pure c" source > > release > >>and build the xcode project from that. >> >>Is there any endian specific code in that source release that might > > trip > >>me up on power pc processors? I ask this because I know that this >>release is "provided as a service to MS-Windows users who lack the > > build > >>support infrastructure of Unix." >> >>Thanks! >> >>Pat > >
