From: Gorjanc G. <Gre...@bf...> - 2008-10-08 16:37:52
|
... >> Then we are not successfull in finding wine binaries in Mac. This is done by R2WinBUGS:::findUnixBinary >> function. It goes like this (returning the result on the first success): >> >> * check if there is x (WINE or WINEPATH) environmental variable >> * check if there is /usr/bin/x >> * try with which x >> * try with locate x >> >> I thought that there is which command in Mac also. Afterall Mac uses unix internally. Can you please check in >> the terminal the result of the following commands: >> >> which wine >> which winepath >> >> locate wine >> locate winepath >> >> Btw. As stated last time, working.directory="." is not really needed unless you do want >> to keep the intermediate files in current working directory. >> > > Actually, working.directory="." is required, otherwise the example doesn't > work. Hence, the reason that it is there... OK > And, which/locate aren't going to work. Those are for the Unix subsystem. > Since Darwine is located in a .bundle, /Applications/Darwine/Wine.bundle, > wine/winepath will not be found. A .bundle is like an .app, but a bit more > general. For example, a .bundle may contain almost anything and it usually > does not contain a Mac app: rather, it is often used to contain > command-line > scripts like wine, man pages, shared libraries, etc. However, I take your > point. It probably makes sense to have links from /usr/local/bin to wine and > winepath. But, the documentation should state that this is necessary. I > don't see that anywhere. Maybe there should be a Mac-specific doc as well > or a wiki or something. Thanks. Is there any other way to find wine binary on Mac direcly from R? I agree that is can be cumbersome to set the whole system even on linux, but it seems it is more complicated on Mac. I think that it would be good if search for wine and winepath binaries would work without hassle. gg |