Thanks Prof. Ripley.
I did see your post about installing XCode 4.6 & 5 but incorrectly assumed that
it would be better to compile and build packages with the latest version of
XCode 5 (September 2013) rather than install the old compilers. Hence the
interest in auto-detecting and specifying t
Rob,
It is true I have been momentarily confused and Prof. Ripley clarified this
(the reason for th confusion is that if you upgrade from Xcode 4 to Xcode
5, llvm-c++-4.2 does not get removed). Follow his directions in the post,
and your user will be fine.
But taking a step back, as a package au
This is documented in the current manuals: please read them. I posted
how to get the compilers used for the CRAN binary, on this list when
Xcode 5 was released (it is for Mountain Lion only):
https://stat.ethz.ch/pipermail/r-sig-mac/2013-September/010327.html
Otherwise see e.g.
http://cran.r
Hi Kasper,
Thank you very much for your reply.
Just to clarify, the situation I'm describing is one in which a user has
downloaded XCode 5 and installed the command line tools so that they can, in
theory, compile and install packages from source. However, the compiler
supplied by XCode5 (App
Rob,
What you should do, is _always_ inherit the compiler which was used to
build R. That is the 'Right' way to go and it is what will happen per
default if you are using Makevars to compile you package. If you need to
use configure, there are hints in R-exts and we can help more specifically,
p
Hi all,
I'm developing a package that needs to be compiled on installation but am
unsure how to ensure that the proper C++ compiler is invoked when installing
this package from source. Is there anyway to, at build time, auto-detect and
set the available compiler using configure / Makevars?
M
