Automatic registration of attributes when non RCpp C/Cpp code is present

[vspinu]

Within the same package I have plain C and Rcpp code. With the new changes (probably #694) compileAttributes generates registration code that takes into account only entries in Rcpp code.

My question is what is correct/recommended way to go about it? Can compileAttributes run tools::package_native_routine_registration_skeleton (or whatever else it does) on all c/cpp files within a package?

[vspinu]

Actually the problem is specific to R < 3.4.0. On 3.4.0 it seems to be doing the right thing.

[jjallaire]

Yes, compileAttributes does run tools::package_native_routine_registration_skeleton when running under R 3.4, so you should indeed try to develop under R 3.4 (or if that's not practical just write your own init function and then compileAttributes won't try to generate any registration code).

…

On Fri, May 26, 2017 at 12:52 PM, Vitalie Spinu ***@***.***> wrote: Actually the problem is specific to R < 3.4.0. On 3.4.0 it seems to be doing the right thing. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#700 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXxy1lnAKTz621e-HsYAlt7OuK0IoAks5r9wNogaJpZM4Nn0MH> .

[vspinu]

Yeh. I switched to 3.4.0. Thanks.

[eddelbuettel]

And for completeness, before R 3.4.0 it worked just fine to call compiledAttributes() by hand (or a script, my case) followed by a call for package registration (easy to script, I blogged about that three times).