On 24.06.2023 19:44, Dirk Eddelbuettel wrote:
On 24 June 2023 at 21:35, Stephen Wade wrote:
| Doesnt seem like the system package is worth it. Should the convention
| simply be to bundle the headers in the package then? What about package
| size - is there some limit to the size of included l
Cheers Dirk and Simon for your advice, very helpful and clear.
It's certainly a complex problem, way above my experience and pay grade.
I've decided the solution for me would be to remove the dependency on Eigen
altogether, as I am only constructing and accessing sparse matrices at the
library-le
On 24 June 2023 at 21:35, Stephen Wade wrote:
| Doesnt seem like the system package is worth it. Should the convention
| simply be to bundle the headers in the package then? What about package
| size - is there some limit to the size of included libraries/headers to
| consider for CRAN?
Here is
Doesnt seem like the system package is worth it. Should the convention
simply be to bundle the headers in the package then? What about package
size - is there some limit to the size of included libraries/headers to
consider for CRAN?
On Sat, 24 June 2023, 15:08 Simon Urbanek,
wrote:
> Stephen,
>
Stephen,
If you want to give the system version a shot, I would simply look for
pkg-config, add the supplied CPPFLAGS to the package R flags if present and
then test (regardless of pkg-config) with AC_CHECK_HEADER (see standard R-exts
autoconf rules for packages). If that fails then use your in
I recently submitted a package to CRAN which downloaded Eigen via Makevars
and Makevars.win. My Makevars.ucrt was empty as I noted that Eigen3 is
installed by default (however, this doesn't ensure that a version of Eigen
compatible/tested with the package is available).
The source is currently on
