Re: [sqlite] SQLITE_OMIT_xxx
Hi, Richard Klein wrote: > [...] > (2) Perforce (our version control software) has trouble diff'ing > two versions of a large file. We have the amalgamated sqlite3.c source file under Perforce control here and I don't recall any problems with diff, except I had to wait a bit longer than usual. In your case, it could have been an occasional failure. I suggest reporting the issue to Perforce, they will most probably fix it. -- Dimitri ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLITE_OMIT_xxx
> On Apr 21, 2008, at 4:25 PM, Richard Klein wrote: >> (3) We build SQLite for many different target platforms, using >> various C and C++ compilers. We get many (i.e. hundreds) of >> warnings, and even some errors. When fixing these problems, >> it is simply easier to edit many smaller files rather than one >> huge, unwieldy file. > > As for warnings, see http://www.sqlite.org/faq.html#q17 > SQLite is ANSI-C code, not C++ so if you try to compile > it with a C++ compiler you might well get errors. I suggest > you use a C compiler instead. Surely Visual Studio must > include a C compiler. > > D. Richard Hipp > [EMAIL PROTECTED] Our target platforms are a variety of set-top boxes from various manufacturers, so we're pretty much stuck with whatever toolchain we get from the vendor. The compiler is often ancient, and some- times is for C++ rather than C. We have to make sure our source code, including SQLite, compiles flawlessly in *all* these environ- ments. It's not a big deal, just a minor hassle. - Richard ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLITE_OMIT_xxx
Understood. I use the amalgamated source for maximum performance. Re 1: Look at Source Insight for editing. The only dig I have at it is that it won't let me split a window into the same source file like the VC editor will. Since I do all my building with command line tools, I don't need the build environment in VC. Re 2: Look at using Araxis Merge instead of the Perforce dif tool. Richard Klein wrote: > Thanks, Mark! > > I use the individual source files rather than the amalgamation, > for several reasons: > > (1) Visual Studio has trouble generating line number info for > files that have more than 64K lines. > > (2) Perforce (our version control software) has trouble diff'ing > two versions of a large file. > > (3) We build SQLite for many different target platforms, using > various C and C++ compilers. We get many (i.e. hundreds) of > warnings, and even some errors. When fixing these problems, > it is simply easier to edit many smaller files rather than one > huge, unwieldy file. > > - Richard > > Mark Spiegel wrote: > >> That's what I do. Once your makefile is set up, make the "sqlite3.c" >> target if you want an amalgamated source file. Be sure to carefully >> coordinate the defined values between the preprocessing step (to >> generate your source file(s)) and the build of your application/dll. >> >> If you are using amalgamated source, you may find a few other small >> problems when building your app, but they are easy to fix. >> >> Richard Klein wrote: >> Richard Klein wrote: > In order to reduce SQLite's memory footprint in my embedded > application, I want to use the SQLITE_OMIT_xxx options to > remove unneeded features from SQLite. > > Using Cygwin running on Windows, I have successfully down- > loaded the canonical sources and autoconfigured the Makefile. > > The Makefile seems to indicate that in order to generate > the parser, opcodes, and keyword hash function so that they > omit the unneeded features, I need only add the following > line to the Makefile: > > OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... > > Is this correct? > > > I believe so, but I haven't ever used the OMIT options when building SQLite. Are you having a problem when you do this? Dennis Cote >>> I haven't tried it yet ... I'll let you know if I have any >>> problems. Thanks! >>> >>> - Richard >>> >>> ___ >>> 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 >> > ___ > 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
Re: [sqlite] SQLITE_OMIT_xxx
On Apr 21, 2008, at 4:25 PM, Richard Klein wrote: > Thanks, Mark! > > I use the individual source files rather than the amalgamation, > for several reasons: To generate individual source files run make target_source > > > (1) Visual Studio has trouble generating line number info for > files that have more than 64K lines. Report this bug to Microsoft. > > > (2) Perforce (our version control software) has trouble diff'ing > two versions of a large file. I had similar problems when I was working on the diff-er in fossil (http://www.fossil-scm.org/) but I eventually overcame them. Suggest you report the problem to Perforce. They are welcomed to use my (GPLed) fossil code :-) > (3) We build SQLite for many different target platforms, using > various C and C++ compilers. We get many (i.e. hundreds) of > warnings, and even some errors. When fixing these problems, > it is simply easier to edit many smaller files rather than one > huge, unwieldy file. As for warnings, see http://www.sqlite.org/faq.html#q17 SQLite is ANSI-C code, not C++ so if you try to compile it with a C++ compiler you might well get errors. I suggest you use a C compiler instead. Surely Visual Studio must include a C compiler. D. Richard Hipp [EMAIL PROTECTED] ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLITE_OMIT_xxx
Thanks, Mark! I use the individual source files rather than the amalgamation, for several reasons: (1) Visual Studio has trouble generating line number info for files that have more than 64K lines. (2) Perforce (our version control software) has trouble diff'ing two versions of a large file. (3) We build SQLite for many different target platforms, using various C and C++ compilers. We get many (i.e. hundreds) of warnings, and even some errors. When fixing these problems, it is simply easier to edit many smaller files rather than one huge, unwieldy file. - Richard Mark Spiegel wrote: > That's what I do. Once your makefile is set up, make the "sqlite3.c" > target if you want an amalgamated source file. Be sure to carefully > coordinate the defined values between the preprocessing step (to > generate your source file(s)) and the build of your application/dll. > > If you are using amalgamated source, you may find a few other small > problems when building your app, but they are easy to fix. > > Richard Klein wrote: >>> Richard Klein wrote: >>> In order to reduce SQLite's memory footprint in my embedded application, I want to use the SQLITE_OMIT_xxx options to remove unneeded features from SQLite. Using Cygwin running on Windows, I have successfully down- loaded the canonical sources and autoconfigured the Makefile. The Makefile seems to indicate that in order to generate the parser, opcodes, and keyword hash function so that they omit the unneeded features, I need only add the following line to the Makefile: OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... Is this correct? >>> I believe so, but I haven't ever used the OMIT options when building SQLite. >>> >>> Are you having a problem when you do this? >>> >>> Dennis Cote >>> >>> >> I haven't tried it yet ... I'll let you know if I have any >> problems. Thanks! >> >> - Richard >> >> ___ >> 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 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLITE_OMIT_xxx
That's what I do. Once your makefile is set up, make the "sqlite3.c" target if you want an amalgamated source file. Be sure to carefully coordinate the defined values between the preprocessing step (to generate your source file(s)) and the build of your application/dll. If you are using amalgamated source, you may find a few other small problems when building your app, but they are easy to fix. Richard Klein wrote: >> Richard Klein wrote: >> >>> In order to reduce SQLite's memory footprint in my embedded >>> application, I want to use the SQLITE_OMIT_xxx options to >>> remove unneeded features from SQLite. >>> >>> Using Cygwin running on Windows, I have successfully down- >>> loaded the canonical sources and autoconfigured the Makefile. >>> >>> The Makefile seems to indicate that in order to generate >>> the parser, opcodes, and keyword hash function so that they >>> omit the unneeded features, I need only add the following >>> line to the Makefile: >>> >>> OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... >>> >>> Is this correct? >>> >>> >> I believe so, but I haven't ever used the OMIT options when building SQLite. >> >> Are you having a problem when you do this? >> >> Dennis Cote >> >> > I haven't tried it yet ... I'll let you know if I have any > problems. Thanks! > > - Richard > > ___ > 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
Re: [sqlite] SQLITE_OMIT_xxx
> Richard Klein wrote: >> In order to reduce SQLite's memory footprint in my embedded >> application, I want to use the SQLITE_OMIT_xxx options to >> remove unneeded features from SQLite. >> >> Using Cygwin running on Windows, I have successfully down- >> loaded the canonical sources and autoconfigured the Makefile. >> >> The Makefile seems to indicate that in order to generate >> the parser, opcodes, and keyword hash function so that they >> omit the unneeded features, I need only add the following >> line to the Makefile: >> >> OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... >> >> Is this correct? >> > > I believe so, but I haven't ever used the OMIT options when building SQLite. > > Are you having a problem when you do this? > > Dennis Cote > I haven't tried it yet ... I'll let you know if I have any problems. Thanks! - Richard ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLITE_OMIT_xxx
Richard Klein wrote: > In order to reduce SQLite's memory footprint in my embedded > application, I want to use the SQLITE_OMIT_xxx options to > remove unneeded features from SQLite. > > Using Cygwin running on Windows, I have successfully down- > loaded the canonical sources and autoconfigured the Makefile. > > The Makefile seems to indicate that in order to generate > the parser, opcodes, and keyword hash function so that they > omit the unneeded features, I need only add the following > line to the Makefile: > > OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... > > Is this correct? > I believe so, but I haven't ever used the OMIT options when building SQLite. Are you having a problem when you do this? Dennis Cote ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] SQLITE_OMIT_xxx
In order to reduce SQLite's memory footprint in my embedded application, I want to use the SQLITE_OMIT_xxx options to remove unneeded features from SQLite. Using Cygwin running on Windows, I have successfully down- loaded the canonical sources and autoconfigured the Makefile. The Makefile seems to indicate that in order to generate the parser, opcodes, and keyword hash function so that they omit the unneeded features, I need only add the following line to the Makefile: OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... Is this correct? Thanks, - Richard ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
