I downloaded Detour Express 3.0 via MS (http://research.microsoft.com/en-us/projects/detours/)
My PC use Intel i3 CPU and Windows 7 32bit.
In addition, I use Visual Studio 2015 Community.
To install detour, I run Visual Studio 2015 Command Prompt.
And do NMAKE(with all option)
Then the error occurs.
=========================================
(Error is written in Korean. I translated it myself)
C:\Program Files\Windows Kits\8.1\include\um\dbghelp.h(1544): warning C4091: 'typedef ': 변수를 선언하지 않으면 '' 왼쪽은 무시됩니다.
C:\Program Files\Windows Kits\8.1\include\um\dbghelp.h(1544): warning C4091: 'typedef ': If you do not define variable, left side of '' will be ignored.
C:\Program Files\Windows Kits\8.1\include\um\dbghelp.h(3190): warning C4091: 'typedef ': 변수를 선언하지 않으면 '' 왼쪽은 무시됩니다.
C:\Program Files\Windows Kits\8.1\include\um\dbghelp.h(3190): warning C4091: 'typedef ': If you do not define variable, left side of '' will be ignored.
What's wrong, and what should I do?
====additional information ===
In Windows Kits folder, there are 4 folders. 8.0, 8.1, 10, NETFXSDK
I think this Windows Kits folder was installed when I installed VS 2015
Does it have any relationship with the error?
You can lower remove treating warnings as errors /WX (project properties:c/c++:general. Or you can just manually delete the word typedef in the dbghelp.h at the two places the compiler flagged.
Related
While installing python package I get the following error even though I have latest Microsoft Visual Studio BuildTools installed.
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
I have added all possible paths to Path variables as well
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VisualStudio\v16.0\Python Tools
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
C:\Program Files (x86)\MSBuild\14.0\Bin
C:\Program Files (x86)\MSBuild
Installing fulll vs_BuildTools solved it for me . For details follow
https://www.scivision.dev/python-windows-visual-c-14-required
Note MSVC vXXX - VS YYYY C++ x64/x86 build tools version and Windows 10 SDK versions must match
Quick solutions like instaling vc_redist.x64 or VC_redist.x86 didn't
solve it for me.
Nothing needs to be added to environment variables.
Answer
If your vscode is supported in 32 bit version, it raises when you start install some packages. I recommended you to install 64 bit vscode if you are using windows 10.
I reinstalled my machine and installed Visual Studio 2017, Visual Studio 2019 (Preview) and the Intel Compiler 18. Due to unknown reasons, my projects do not work anymore, and I can't figure out what's causing it. Did anyone ever experience the following error message?
My project uses the Intel C++ Compiler 18.0 toolset.
Visual Studio 2017 error message:
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\include\xmemory0(178):
error : identifier "__STDCPP_DEFAULT_NEW_ALIGNMENT__" is undefined
1> enable_if_t<(!_HAS_ALIGNED_NEW || _Align <=
__STDCPP_DEFAULT_NEW_ALIGNMENT__), int> = 0> inline
Visual Studio 2019 (Preview) error message:
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Platforms\x64\PlatformToolsets\Intel C++ Compiler 18.0\Toolset.targets(150,5):
error MSB4062: The "ICMessage" task could not be loaded from the assembly C:\Program Files %28x86%29\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Intel.Build.ICLTasks.v150.dll.
Could not load file or assembly 'file:///C:\Program Files %28x86%29\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Intel.Build.ICLTasks.v150.dll' or one of its dependencies.
The system cannot find the file specified.
Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
Before the reinstallation, my project worked fine. Does anyone have an idea what's going on here?
The system cannot find the file specified.
1.Check whether the Intel.Build.ICLTasks.v150.dll exists in the path C:\Program Files (x86)\Microsoft Visual Studio\2017\xxx\Common7\IDE\VC\VCTargets. According to the error message it's not there, so i guess the Intel Compiler 18 was not successfully installed.
Note that recommended order to do the installation is: Install VS successfully and then install Intel Compiler. If you install the Intel Compiler before installing the VS2017, it will cause issues.
e.g: After installing VS, when I install the Intel Parallel Studio, it will download several files and assemblies to folder C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets for future development. So if I install Intel compiler before installing VS, I can't find Intel.Build.ICLTasks.v150.dll there.
2.And for your original error message in VS2017, I suggest you update your Intel Compiler to 2019 Update3 and higher, see versions. When you reinstall VS, the installer will download latest 15.9.16 version(newer than your old version), so you also need to upgrade your Intel compiler version to resolve some conflicts.
I have recently installed Visual Studio Community 2013 with update 4 and when I try to build my project I get these errors(see below):
C:\Program Files(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(362,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid version number.
1> main.cpp
1>c:\program files (x86)\microsoft sdks\windows\v7.1a\include\sal_supp.h(57): warning C4005: '__useHeader' : macro redefinition
1> C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\sal.h(2886) : see previous definition of '__useHeader'
1>c:\program files (x86)\microsoft sdks\windows\v7.1a\include\specstrings_supp.h(77): warning C4005: '__on_failure' : macro redefinition
1> C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\sal.h(2896) : see previous definition of '__on_failure'
How to solve them? I tried many ways but no luck.
Go to control panel and go to uninstall program.
Choose your visual studio community edition update 4. Select change or repair, if it's there. If it opens to the Visual Studio window then select repair there.
Select repair.
Keep your internet connection on while you do this, so your sdk and platform tools can be updated.
If this doesn't work, there are some links to altering the registry:
https://stackoverflow.com/a/24478856/3956566
https://social.msdn.microsoft.com/Forums/vstudio/en-US/48a4500c-2c48-43dd-822b-10e83258d18b/warning-msb8003-could-not-find-windowssdkdir-variable-from-the-registry-targetframeworkversion-or?forum=visualstudiogeneral
How to set SGEN toolpath in Msbuild to target 3.5 framework
https://code.google.com/p/gyp/issues/detail?id=457
When in VS2010 I add
#include <iostream>
to console aplication template I get many errors in type_traits
error C2275: '_Ty' : illegal use of this type as an expression c:\program files (x86)\microsoft visual studio 11.0\vc\include\type_traits 762 1 pcl1 (Visual Studio 2010)
error C3861: '__is_standard_layout': identifier not found c:\program files (x86)\microsoft visual studio 11.0\vc\include\type_traits 762 1 pcl1 (Visual Studio 2010)
error C2955: 'std::_Cat_base' : use of class template requires template argument list c:\program files (x86)\microsoft visual studio 11.0\vc\include\type_traits 763 1 pcl1 (Visual Studio 2010)
error C2275: '_Ty' : illegal use of this type as an expression c:\program files (x86)\microsoft visual studio 11.0\vc\include\type_traits 768 1 pcl1 (Visual Studio 2010)
an many others...
I don't know why why but I think it's somehow connected with the fact that I'm using both VS2012 and VS2010. How to fix it?
From the error message it is clear that your VS2010 project is somehow being directed to look in the VS2012 include directory, c:\program files (x86)\microsoft visual studio 11.0\vc\include. This is never a good idea.
Check your project settings under C/C++ / General / Additional Include Directories. Remove any references to compiler include directories. The correct directories for your compiler will be automatically located by the system.
I have set-up everything according to instructions on https://github.com/TideSDK/TideSDK/wiki/Windows7-x86-2005
But, scons won't pick up "rc" from PATH:
> scons -s debug=1 sdkinstaller run=1
...
runs fine for a while, until:
...
cl : Command line warning D9035 : option 'Wp64' has been deprecated and will be
removed in a future release
cl : Command line warning D9035 : option 'Wp64' has been deprecated and will be
removed in a future release
boot_win32.cpp
'rc' is not recognized as an internal or external command,
operable program or batch file.
scons: *** [build\win32\objs\boot\support\winboot.res] Error 1
> rc
fatal error RC1107: invalid usage; use RC /? for Help
> echo %path%
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;C:\Program Files\Microsof
t Visual Studio 8\VC\BIN;C:\Program Files\Microsoft Visual Studio 8\Common7\Tool
s;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;C:\WINXP\Microsoft.NET
\Framework\v2.0.50727;C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;C
:\Program Files\ImageMagick-6.8.0-Q16;C:\WINXP\system32;C:\WINXP;C:\WINXP\System
32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Git\cmd;C:\Program
Files\Git\bin;C:\Python25\Scripts;C:\Python25
Googling on this matter suggests the solution to add the VC bin directory to PATH, but as you can see, that is already in place.
Note: I installed and used scons 2.2.0 as well, but then it wouldn't even recognize "cl". At least with scons 1.2.0 it recognizes "cl", but unfortunately not "rc"
First time building on Windows, any advice appreciated!
Virtual machines are cheap and accessible. I'd recommend a clean build environment that is not polluted by several SDK versions.
Might help for someone else, but Visual Studio has it's own CMD which will have these path set. Just open corresponding Visual Studio CMD and compile from there.