On 18 July 2012 at 18:21, Vaclav Petras wrote: | I used it just as an minimal working example. I'm sorry for confusion. | | I need it for _truly new libraries_ and same would apply also for my | own library if i have some. | | As I see I didn't include to my previous email explicit sentence | stating that I need really custom include path. So here it is.
As I said, you probably want autoconf / configure to automate the search for headers and resulting configuration. What is your use case? Are you sure you don't want to build a package? In that case you'd modify src/Makevars and would not need the plugin which is just used for smaller-scale use via inline. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com _______________________________________________ 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
