c and sqlite

Argh! OK, what about this precompiled one?

Just saw your edit. Hooray! :)

Now, is there enough there to figure out what’s wrong with your own code?

Now, is there enough there to figure out what’s wrong with your own code?

I didn’t do sqlite3_initialize();

Edit: Actually, in my test app from a couple of days ago I’d forgotten the call to sqlite3_initialize();. Could this possibly be the same issue? Apparently I didn’t document this anywhere, which is probably my fault :)

Yup, I can confirm that this is the issue. Thanks! :)

JFYI, the GCC library port doesn’t requires sqlite3_initialize(). I am mentioning this here for reference for the future, given we actually have two different ports…

I’ve updated the “Notes” section in the other thread accordingly.

I suspect that the other build isn’t defining SQLITE_OMIT_AUTOINIT, and therefore it’s initialising the library automatically. The SQLite devs recommend defining it, so I do.

I need to revisit this topic..
I have a sqlite library compiled with gccsdk. I can open a database file, but when running statements I get “Not a database file”.. perror gives me “no such file…”. unixlib handles riscos paths just fine, /app$dir/file which I guess gets into sqlite3_open16.When done with a $ in filename it doesn’t work with sqlite_open without the “16”.

I am running out of ideas.. Does sqlite need some special treatment for file paths?

Versions after 3.19.4 have that problem with gccsdk.

This version can be downloaded from here for static libraries and here for shared libraries.

Thanks.. I use new gcc , but managed to compile. It works.