On Sun, Jul 11, 2010 at 4:58 AM, Romain Francois <span dir="ltr"><<a href="mailto:romain@r-enthusiasts.com">romain@r-enthusiasts.com</a>></span> wrote:Le 11/07/10 02:14, Dominick Samperi a écrit :<br><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Romain,<br>
<br>
I made two small changes that should have no impact at all since they only<br>
apply when you build using windows DLL's (not static libs). Obviously these<br>
are not tested by a win-builder submission.<br>
</blockquote>
<br></div>
Why not.</blockquote><div><br>Because testing this would require PATH to be changed at CRAN to include<br>the directory containing Rcpp.dll, and this must be done BEFORE the package<br>build or check process. This would have to be done using a Windows batch<br>
file as part of the initialization. Doing it in configure.win will not work. Also,<br>a real test would require another package (like cxxPack) that links against<br>Rcpp dynamically.<br><br>Without this update to PATH every use of Rscript would have to<br>
explictly load the client package like this:<br><br>Rscript --vanilla -e "{ library(cxxPack); cxxPack:::LdFlags() }"<br><br>For this reason it appears that static libs need to be used for packages<br>submitted to CRAN, unless some way is provided to update CRAN's<br>
windows-level search path.<br><br>Perhaps the LinkTo: mechanism can be modified to take care of this<br>special processing under Windows?<br><br>On your comments about switching to <a href="http://configure.in">configure.in</a>, etc., recall that<br>
there is no configure under Windows (just configure.win).<br><br>Dominick<br> </div></div><br>