1
Vote

setup_vcpp cannot determine the location of the VS Common Tools folder

description

Reported as a follow up to issue 47. This deserves a dedicated issue.

Reported:

Thank you for your response and your reactivty. Unfortunalty , I still receive an error when I try to install from github.

install_github("jmp75/rClr", build_vignettes=TRUE)

I get this error :
'VSCOMNTOOLS' n'est pas reconnu en tant que commande interne
ou externe, un programme ex‚cutable ou un fichier de commandes.
ERROR: setup_vcpp cannot determine the location of the VS Common Tools folder.
I still get the error when I try to build sources (after pulling code source) , or even installing MONO 3.2.3.

Do I miss some basic requirements?

comments

jperraud wrote Dec 19, 2014 at 11:32 PM

Copied from the issue 47:

The package build process tries to find the location of visual studio and related tools using the batch commands in setup_vcpp.cmd. Normally if you have installed VS 2013, whatever edition including Express, you should have an environment variable VS120COMNTOOLS set (yes, with a 12, not 13 like in 2013. This is unfortunate).

It need not be in the usual "C:\Program Files\et_caetera", the VS 2013 install process should have set that up correctly. There is a fallback checking for the environment variable for VS 2012 too, if one happens to still have that version installed.

Bit of a mystery why this environment variable is not detected; I went to some length figuring this out to make sure the VS 2013 setup scripts were found.

I can only advise that you set the presumably missing environment variable VS120COMNTOOLS to something like the following value.

c:\Program Files\Microsoft Visual Studio 12.0\Common7

Blanks in paths are handled. I cannot think of why working on an OS with a French setup would make a difference, but this may be the case.

I hope this helps. Thanks for reporting the full error message; this really helps to zoom in on the root cause.

agstudy wrote Dec 20, 2014 at 11:35 AM

I re-installed VS 2013 (Express Edition) and the build process works like a charm.
Sorry again for this I had to check again in my side before asking here.
Thank again you for your help and for this package.