Re: packaging stan
On 3 August 2013 at 14:58, Ross Boylan wrote:
| Is stan building a shared or static library?
|
| Yes. Not sure which.
Almost surely shared because ...
| If not, that may be the
| missing link between the two. Requiring the stan source be present when
| building rstan (as a seperate source package) will not work or only work
| with lots of trouble I do not think is worth it. So if there is no
| library being built or other support, combining both into one source
| package might be an option.
|
| One indication this is alright would be that both stan and rstan are
| released in lockstep.
|
| My understanding, which may be wrong, is that the stan system includes a
| "compiler" (stanc) that converts a stan program to C++ and then builds an
| executable from it. The executable, and maybe stanc, need the stan library to
| run.
|
| I think the rstan R package invokes stanc behind the scenes and builds a
| library dynamically loadable in R. Or possibly it just runs the compiled stan
| code.
... because of the dynamically-linked modules. The Stan folks use my Rcpp
package in the mix, and wrote an alternative implementation of inline to
store/cache compiled modules for their use.
That said, I know next to nothing about (R)Stan internals and builds. I am
not an (R)Stan user myself.
Dirk
--
Dirk Eddelbuettel | edd@debian.org | http://dirk.eddelbuettel.com
Reply to: