Dear Prof. Ripley
Prof Brian Ripley wrote:
> You have $(ROOTSYS), not ${ROOTSYS} as I had.
Thank you very much, changing the braces did the trick, now everything
works!
>
> Also, the output you show is missing the quotes, which is unlikely if
> this was the Makefile.win version used.
This is cor
You have $(ROOTSYS), not ${ROOTSYS} as I had.
Also, the output you show is missing the quotes, which is unlikely if this
was the Makefile.win version used.
To summarize:
1) Use ${ROOTSYS} (with braces).
2) Either use forward slashes and no spaces or ensure the path is quoted
in the cl call.
T
Dear Prof. Ripley
Here is the Makefile.win, which contains already your suggestion for
spaces (thank you), but contains only 3 of 14 header files:
#--
ROOTSYS = C:\\root
#ROOTSYS = ${ROOTSYS}
LDOPT
Dear R developers,
these days I'm working on some R code for fitting completely generic
Bayesian Hierarchical Models in R, a la OpenBUGS and JAGS.
A key feature of OpenBUGS and JAGS is that they automatically build an
appropriate MCMC sampler from a generic model, specified as a directed
acyclic g
> cl /Ic:\root/include /MT /EHsc /Ox /D "MSVC" /D "WIN32" /c TMLMath.cxx
will AFAIK not work when passed to the shell used (which is ash), and in
any case will not work for paths with spaces in.
You still haven't shown us the Makefile.win, but probably you need
cl /I"${ROOTSYS}/include" /MT /EH
Dear Prof. Ripley
Thank you for your fast reply and sorry for being not specific enough.
My problem is that I need to use MS VC++ for the WinXP port of my
package (xps at BioC):
Here is my concrete problem and what I did:
- installed MS Visual Studio Express 2008
- installed binary of ROOT fram
On Fri, Mar 21, 2008 at 11:36 AM, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 21/03/2008 2:09 AM, Peter Danenberg wrote:
> >> No, we want a solution in R.
> >
> > Would it suffice, by the way, to source() a file and introspect upon
> > its objects with ls(), formals(), typeof(), mode(), and
On Fri, 21 Mar 2008, cstrato wrote:
>
> Dear all,
>
> When porting my package to WinXP I have the following problem:
> I need to create an environment variable "MYVAR=c:\mypath" which I have
> saved in the control panel "System->My Computer" (under the `Advanced' tab).
>
> I have two files which n
Dear all,
When porting my package to WinXP I have the following problem:
I need to create an environment variable "MYVAR=c:\mypath" which I have
saved in the control panel "System->My Computer" (under the `Advanced' tab).
I have two files which need to access MYVAR: config.win, Makefile.win
Wh
> parse() currently does nothing with comments, but it does tell you
> where each parsed expression came from . . .
That's exactly what I was looking for, Duncan; thanks. In fact, I used
parse() recently to write a telnet frontend to R.
__
R-devel@r-pro
On 21/03/2008 2:09 AM, Peter Danenberg wrote:
>> No, we want a solution in R.
>
> Would it suffice, by the way, to source() a file and introspect upon
> its objects with ls(), formals(), typeof(), mode(), and the like; or
> should we formalize, say, a BNF and write the accompanying automaton?
I d
11 matches
Mail list logo
