[Rcpp-devel] Issues creating static library using Makevars

[Toby Hocking]

Right, Writing R Extensions is a great reference.
To clarify the question, we are developing a package like RInside, which
contains some compiled C++ code that is not meant to be used from R main.
We would like to distribute the C++ source code in an R package (like
RInside), so we are trying to figure out how RInside managed to do this and
satisfy CRAN checks.
Looking at current CRAN checks for RInside
https://cloud.r-project.org/web/checks/check_results_RInside.html I see
some similar NOTE / WARNING ... are these new in the last few months, or
were they there when you submitted to CRAN? i.e. did CRAN accept the
submission even with such NOTE / WARNING? Just trying to figure out the
best way to package this compiled code so that CRAN will accept it.
Any tips/tricks you have discovered from your experience with RInside would
be appreciated.
Toby

On Fri, Jun 26, 2020 at 8:08 PM Dirk Eddelbuettel <edd at debian.org> wrote:

>
> On 26 June 2020 at 15:55, Akhila Chowdary Kolla wrote:
> | But when I check the package I get the following warnings: using
> | devtools::check()
> | ‘../inst/include/Log.o’   File ‘testproject/libs/testproject.so’:
>  Found
> | no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’    Compiled code
> | should not call entry points which might terminate R nor write to
> | stdout/stderr instead of to the console, nor use Fortran I/O nor system
> | RNGs. It is good practice to register native routines and to disable
> | symbol search.*
>
> See "Writing R Extensions"
>
> |   *Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’  - why
> is
>
> See "Writing R Extensions"
>
> | this necessary as I am trying to compile some external C
> | files(inst/include/DeepState.c) which are not in src folder*
> |    *Compiled code should not call entry points which might terminate R
> | nor write to stdout/stderr instead of to the console, nor use Fortran
> | I/O nor system RNGs. - what does this mean?*
>
> See "Writing R Extensions"
>
> | how can I solve this issue and get rid of the warning in the R CMD check?
> | Can someone please suggest a way to resolve this?
>
> See "Writing R Extensions" -- nobody here on the list "makes the rules".
> Only
> R Core / CRAN do. We all just try live by them.
>
> Dirk
>
> --
> http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
> _______________________________________________
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20200627/ee9e3382/attachment.html>