On Tue, May 3, 2011 at 3:31 PM, jeff archer <jarch...@yahoo.com> wrote:
> >I believe any compilation options that require changes in SQL parser > >require compiling from original sources as well. They cannot be used > >with amalgamation file which has already generated SQL parser's code. > > > >Pavel > > OK. But this call in the parser source... > > sqlite3FinishTrigger > (pParse, yymsp[-1].minor.yy203, &all); > Should be enclosed in... > > #ifdef SQLITE_OMIT_TRIGGER > sqlite3FinishTrigger(pParse, yymsp[-1].minor.yy203, &all); > #endif > You are looking at machine-generated code. If you rerun the "lemon" parser generator with the -DSQLITE_OMIT_TRIGGER option, then the lines of code above will not appear in the output at all. Rebuilding sqlite3.c is more involved that simply rerunning "lemon", though. You have to combine the output of lemon with the output of 4 other machine-generated files as well as dozens of hand-written code files, in exactly the right order. Your best bet is to (1) get a unix box of some kind, (2) get a copy of the canonical source code, (3) edit the Makefile to include -DSQLITE_OMIT_TRIGGER, and (4) type "make sqlite3.c" > > Jeff Archer > Nanotronics Imaging > jsarc...@nanotronicsimaging.com > <330>819.4615 > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
