Hi, Jason, The assert is from RcppEigen.
I think the reason is how "NDEBUG" is handled by Armadillo. In your package, the RcppArmadillo header is included before RcppEigen: https://github.com/jasonserviss/check/blob/master/src/RcppExports.cpp#L4 In RcppArmadillo: https://github.com/RcppCore/RcppArmadillo/blob/master/inst/include/RcppArmadilloConfig.h#L92-L94 The NDEBUG has been undefined. Then in RcppEigen: https://github.com/RcppCore/RcppEigen/blob/master/inst/include/Eigen/src/Core/util/Macros.h#L549 The assert will be used if NDEBUG has been undefined. I hope this answers your question. Best wishes, KK On Wed, Jun 13, 2018 at 7:05 AM, Jason Serviss <jason.serv...@ki.se> wrote: > Hello everyone, > > I am currently in the process of trying to utilise C++ via Rcpp, > RcppEigen, and RcppArmadillo in a package for the first time. I am > experiencing the following on running devtools::check() with the package: > > checking compiled code ... WARNINGFile ‘check/libs/check.so’: > Found ‘___assert_rtn’, possibly from ‘assert’ (C) > Object: ‘RcppExports.o’ > > > I found a similar problem previously discussed (here: > http://rcpp-devel.r-forge.r-project.narkive.com/yc1h8bf6/ > rcppeigen-package-skeleton-r-cmd-check-warning) some time ago although, > in this case, it seemed to be system specific. Based on the comments, I > created a minimal reproducible example (here: https://github.com/ > jasonserviss/check) and automated the build with TravisCI (build report > here: https://travis-ci.org/jasonserviss/check/builds/391685256). > > I have noticed two things: > > 1) there are 2 functions in the package, function “a" and function “b”, if > I remove function “b” I no longer receive the warning. Despite this, there > wouldn’t, to my eyes, seem to be anything extremely unusual about function > “b”. > > 2) If I remove RcppArmadillo from the LinkingTo section in the DESCRIPTION > file I, again, no longer receive the warning. I am aware of the fact that, > in the example, there is no need to link to RcppArmadillo although, in the > real use case, there is. > > Id be very appreciative if anyone here could help me get an understanding > for this warning and how it can be resolved! > > Kind Regards, > Jason Serviss > > > _______________________________________________ > Rcpp-devel mailing list > Rcpp-devel@lists.r-forge.r-project.org > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel >
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
