On 16.03.2020 10:58, Duncan Murdoch wrote:
On 16/03/2020 3:00 a.m., Alois Schlögl wrote:
Thanks for your response. For *nix (Linux, MacOSX), this can be
achieved. For windows, currently the only way to compile libbiosig is
through mingw-cross-compiler environment (MXE) [1] or in cygwin.
On 16/03/2020 3:00 a.m., Alois Schlögl wrote:
Thanks for your response. For *nix (Linux, MacOSX), this can be
achieved. For windows, currently the only way to compile libbiosig is
through mingw-cross-compiler environment (MXE) [1] or in cygwin.
Currently, libbiosig does not compile with with
Thanks for your response. For *nix (Linux, MacOSX), this can be
achieved. For windows, currently the only way to compile libbiosig is
through mingw-cross-compiler environment (MXE) [1] or in cygwin.
Currently, libbiosig does not compile with with VC++for various reasons,
and libbiosig has some
I suspect the question in this case depends on the availability of
libbiosig. If CRAN test machines don't have that and its source isn't
included in the R package, then it will fail on initial install. CRAN
doesn't have a lot of resources to install difficult libraries; I have
no idea if
I am just a lurker (not representing CRAN) but I am having a hard time
understanding your question.
Binary packages are a convenience for users, not a method for submitting
packages. When you have an R package accepted it is accepted in source format.
If it doesn't exclude support for Windows
