Hello,
at last I was able to successfully compile the sqlite3.dll with json1 extension included in a way that our WinRT application works with it seemingly without problems. The process how I got it working has however been really..lets say "experimental" and therefore I would love if anyone could validate my steps or give us some tips on what could have been done better. >From the available guides this one proved to be the most useful: >https://sonyarouje.com/2014/07/17/compile-sqlite-for-winrt-with-fts4-unicode61-support/ However following this guide completely proved to not work as I was unable to complete nmake command with FOR_WINRT=1 parameter if I didn't call "fossil checkout winrt" command first. When I checked out winrt trunk, and modified Makefile.msc to include -DSQLITE_ENABLE_JSON1, the resulting dll did not work with json functions. The working solution seems to be the one where I don't call "fossil checkout winrt" but don't use FOR_WINRT=1 parameter with nmake command. 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. This however is combination of steps, that was not mentioned in any guide so I have my doubts w/e it is correct. Could anyone give us some confirmation w/e my approach was valid, or give us tips on what we could have done better? Thank you very much, SVORADA Peter ****************************************************************************** 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. []
