Skip to content

[R-pkg-devel] trying to understand an error

4 messages · Steven Scott, Uwe Ligges, Kevin Ushey

#
If there's anyone willing to take a look at the build errors I would
appreciate it.  I'm trying to work a bug report from a downstream user, and
I think the OSX build has an issue that I don't understand.
Thanks.

On Thu, May 31, 2018 at 1:49 PM, Steven Scott <steve.the.bayesian at gmail.com>
wrote:

  
  
#
Please ask the Mac maintainer, Simon Urbanek, in such a case where it is 
not obvious what is going on.

Best,
Uwe Ligges
On 05.06.2018 18:45, Steven Scott wrote:
#
Thanks Uwe.   Will do.

On Tue, Jun 5, 2018 at 1:55 PM, Uwe Ligges <ligges at statistik.tu-dortmund.de>
wrote:

  
  
#
For what it's worth, the package compiles successfully on my own macOS
machine but it takes a long time to build just because of how large it is.
Perhaps the CRAN build machine is set to interrupt long-running
installations, under the assumption that they're hanging / frozen?

Given how many C++ source files your package has, it may be prudent to
combine some of them into single C++ translation units, so they can be
built faster (avoid re-parsing the heavy BH and RcppEigen headers so many
times during compilation).

A simple way to accomplish this -- suppose you have files A.cpp, B.cpp,
C.cpp and wanted to compile them together. You could create a file:

    #include <src/A.cpp>
    #include <src/B.cpp>
    #include <src/C.cpp>

and then compile that single file to effectively build those three files
all at once. This does of course require that your source files don't have
any accidental symbol collisions, but I think it would be worth
investigating.

Best,
Kevin

On Tue, Jun 5, 2018 at 2:22 PM, Steven Scott <steve.the.bayesian at gmail.com>
wrote: