command cl.exe failed upon pip install django_compressor - django

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!

Related

Installing B&R Automation Studio V 4.9.2 C++ redistributable setup not found

When installing B&R Automation Studio V4.9 (when V4.7 is already installed) I get a
C++ redistributable setup not found
error.
In the picture below you see the redistributables of C++ that are already installed.
Does anybody know how to fix this problem?
Fixed this issue by reinstalling B&R Automation Studio V4.9.
I thinks something went wrong with the extraction of the zip file.

Cannot install C++ templates for Visual Studio 2017, error "Couldn't install Microsoft.Net.4.TargetingPack"?

Tried restarting and reinstalling, neither help. To clarify whether I'm modifying the Visual Studio installation, installing it from scratch or trying to install the separate C++ build with another installer, I get this same error. Any help would be appreciated.

How to ensure Visual studio updates the registry when installing compiler

I'm having a frustrating time trying to get the visual studio compiler up and running. I'm trying to install the visual studio compiler to use with matlab.
After installing build tools from here, for some reason, the registry is not updated and matlab is not able to find the compiler. I tried uninstalling and reinstalling after cleaning the registry using ccleaner but that doesn't seem to be working. Any suggestions on what I might be doing wrong? Any help will be much appreciated.
Turns out the new version of visual studio 2017 doesn't actually update the registry or something like that (see here: https://developercommunity.visualstudio.com/content/problem/2813/cant-find-registry-entries-for-visual-studio-2017.html) .
I ended up installing the older version of visual studio community (VS 2015 with updates) and matlab was able to find it.

How can I get MatLab to find the Visual C++ Compiler?

Preamble: I found a solution in the midst of writing this, and this problem was a PITA and had a convoluted solution. Thus, I feel compelled leave this here to help any poor soul who has this problem.
I'm new to MatLab, and I don't usually use Visual C++ either, so forgive me if this should be painfully obvious.
Short version: I have Visual C++ 2013 installed on my computer, but mex can't find it when I run mex -setup c++. I get the following:
>>mex -setup cxx
Error using mex
No supported compiler or SDK was found. You can install the freely available
MinGW-w64 C/C++ compiler; see Install MinGW-w64 Compiler. For more options, see
http://www.mathworks.com/support/compilers/R2015b/win64.html.
Here's the full situation.
OS: Windows 10 Home
Compiler: Visual Studio 2013 (v120, up-to-date)
I confirmed that I can compile and run a program using this toolset.
MatLab version: 2015b
I was originally running Visual Studio 2015, and mex found the compiler just fine. However, I soon found out that Simulink is not compatible with VS 2015, so I had to roll back to VS 2013, and this is when my problem started.
I've tried, among many others, the following sites to find a solution:
The MatLab mex documentation - No help, only shows basic mex usage.
The MatLab supported compiler list - Confirmed that VC++ 2013 is compatable.
Then I went down a rabbit hole.
A very protracted mathworks.com answer that suggested other links. This led me to...
Another mathworks.com answer which sounds like my problem, and suggests patching my setup. Turns out that I don't have SDK 7.1 installed. So, I went to install, and got this error:
Some components could not be installed. Some Windows SDK components require the RTM .NET Framework 4...
This Stack Overflow question asks about this issue, and I hit the exact same issue Danilo Gadêlha had in regards to the .NET Framework already being installed.
I tried the top answer, and after removing every single reference to .NET framework of any version I could find, including those under "Windows Features", I still couldn't install.
I tried the next option, and even in safe mode, RegEdit wouldn't let me change the values suggested by the next answer, so that was a bust.
Lastly, I tried MandM's solution, which finally solved my chain of problems.
I think this was the root of my problem: when I uninstalled Visual Studio 2015 and installed Visual Studio 2013, an installation or registry setting was left in an incorrect state, and mex was unable to find Visual Studio 2013 as a result.
The solution that worked for me:
Leave Visual Studio 2013 installed.
As MandM answered:
Uninstall the following:
"Microsoft Visual C++ 2010 x64 Redistributable"
"Microsoft Visual C++ 2010 x86 Redistributable"
Before installing the Windows 7.1 SDK, and the install package reinstalls those two during installation.
As Robert Važan points out in the comments:
If error message persists despite this workaround, just click OK and proceed with installation. The installation will succeed this time..
I did get this error, but the install worked fine.
Install the SDK 7.1 Patch, which fixes the issue highlighted on this mathworks.com answer.

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