[Rcpp-devel] Visual Studio compatible Rcpp

[romain at r-enthusiasts.com]

Le 14 sept. 2010 à 16:26, pooja varshneya <pooja.varshneya at gmail.com> a écrit :

> Thanks for the reply Romaine !!

How did i get an extra "e" in my name ? :-)

> The FAQ entry says that R and Visual
> Studio don't get along.
> However, i managed to generate a Visual Studio compatible import
> library  for R from the instructions given in R source folder
> README.packages file.
> 
> Can you please elaborate on the problems you encountered in Visual
> Studio compilation ? Has anyone tried it before ?

I have not. And i dont plan to. 

I suppose C is easier to deal with than C++. if i cared about that, i would first try to use a simpler C++ library (one or two vanilla c++ classes). Rcpp uses many features of C++ that perhaps confuse the compiler you want to use. 


> I am using Rcpp_0.8.0 because Rcpp_0.8.0 and RInside_0.2.0 are the
> only compatible versions running without segmentation fault on
> windows. When i upgrade to a later version, RInside examples crash
> with segmentation faults.

Ah ok. Nobody offered their help here

> I greatly appreciate your help in this regard.

I'm afraid i dont have any help to offer in that department. Other people might. Maybe you'll find clues by browsing this list archives.

Romain

> Thanks,
> Pooja
> 
> On Tue, Sep 14, 2010 at 2:19 AM, Romain Francois
> <romain at r-enthusiasts.com> wrote:
>> Le 13/09/10 23:26, pooja varshneya a écrit :
>>> 
>>> Hi Folks,
>>> 
>>> I need to use Rcpp and RInside packages for a project that is compiled
>>> using Visual Studio. I have managed to generate Visual Studio
>>> compatible import library for R.
>>> But now i am unable to install Rcpp package using 'R CMD INSTALL
>>> Rcpp_0.8.0.tar.gz'. I receive undefined reference errors as given
>>> below. Does anyone know the steps for compiling Rcpp and RInside using
>>> Visual Studio ?
>>> 
>>> 
>>> -------------------------------------------------------------------------------------------------------------
>>> debugging.o:debugging.cpp:(.text+0x1bc): undefined reference to
>>> `Rf_mkChar'
>>> debugging.o:debugging.cpp:(.text+0x1d0): undefined reference to
>>> `SET_STRING_ELT'
>>> exceptions.o:exceptions.cpp:(.text+0x286): undefined reference to
>>> `Rf_mkString'
>>> exceptions.o:exceptions.cpp:(.text+0x295): undefined reference to
>>> `Rf_install'
>>> exceptions.o:exceptions.cpp:(.text+0x2a8): undefined reference to
>>> `Rf_lang3'
>>> r_cast.o:r_cast.cpp:(.text+0x23): undefined reference to `TYPEOF'
>>> r_cast.o:r_cast.cpp:(.text+0x3d): undefined reference to `Rf_coerceVector'
>>> r_cast.o:r_cast.cpp:(.text+0x13f): undefined reference to `TYPEOF'
>>> r_cast.o:r_cast.cpp:(.text+0x1cc): undefined reference to
>>> `Rf_coerceVector'
>>> r_cast.o:r_cast.cpp:(.text+0x25b): undefined reference to `TYPEOF'
>>> .......
>>> 
>>> -------------------------------------------------------------------------------------------------------------
>>> 
>>> 
>>> Thanks,
>>> Pooja
>> 
>> See item 2.7 of the Rcpp-FAQ vignette:
>> http://cran.r-project.org/web/packages/Rcpp/vignettes/Rcpp-FAQ.pdf
>> 
>> Also, we released Rcpp 6 times since version 0.8.0, why would you use an
>> obsolete version ?
>> 
>> Romain
>> 
>> 
>> --
>> Romain Francois
>> Professional R Enthusiast
>> +33(0) 6 28 91 30 30
>> http://romainfrancois.blog.free.fr
>> |- http://bit.ly/cCmbgg : Rcpp 0.8.6
>> |- http://bit.ly/bzoWrs : Rcpp svn revision 2000
>> `- http://bit.ly/b8VNE2 : Rcpp at LondonR, oct 5th
>> 
>> 
>>