Skip to content
Prev 17444 / 21312 Next

[Bioc-devel] Compiling a cpp source code while installing package

At the link 

  https://ctg.cncr.nl/software/magma

it says " The MAGMA source code can also be downloaded below, which can be used to compile the program on the target system if this is not supported by the provided binaries (note that standard copyright applies; the MAGMA binaries and source code may not be distributed or modified)."

So it sounds like you are not able to do what you want anyway?

Generally, I do not think bundling large software projects that are not specifically designed as libraries is a good strategy for R / Bioconductor. And while you might ask us to install the software on our build systems so that your package can use the program, I'd offer up the cost of doing that, both for us and for your potential users --  perhaps a better strategy is simply to offer your package to the MAGMA maintainers as an improvement to the R scripts they already provide and distribute from the link above?

Martin

?On 11/8/20, 7:40 AM, "Bioc-devel on behalf of Alexandru Voda" <bioc-devel-bounces at r-project.org on behalf of alexandru.voda at seh.ox.ac.uk> wrote:

    Thanks for the reply, Martin!

    Unfortunately, the C++ software is large (https://ctg.cncr.nl/software/magma), not just some feature that can be used from R base, CRAN or Bioconductor.

    Also, I wouldn't make a separate library for the C++ software because the *main* purpose of my package is to wrap them up for R. Other functions are just a secondary aim of the package.

    Thank you for the recommended packages! I was wondering if there's any standard guidance/vignette for how Rhtslib & Rhdf5lib approached this? There are numerous Rcpp vignettes that I could find, but couldn't find for pure C compiled by R?
Message-ID: <DM6PR04MB6624432A544B3867D64E1C16F9EB0@DM6PR04MB6624.namprd04.prod.outlook.com>
In-Reply-To: <CWLP265MB0596C17BF8E19227F7D128BAEFEB0@CWLP265MB0596.GBRP265.PROD.OUTLOOK.COM>