Thanks for your quick reply! Indeed, the file you described within RcppGSL\examples\RcppGSLExample\src looks as follows:
## This assumes that the LIB_GSL variable points to working GSL libraries PKG_CPPFLAGS=-I$(LIB_GSL)/include PKG_LIBS=-L$(LIB_GSL)/lib -lgsl -lgslcblas I can now simply replace LIB_GSL by the path where my GSL folder is located? And when I define a new function (outside RcppGSLExample), which Makevars.win file is then queried? (since there is also a makevars.win file in RcppGSL\skeleton; I should update this as well?) Thanks On Wed, Nov 12, 2014 at 3:32 PM, Dirk Eddelbuettel <e...@debian.org> wrote: > > Hi Devin, > > On 12 November 2014 at 15:13, Devin Heer wrote: > | Thus, I would really like to get the RcppGSL package up and running. I > have > | downloaded the GSL library and saved it in the same folder where the > header > | file Rcpp.h is located (I assume this is the default place RcppGSL is > looking > | for header- and source files). > > Nope. See below. > > | For test purposes, I try to compile the following (copied from > r-bloggers): > > [...] > > | > c:/rbuildtools/3.1/gcc-4.6.3/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../ > | i686-w64-mingw32/bin/ld.exe: cannot find -lgsl > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > You need to communicate to your systeh where GSL is. > > Linux and OS X do that by querying the gsl-config script. > > Windows does that by querying the environment variable LIB_GSL, see > src/Makevars.win > and this comment: > > ## This assumes that the LIB_GSL variable points to working GSL > libraries > > The RcppGSL package comes with its test package examples/RcppGSLExample -- > I > would recommend trying to build that first. > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org >
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
