Yup, our application heavily depends on the full-text search, so that's another option I enabled.
Thank you very much, I will feel much, much safer now when presenting my results to collegues. SVORADA Peter ________________________________________ From: sqlite-users-bounces at mailinglists.sqlite.org <sqlite-users-bounces at mailinglists.sqlite.org> on behalf of Richard Hipp <d...@sqlite.org> Sent: Thursday, April 21, 2016 4:20 PM To: SQLite mailing list Cc: Dalibor Zliechovec Subject: Re: [sqlite] JSON vs. WinRT vs. SQLite On 4/21/16, Peter Svorada <Peter.Svorada at afsi.com> wrote: > > The working solution seems to be the one where I don't call "fossil checkout > winrt" Correct. The "winrt" branch has long since been merged into trunk. See https://www.sqlite.org/src/timeline?n=100&r=winrt for details. > All I did was > include following lines in Makefile.msc > > > OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_JSON1=1 > > OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_FTS4=1 > > OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_OS_WINRT=1 > > > When I build sqlite3.dll afterwards, the app seems to be working fine and it > recognizes json functions. That looks right. You have also enabled FTS4, as I'm sure you recognize. -- D. Richard Hipp drh at sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ****************************************************************************** This email and any files transmitted with it are confidential and may be subject to copyright. They are intended solely for the use of the individual or entity to which they are addressed. If you have received this message in error please notify AFS immediately by return email. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of AFS, except where an authorized sender specifically states them to be the views of AFS. It is your responsibility to verify this email and any attachments for the presence of viruses. AFS accepts no liability for any damage caused by any virus transmitted. []
