On Wed, 2014-06-18 at 16:10 +0200, Renaud Gaujoux wrote:
> > Maybe. Read the documentation and sources for yourself (see below).
>
> Not working, at least in my hands, as it requires `sh`.
>
> > Yes, *and documented*
>
> True. I overlooked the beginning of the NB point.
>
> > (including that i
> Maybe. Read the documentation and sources for yourself (see below).
Not working, at least in my hands, as it requires `sh`.
> Yes, *and documented*
True. I overlooked the beginning of the NB point.
> (including that it should not be used for Windows executables).
Yes, that's why I use the s
On 18/06/2014 09:11, Renaud Gaujoux wrote:
Thank you for the replies and hints.
A 'pre-built windows binary' of what?
Sorry this was not clear, src/ contains source code for a binary
executable, which produces no .lib or .dll.
It is all fine in a R development environment:
* On Linux, the
Thank you for the replies and hints.
> A 'pre-built windows binary' of what?
Sorry this was not clear, src/ contains source code for a binary
executable, which produces no .lib or .dll.
It is all fine in a R development environment:
* On Linux, the executable is compiled and copied to
R_PACKAGE
On 17/06/2014 21:38, Skye Bender-deMoll wrote:
Please forgive another comment on this topic.
But it is not on the topic ... this function is run on a single directory.
The 'type' argument to tools::write_PACKAGES doesn't currently accept
the 'mac.binary.mavericks' value. It seems like it sho
