From: Staffan T. <sta...@gm...> - 2014-10-07 22:04:13
|
Thanks hex, I will try to compile without codec and see if it works. Apparently some major changes have been made to ooSQLite since level 9969 when I didn't have any problems to compile even with codec. I know Mark added support for encryption but maybe this now has been taken away, one can ask. I guess the change history would tell. Staffan On Tue, Oct 7, 2014 at 9:11 PM, hakan <he...@us...> wrote: > Message was cut, here it is again > Staffan > I believe you are compiling with encryption and maybe these errors are > from that circumstance. > The Changes I suggested is for unencrypted oosqlite, If you can try to > remove > /DSQLITE_HAS_CODEC in your compile line, we will see If that will let > oosqlite compile as it did for me > I am a real novice in this area. > Maybe you also need to compile the APICOMMON as it uses OOrexx libraries. > > I have a note that to be able to use /DSQLITE_HAS_CODEC you must add to > sqlite3.c > #include "codecext.c" > but I think it's something more to do, can't find my notes on that. > I haven't succeeded to compile with encryption since your suggestion to > use botan, IRC, years back. > As I said I'm a novice on this. > /hex > > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |