Skip to content
Prev 12613 / 398502 Next

Building R with Microsoft Visual C++

"Neil Osborne" <nc_osborne at hotmail.com> writes:
Well, sixteen years to be precise in my case. However, you need to
know that the grey-haired men (some more than others, none of us wear
white coats though, and some of us can still manage without reading
glasses) *also* gave up on Visual C++ many moons ago. The project file
structure of VC++ is simply not strong enough to build the auxiliary
files needed for R, and we only achieved the cross-platform
portability by using the gnuwin tools. This is simply the traditional
clash between two kinds of user-friendliness: making simple things
easy vs. making difficult things possible (and automatable). (You can
read the book or wait for the movie, but in academia the latter option
may require a very long wait!)
Well, it is... *provided* you use the suggested tools. Once the tools
are installed, you start a shell, go to the relevant directory, type
"make" and sit down and watch the magic. This might have taken you
three and a half days to get to work and three and a half weeks to
begin to understand how it works... 

If you want to use a different set of tools, in particular a
proprietary one, you really can't expect anyone else to jump up and
help you out. It might be doable - versions of R for Windows around
the 0.50 revision (c.1997) were actually made with VC++ (by Robert),
but it usually took him over a month from the Unix releases were made.
However, the functionality of R has been expanded considerably since
then and I have no clue as to where VC++ stands when it comes to
dynamic linking and suchlike. I also think some non-binary items were
actually built on Unix and copied across (but my memory is fading).