Re: [R-pkg-devel] best approach to getting an external library to *not* use stdout, stderr, etc.

2017-06-28 Thread Simon Barthelmé
Hi Iñaki Thanks for the suggestion. I'm not sure how to make it work, though, if you call freopen on stderr, R CMD check will still detect a call to stderr and trigger a warning. Have you yourself used it? Best Simon On 28/06/2017 17:13, Iñaki Úcar wrote: 2017-06-28 16:29 GMT+02:00

[R-pkg-devel] best approach to getting an external library to *not* use stdout, stderr, etc.

2017-06-28 Thread Simon Barthelmé
Dear list, I'm trying to wrap an external C++ library that has the bad habit of printing errors to std::cerr, a behaviour which will lead to CRAN issuing warnings. I was wondering if people had come up with a solution to this problem that's better than patching everything by hand? Thanks Si

Re: [R-pkg-devel] problem with package_native_routine_registration_skeleton

2017-06-22 Thread Simon Barthelmé
d to >> help... >> best, >> Mark >> Op wo 21 jun. 2017 om 23:46 schreef Simon Barthelmé < >> simon.barthe...@gipsa-lab.fr>: >>> Dear list, >>> >>> Is anybody else having problems with &g

[R-pkg-devel] problem with package_native_routine_registration_skeleton

2017-06-21 Thread Simon Barthelmé
Dear list, Is anybody else having problems with tools::package_native_routine_registration_skeleton? > tools::package_native_routine_registration_skeleton("~/Repos/imager") Error in native_routine_registration_db_from_ff_call_db(calls, dir, character_only) : no native symbols were extract