error: command 'C:\\ Visual Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.14.26428\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2 - c++

Hi so I was trying to pip install python-ldap using my git bash but at first it told me that i don't have cl.exe so i downloaded the visual studio C++ pack now it's showing this error
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.14.26428\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2
I never coded with C++ so I'm not sure what the error is. I downloaded the CLI tools for C++ too and I don't think it's because the cl.exe isn't in the path since it found it. Any insights ??

Install Visual C++ 2015 Build Tools from https://go.microsoft.com/fwlink/?LinkId=691126 with default selection.

I know this question was asked years ago, but for future users, I thought of providing an answer for this question. Today I've faced the same problem with the "Microsoft visual studio 2019 build tool."
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.29.30037\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2
I have come across this issue while trying to install the dependency through anaconda3 cmd in windows OS.
pip install sparse_dot_topn
I have tried different methods suggest in different portals and couldn't resolve this for hours. At the same time, I've ended up installing unnecessary components of the visual studio build tool as well. Finally, I found the problem is associated with the setup tool library, and the problem can be solved through force upgrade to the setup tool package
python -m pip install -U pip setuptools

There doesn't seem to be a valid solution for this error but one workaround is to install the windows binary package from https://www.lfd.uci.edu/~gohlke/pythonlibs/#python-ldap

In my case, I had to copy or link (using link shell extension) the x64 version of "C Connector" to the x86 folder.
If you can't find the x64 C connector...
Download mysql-installer-web-community-8.0.12.0.msi from their website:
https://dev.mysql.com/downloads/installer/
Run the Installer, and click the Add button on the right, then locate the Connector C 6.1 x64
The C++ Connector has C compatible header files, but hard-linking to it does not work, as explained here: https://dev.mysql.com/downloads/connector/c/
You cannot install the x86 version alongside the x64 version. The installer does not permit this.
Otherwise, Hard-Link the x64 version
Install link shell extension.
Navigate to "C:\Program Files\MySQL\" then right click on "MySQL Connector C 6.1" and click Pick Link Source
Navigate to "C:\Program Files (x86)\MySQL\" and Drop Link As... > Junction
A Junction is a duplicate reference in the file system to a folder. Creating a second junction reclassifies the original folder a junction as well, but they are both authentic references to the same folder, and so, unlike symbolic links, they will work with scripts, because they are real, and are implemented on the file system level.
Then, if the connector you have installed is a different version number and you want to try to force it to work with a non-compatible script, rename it to match the folder mentioned in the error message. For example...
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.15.26726
\bin\HostX86\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -Dversion_info=(1,3,13,'final',0) -D__version__=1.3.13 "-I C:\Program Files (x86)\MySQL\MySQL Connector C 6.1 \include" "-Ic:\program files\python37\include" "-Ic:\program files\python37\include" "-IC:\Program Files (x86)\Microsoft Visu...
Crappy pip code failing to pass variables from the system environment :(

I had a similar issue.
I had installed a 32-bit python interpreter from https://www.python.org/downloads/windows/ mistakenly in my 64-bit windows machine.
Then I downloaded the correct 64-bit interpreter setup and installed it. Then I pointed the Pycharm interpreter path to it.
Then my issue was solved. I hope this will help you...

When I was perusing the internet to find the solution I ran into an adjacent problem:
Python was not found, which I solved by (assuming your python works and is added to PATH) going to Settings > Manage App Execution Aliases and turning off "python". They try installing your package again

Install the C++ build tools from here: https://my.visualstudio.com/Downloads
Search for 'build tools' and download the latest VS build tools installer. Install the C++ build tools (currently it's called "Desktop Development with C++") with the defaults.

What worked for me in the same situation: Except installing VS Build Tools, install whole Visual Studio. Python libs often require C/C++ compiler

I had the same error; although when installing lux-api
What worked for me was downgrading the default python version 3.10 -> 3.9
(ref)
p.s. the error that I had was the following
error: command ...\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX86\\x64\\cl.exe failed with exit code 2
----------------------------------------
ERROR: Failed building wheel for pandas
Failed to build pandas
ERROR: Could not build wheels for pandas, which is required to install pyproject.toml-based projects

I had the similar issue. I was trying to build pandas from source. I figured out that my build tools were not compatible with the source. I had MSVC v142 installed. So I installed the below components and this worked for me:
Windows 10 SDK (10.0.17763.0)
MSVC v141 - VS 2017 C++x64/x86 build tools
These tools can also be installed from cmd, just install visual studio 2019 build tools exe and then run this command in cmd as admin:
vs_buildtools.exe --quiet --wait --norestart --nocache ^
--installPath C:\BuildTools ^
--add "Microsoft.VisualStudio.Workload.VCTools;includeRecommended" ^
--add Microsoft.VisualStudio.Component.VC.v141 ^
--add Microsoft.VisualStudio.Component.VC.v141.x86.x64 ^
--add Microsoft.VisualStudio.Component.Windows10SDK.17763
I also had to install additional tools to make it work correctly:
C++/CLI Support for v141 build tools (14.16)
Once the tools were installed correctly then I had to initialize x64 environment with new installed build tools:
"C:\BuildTools\VC\Auxiliary\Build\vcvars64.bat" -vcvars_ver=14.16 10.0.17763.0
After that I restarted my computer and build pandas again and it was build successfully.

Related

command cl.exe failed upon pip install django_compressor

im posting this because im encountering this problem and had been trying to solve this issue for days but failed to. I faced the following error (refer to attached) when i try to install django_compressor (pip install django_compressor) i searched online for solutions but is unable to rectify the problem.figure 1
Im currently have python 3.6 with visual studio 14.0 and visual C++ build tools installed. I had referred to stackoverflow.com/questions/32740319/error-command-cl-exe-failed-no-such-file-or-directory-python-3-4 to attempt to try the command "C:\Windows\System32\cmd.exe /E:ON /V:ON /T:0E /K "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /RELEASE /x64" from one of the answer posted but i still face problem with x64 compilers not installed.
And i tried to solve the x64 compilers issue by installing the Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1 referencing from help.appveyor.com/discussions/problems/1266-no-64bit-compiler-in-the-71-windows-sdk
And also uninstalling visual studio service pack 1 to rectify the x64 compilers issue referencing from Visual Studio 2010 Service Pack 1 and Windows SDK for Windows 7 and .NET Framework 4 Issue in the microsoft visual studio https://msdn.microsoft.com/en-us/vstudio/gg697159 but still to no availability.
Right now i do not know how to proceed on solving the problem of installing django_compressor (cl.exe) as well as the x64 compilers when i try to retify the cl.exe problem. Would require your assistance in this, thank you so much!
###############################################################################
NOTE EDITED: Hi all, i would like to say i manage to find a possible solution, because the program regards to cl.exe with is i presume it got to do with x64 compilers and knowing this issue occur when trying to install rjsmin and rcssmin. I decided to download both the package, extract it and install it using "python setup.py install --without-c-extensions" and it works so i presume it got to do with c extensions and i manage to install django_compressor. But i would like to check will this cause any possible problems in the future? Thank you so much once again!

NPM Install on Windows 7 issue, no Microsoft.CPP folder

I'm having troubles with npm install on Windows 7.
I'm using Visual Studio 2013 Express and I've also installed Microsoft Build Tools 2013.
I have the Path variable set and I've tried with the --msvs_version parameter in the npm install
It gives me the
error MSB4019: "C:\Program Files (x86)\MSBuild\12.0\Microsoft.Cpp.Default.props" not found
That folder doesn't exist on my computer, I only have
MSBuild\12.0
and
MSBuild\Microsoft
What do I miss to install?? I would be able to compile Node project without having to install the full version of VS, if possible, and honestly, I would be able to do it by installing the minimum required software.
Thank you!

Build Qt 5.2.1 with Visual Studio 2010 for Win 7 64Bit

I'd like to build Qt 5.2.1 for Visual Studio on my Windows 7 64Bit machine. I know, there are various similar questions, but none which I have found really give me the feeling that I definately know how to proceed.
First, I tried to follow the instructions in How to build Qt for Visual Studio 2010, but I noticed that things for Qt 5 have changed a bit. E.g., there is no Qt/bin directory that you could add to the path variable, since now there are many different bin directories.
I then found http://qt-project.org/doc/qt-5/windows-building.html but here I am not sure if they use Visual Studio 10 and I do not understand the instructions to get the environment variables right.
This link http://qt-project.org/wiki/Building-Qt-5-from-Git is also interesting, as it gives various hints, but it uses git and I would like to build from the opensource zip file.
So, what are the steps I need to take precisely? I will write my version here, and you can extend/correct it.
Install Perl and Python and add them to system path
Download http://download.qt-project.org/official_releases/qt/5.2/5.2.1/single/qt-everywhere-opensource-src-5.2.1.zip
Unzip the file from 1. to C:\Qt5.2.1
Install the standalone Windows SDK (http://msdn.microsoft.com/en-US/windows/apps/br229516)
Set up the Qt Environment variables. How?!! Please clarify Step 3 of http://qt-project.org/doc/qt-5/windows-building.html
Open the Visual Studio Command Prompt 2010. Run there
configure -MP -opensource -confirm-license -debug-and-release -no-webkit
Type "nmake" in the Visual Studio Command Prompt 2010.
http://qt-project.org/doc/qt-5/windows-building.html mentions "If an installation prefix was given, type jom install, nmake install or mingw32-make install" - what is an installation prefix??
Then, I believe Qt should be installed in C:\Qt5.2.1; How can I check if the installation was successfull? Is it possible, to have Qt in my list of installed applications using this approach?
I'd be happy if you could correct/comment my approach, since some steps are not entirely clear to me and I have mixed different tutorials.
Thanks!

Node packages not building on Windows 8.1 - Missing Microsoft.Cpp.Default.props

NPM packages are not building on Windows 8.1 - failing with following error,
error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
I have tried the following,
Setting an evironment variable VCTargetsPath to C:\Program Files (x86)\MSBuild\12.0\ (The error changes accordingly but there is no Microsoft.Cpp.Default.props with the 2012 build tools).
Installing a VisualStudio 2010 environment (uninstalled then installed in the correct order) according to this answer
Completely removed VisualStudio 2010 and tried a VisualStudio 2012 instead, which should work according to the Node-gyp wiki
Added registry keys according to this answer
Tried using the Windows 7.1 SDK command prompt according to this answer
Tried setting VisualStudioVersion before running npm according to this answer
Tried passing --msvs_version=2012 to npm according to this answer
None of the above have worked.
I've spent ages on this already. Does anyone have a definite answer that works?
The quick fix for me was this:
set VCTargetsPath=C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120
npm install
Finally Microsoft is providing much better solution to VS.
I just wanted to update this question with the latest answer. You now do not need to install Visual Studio.
Source: https://github.com/nodejs/node-gyp/issues/629#issuecomment-153196245
Instructions below in case the source goes down.
Install VC++ Build Tools Technical Preview using the Default Install option.
[Windows 7 only] requires .NET Framework 4.5.1
Install Python 2.7, and add it to your PATH: npm config set python python2.7
Launch cmd and run:
npm config set msvs_version 2015 --global (this is instead of lnpm install [package name] --msvs_version=2015l every time.)
So it is 2.47am - figured it out.
Although the node-gyp site seems to suggest using Visual Studio 2010 or 2012, instead for Windows 8.1, install Visual Studio Express 2013 for Windows Desktop as discussed in this issue.
Setting the following fixed the problem for me
/property:VCTargetsPath="C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120
As mentioned on this forum
A quick note for people who installed:
Visual Studio 2012 (Express)
MSBuild 2012
with the issue of:
MSBuild loads Microsoft.Cpp.Default.props
MSBuild cannot load Microsoft.Cpp.props
The solution is here:
set parameter of MSBuild:
/property:VCTargetsPath="C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110"
This is the same issue as described here
NPM native builds with only Visual Studio 2013 installed
If you have a version of VS2013 installed set this environment variable before running the npm command:
set GYP_MSVS_VERSION=2013
or for VS2012
set GYP_MSVS_VERSION=2012
background reading: https://github.com/Automattic/socket.io/issues/1151
Just in case people encounter this issue again, the issue got resolved in my case when I did a
npm install -g --production windows-build-tools
Link for reference
Related question

How to compile code with visual studio using makefile

I have just downloaded a open source project which is said to be compiled using visual studio c++. It contains 3 makeFiles (makeFile, makeFile(1) and makeFile(2) )
I always open programs in VS using the .sln files and now I dont know what to do with this makeFile.
can anyone instruct me how to deal with it please.
regards
You may try NMake. See NMake Reference and Stackoverflow post.
NMake is included with Visual Studio. You may try with NMake shipped with the edition of Visual Studio you may want to use.
If you are only familiar with Visual Studio projects and solutions, dealing with makefiles can be a challenge. The following link will give you a good introduction to makefiles from a Visual studio perspective.
An introduction to Makefiles for Visual Studio developers
Translating Linux makefiles to Visual Studio solution will be a manual effort.
NMake looks promising. However, the following link takes a simple Makefile and explains some fundamental issues that one may encounter.
Makefiles in Windows
VS2017 and cross-platform dev with make linux binaries
If you're working on windows 10, you can make make work and compile linux binaries:
have lxss installed, and gdb server, ssh server installed:
sudo apt update &&
sudo apt install -y build-essential gdbserver openssh-server
make sure you can connect through ssh to your local machine:
sudo vi /etc/ssh/sshd_config &&
sudo service ssh start
make sure you have linux development with c++ packages installed (VS2017 install)
make sure you configured your connexion to lsxx through ssh in VS/tools/options/connection manager ("connection" in search).
make sure to have a linux project (new project/other languages/vc++/crossplatform/linux)
yet, add you make commands in project/properties.
I've just run into the same problem and for me the solution:
open "VS2012 Native Command Prompt" the name varies over different versions of MSVS. then simply type 'nmake makefile.vc'. nmake is the command, makefile.vc is your own makefile in your local folder. and it is done (if no further errors occur)