On 6 November 2020 at 22:45, Jiefei Wang wrote:
| I'm not sure why publishing the C++ source along with your package is not
| feasible for you. If it is because of something besides technical
| difficulty, you might need to consider an alternative method. Since the R
| package must be portable, yo
Hi Jon,
I'm not sure why publishing the C++ source along with your package is not
feasible for you. If it is because of something besides technical
difficulty, you might need to consider an alternative method. Since the R
package must be portable, your secret functions must also be portable. You
c
On Fri, 6 Nov 2020 at 02:11, Dirk Eddelbuettel wrote:
>
> On 4 November 2020 at 15:24, Jon Davidson wrote:
> | I have an existing Rcpp module that has already been compiled into a .so.
> | How can I integrate this into an R package?
>
> I am afraid you can't as an .so file can only be used on one
Also, it is important that all compiler flags are set consistently among all
compilation units to insure proper linkage, and this policy helps keep those
settings in one place.
On November 5, 2020 6:10:55 PM PST, Dirk Eddelbuettel wrote:
>
>On 4 November 2020 at 15:24, Jon Davidson wrote:
>| I
On 4 November 2020 at 15:24, Jon Davidson wrote:
| I have an existing Rcpp module that has already been compiled into a .so.
| How can I integrate this into an R package?
I am afraid you can't as an .so file can only be used on one architecture,
and likely one subsets thereof (i.e. a Debian objec
Hi,
I have an existing Rcpp module that has already been compiled into a .so.
How can I integrate this into an R package? The existing vignette for
packaging an Rcpp module involves including the C++ source in the package
folder, which will not be feasible for my setup. I can, however, have the
co
