appveyor about bikedata HOT 9 CLOSED

Note that RSQLite should install sqlite, and also this commit installs it explicitly with chocolatey which definitely installs sqlite, yet the build still fails. The lsqlite3 library is passed to Makevars by the config file, so that's also not the problem.

from bikedata.

If I remember correctly, RSQLite bundles a copy of SQLite in the package, so never uses the common header files. It looks to me like the sqlite includes directory is not being passed correctly for some reason as it is complaining about sqlite3.h (which the lsqlite3 call would not have any effect on).

from bikedata.

Do you know where chocolatey installs sqlite3 to and if it includes the header files?

from bikedata.

It it doesn't include the header files we may need to revert to something like this.

from bikedata.

Thanks @richardellison for the quick response! Alas, I still can't get it work. No matter what I try, it always fails on sqlite.h: No such file or directory. That even applies when the header (almagamation) files are extracted in to a directory that is definitely on the $PATH. I give up (for the moment at least)!

(One note fyi: The dll can't be downloaded for an R package, because it is then incorporated into the package itself, which consequently fails R CMD check, but the chocolatey install does the job there, so that's okay.)

from bikedata.

and wouldn't ya know it, it's actually a pervasive windows problem: The package fails on win-builder.r-project as well, with undefined references to all sqlite3.h bindings. 👎 Gotta figure this out after all ...

Note that Kirill says on RSQLite that 'Header files for sqlite3 are no longer installed, linking to the package is not possible anymore. Packages that require access to the low-level sqlite3 API should bundle their own copy' (in NEWS.md) - why? The sqlite3.c fiile is now >7MB, which would make for a huge package! There must be a better way ...

from bikedata.

Is it possible to download the necessary files when compiling on Windows only? Wouldn't solve the problem of the Windows binaries being large though.

On the other hand, is 7MB really going to be an issue when the package is intended to download datasets many times larger than this?

from bikedata.

It's really just an appveyor issue - the win-builder machines have no probs finding the headers, and I'd be highly resistant to such a package inflation for reasons that have nothing to do with cran. I'll remain hopeful of a more lightweight solution for a bit longer...

from bikedata.

@richardellison Finally back onto this with what appears to be the only viable solution of just bundling the whole damn lot. Whatever works in the end ... Thanks for your input on this issue. closing now.

from bikedata.