Hi,
A few extra comments are below.
On 04/14/2017 12:46 AM, Zhian Kamvar wrote:
Hi,
On Apr 13, 2017, at 11:41 , Vineetha Warriyar Kodalore Vijayan
<vineethawarriyar....@ucalgary.ca
<mailto:vineethawarriyar....@ucalgary.ca>> wrote:
Hi Ege,
Thank you!
In the init.c file, do I have to change 'void' to corresponding
declaration?
E.g:
extern void F77_NAME(datacon)(void *, void *, void *, void *, void *,
void *, void *, void *, void *, void *, void *);
I don't think you need to change anything in the generated file. At
least I didn't, and I believe Brian Ripley mentioned that the script
generated fully working init files for hundreds or thousands of packages
with compiled code and only needed manual changes for tens of packages
when they tested it on CRAN.
Also, how do I know the package passes the CRAN incoming feasibility
as it does not show any warnings or notes on my R CMD CHECK --as-cran.
Re submit and see again?
You can use R-Hub as a way to check your package on the development
version: https://github.com/r-hub/rhub#readme If you have your package
on a public remote git repository, you can additionally set up a
continuous integration service like
travis-ci: https://docs.travis-ci.com/user/languages/r/ and use that to
check against devel.
I agree that R-Hub is a great solution, and I have used it several times
myself. You can even just use the website to submit a package:
https://builder.r-hub.io/advanced
But the R interface is nice, so it is recommendable to install the rhub
package.
Alternatively, submitting to http://win-builder.r-project.org/ also lets
you test under R-devel.
Best,
Ege
Best,
Zhian
Regards,
Vineetha Warriyar
________________________________
From: R-package-devel <r-package-devel-boun...@r-project.org
<mailto:r-package-devel-boun...@r-project.org>> on behalf of Ege Rubak
<ru...@math.aau.dk <mailto:ru...@math.aau.dk>>
Sent: Thursday, April 13, 2017 9:35:36 AM
To: r-package-devel@r-project.org <mailto:r-package-devel@r-project.org>
Subject: Re: [R-pkg-devel] Package Submission: issues with
R_registerRoutines', 'R_useDynamicSymbols'
Hi,
This is something that has gotten quite a bit of attention recently due
to the coming R 3.4 giving a NOTE when routines aren't declared. You
should be able to find info on this list or elsewhere.
Basically you need to make a file called e.g. init.c in your src/ with
the appropriate code. This file can be auto-generated for you as
described by Dirk here:
http://dirk.eddelbuettel.com/blog/2017/03/30/#002_even_easier_package_registration
Good luck!
Ege
On 04/13/2017 11:14 PM, Vineetha Warriyar Kodalore Vijayan wrote:
Hi,
When I submitted my R package to CRAN, it didn't go through the
automatic incoming check, resulting the following NOTE. I tested on
my macOS with R CMD CHECK and R CMD --as-cran, both went through with
one NOTE ( Maintainer: NOTE).
* checking compiled code ... NOTE
File 'EpiILM/libs/i386/EpiILM.dll':
Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols'
File 'EpiILM/libs/x64/EpiILM.dll':
Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols'
It is good practice to register native routines and to disable symbol
search.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
I did go through the manual (section 5.4), but didn't understand
much. Can someone help to resolve this issue?
Thanks,
Vineetha
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
