I am trying to wrap a third-party toolkit that provides a C++ API. The code is
open source and includes a license that allows me to include it directly in an
R package. Right now, I am happy if I can get ANY build (linux, windows, or
Mac) working. The rough build process looks like that given
hi Sean,
On 23 August 2016 at 09:13, Sean Davis wrote:
| I am trying to wrap a third-party toolkit that provides a C++ API. The code
is open source and includes a license that allows me to include it directly in
an R package. Right now, I am happy if I can get ANY build (linux, windows, or
M
Thanks for the reply and feedback, Dirk.
> On Aug 23, 2016, at 10:59 AM, Dirk Eddelbuettel wrote:
>
>
> hi Sean,
>
> On 23 August 2016 at 09:13, Sean Davis wrote:
> | I am trying to wrap a third-party toolkit that provides a C++ API. The
> code is open source and includes a license that allo
Remember there are no rules for a configure script, there is only the
tradition that it is a script you invoke prior to make. "Hand-written"
configure scripts can do anything they want. In this case, I had a 2s look
at the configure script in the ngs project which ultimately are a series of
"konf
On 23 August 2016 at 11:13, Sean Davis wrote:
| Thanks for the reply and feedback, Dirk.
Pleasure!
| > On Aug 23, 2016, at 10:59 AM, Dirk Eddelbuettel wrote:
| > Local shared libraries is hard(est). I would not start there.
I missed one line here: "Hard(est) because you have to communicate wi
