This might seem like a dumb question but I am getting conflicting information from web sources.
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1218086.html I'm trying to enable unicode61 tokenizer for a build on iOS. Apple frowns upon including your own libicu since they include their own libicucore.dylib and restrict access to how it is used purely through their NSString APIs. The above link suggests I can simply compile sqlite with -DSQLITE_ENABLE_FTS4_UNICODE61 but not needing -DSQLITE_ENABLE_ICU. I have tried this with v3.8.5 and get errors that the unicode61 tokenizer is not recognised. Which makes sense to me, since presumably sqlite relies on ICU for it's definition of 'what is unicode' (as it is a moving target it would seem). So is it possible to have an ICU-less build that allows the unicode61 tokenizer? Or should I look at writing a custom tokenizer that hooks into the allowed NSString API? Kind Regards -- Josh Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
