[Rcpp-devel] Some suggestions

Dominick Samperi djsamperi at gmail.com
Sun Jul 11 17:51:03 CEST 2010


On Sun, Jul 11, 2010 at 4:58 AM, Romain Francois
<romain at r-enthusiasts.com>wrote:Le 11/07/10 02:14, Dominick Samperi a
écrit :

 Romain,
>>
>> I made two small changes that should have no impact at all since they only
>> apply when you build using windows DLL's (not static libs). Obviously
>> these
>> are not tested by a win-builder submission.
>>
>
> Why not.


Because testing this would require PATH to be changed at CRAN to include
the directory containing Rcpp.dll, and this must be done BEFORE the package
build or check process. This would have to be done using a Windows batch
file as part of the initialization. Doing it in configure.win will not work.
Also,
a real test would require another package (like cxxPack) that links against
Rcpp dynamically.

Without this update to PATH every use of Rscript would have to
explictly load the client package like this:

Rscript --vanilla -e "{ library(cxxPack); cxxPack:::LdFlags() }"

For this reason it appears that static libs need to be used for packages
submitted to CRAN, unless some way is provided to update CRAN's
windows-level search path.

Perhaps the LinkTo: mechanism can be modified to take care of this
special processing under Windows?

On your comments about switching to configure.in, etc., recall that
there is no configure under Windows (just configure.win).

Dominick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20100711/55b92496/attachment.htm>


More information about the Rcpp-devel mailing list