On Thu, 7 Dec 2023 19:29:46 +0100
Serge wrote:
> g++ -std=gnu++11 -I"D:/RCompile/recent/R-4.3.2/include" -DNDEBUG
> -I../inst/projects/ -I../inst/include/ -DIS_RTKPP_LIB -DSTKUSELAPACK
> -I'D:/RCompile/CRANpkg/lib/4.3/Rcpp/include'
> -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include" -fopenm
On 12/14/23 19:39, McGrath, Justin M wrote:
At this point, the policy appears to have nothing to do with tar, contrary to
the error message. Thus, replacing tar with zip wouldn't address CRAN's
concern. The policy given in this thread (and seemingly unstated anywhere
public) is that CRAN wants
At this point, the policy appears to have nothing to do with tar, contrary to
the error message. Thus, replacing tar with zip wouldn't address CRAN's
concern. The policy given in this thread (and seemingly unstated anywhere
public) is that CRAN wants to allow someone on Windows to unpack an R pa
Compiled code is another source of long names. Some libraries are produced
by companies with style restrictions that demand LongDescriptiveNames for
functions and classes, and which expect file names to match the name of the
class contained within. If you've got
Models/SpecificModelFamily/Posteri
On Wed, 13 Dec 2023, McGrath, Justin M wrote:
On Windows, packages will be in "C:\Users\[User Name]\Documents\R\win-library\[R
version]\[Package Name]".
With a 150 byte limit, that leaves 70 bytes for the user name, R version
and package name. That seems more than sufficient. If people are
It looks like the problem was coming from this line in the Makevars
## $(SHLIB) is the usual default target that is built automatically from all
source
## files in this directory. pkglib is an additional target for the library
## that will be installed in inst/ and which users can link against.
.
