Jay,
Thank you.
Yeah, but as (
http://www.boost.org/doc/libs/1_54_0/more/getting_started/unix-variants.html#header-only-libraries
) said, Boost.Thread /must/ be built separately.
On 11/02/2013 11:07 PM, Jay Emerson wrote:
> Simon,
>
> If Boost.Thread is only headers, it would be a candidate to
Simon,
Here is what I would do:
1) See
http://cran.r-project.org/bin/windows/contrib/ThirdPartySoftware.html
and learn about BOOSTLIB
2) Build a minimal R package invoking one or two Boost Thread functions.
Use BOOSTLIB in src/Makevars.win
3) Upload the package to win-builder. If
Simon,
This question is somewhat off-topic here. I'll give you an answer but I would
like you to conisder posting any follow-ups on r-devel.
On 2 November 2013 at 21:54, Simon wrote:
| Recently, I made an R package that used the C++ library Boost.Thread
(http://www.boost.org/doc/libs/1_54_0/doc
Simon,
If Boost.Thread is only headers, it would be a candidate to include in
package BH. This would greatly simplify life for you and the users of your
package.
Jay
On Sat, Nov 2, 2013 at 9:54 AM, Simon wrote:
> Hi,
>
> Recently, I made an R package that used the C++ library Boost.Thread (
Hi,
Recently, I made an R package that used the C++ library Boost.Thread
(http://www.boost.org/doc/libs/1_54_0/doc/html/thread.html) for multithreading.
Previously, I have posted a question at stackoverflow
(http://stackoverflow.com/questions/19651954/is-it-possible-to-build-an-r-package-which
Thanks Romain,
I’ll come back to this thread when I found out what the reason of this behavior
in my environment is.
Best
Simon
On 02 Nov 2013, at 10:46, Romain Francois wrote:
> compileAttributes ends up calling a .Call function that lives inside Rcpp.so.
>
> Le 2 nov. 2013 à 10:25, Simon
compileAttributes ends up calling a .Call function that lives inside Rcpp.so.
Le 2 nov. 2013 à 10:25, Simon Zehnder a écrit :
> Thanks Romain,
>
> looks the same here. So the path is the same, but it seems, that the padding
> is different. I would like to understand what happens when I call
Thanks Romain,
looks the same here. So the path is the same, but it seems, that the padding is
different. I would like to understand what happens when I call
compileAttributes. Is there anywhere a linking involved with Rcpp.so or
Rcpp.dylib?
Best
Simon
On 02 Nov 2013, at 09:57, Romain Fra
Le 02/11/2013 09:35, Simon Zehnder a écrit :
First, I didn’t. But for getting some output from the functions in
attributes.cpp I later compiled the Rcpp package from source. When I compile
with the option “-headerpad_max_install_names” the compileAttributes runs
without an error. If I compile
First, I didn’t. But for getting some output from the functions in
attributes.cpp I later compiled the Rcpp package from source. When I compile
with the option “-headerpad_max_install_names” the compileAttributes runs
without an error. If I compile without this flag, I get the pointer error.
Pr
10 matches
Mail list logo
