I have a native c++ program exe which builds successfully and runs successfully in the release version. However when i try to run debug exe, it throws an exception "This application has failed to start because MSVCP80D.dll was not found. RE-installing the application may fix the proble,
Try statically linking the runtime libraries if you need to run a debug build on a PC that does not have Visual Studio installed.
http://msdn.microsoft.com/en-us/library/abx4dbyh(v=VS.100).aspx
That is because you don't have the DEBUG version of the C/C++ runtime on that machine, only the RELEASE builds. Debug builds are meant only for development and debugging. You should not install/distribute them, only Release builds. And you should install the appropriate redistributable with the VC++ runtimes.
Related
I have a Service Fabric project with this structure:
MyServiceFabric.sfproj
MyService.cspro
MyCommonCppMixedDll.vcxproj
If I compile from VS and from the command line:
msbuild MyServiceFabric.sfproj /p:Configuration="Release" /p:Platform="x64"
everything compiles as expected. When I try to Publish the project from VS, it works, but from the command line it fails. This is the command line I'm using:
msbuild MyServiceFabric.sfproj /p:Configuration="Release" /p:Platform="x64" /t:Package
the errors I'm getting, are related to the c++ project, that it fails to compile the platform Win32. If I remove the platform win32 from the c++ project, I receive the error:
This project t doesn't contain the Configuration and Platform combination of Release|Win32.
Obviously I don't want to compile half of the project in x64 and the c++ project in win32. For some strange reasons msbuild doesn't forward the platform to the c++ project.
I've seen in Microsoft.Cpp.Default.pros line #88 that if the platform is not specified, it default fall in Win32.
Any Ideas ?
We're currently making a build environment for some of our projects.
In particular we're using VC++ 6.0 and VS2019 to build some of these projects.
When building our C++ project in VS2019 with the Platform Toolkit set to C++ 2015 v140, MSBuild attempts to use the VC++ 6.0 compiler to build the project. If I switch the Toolkit to any other version it builds with the correct cl.exe.
If I remove the VC98 folder that contains cl.exe from the path environment variable I get a cl.exe can't be found error in VS2019.
So I think there's something hardcoding the 2015 toolkit against the VC6.0 cl.exe.
I've tried installing and reinstalling the additional components in the VS Installer but no luck.
Repair of VS2019 didn't fix it either.
I've tried all versions of Visual Studio back to 2013 same issue.
This looks like an MSBuild issue, it's in the wrong location.
Is there any place where I can view the mapping for the toolkits in MSBuild? I couldn't see much in the registry.
The output when I build shows the following, the version is clearly a very old compiler (the VC6.0 one):
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86
I'm porting an application from VS 2005 to VS 2019. I successfully ported the debug version but faced with issues during release one.
First, when I launch my release app, I got an error "MSVCP80.dll not found". It's strange because debug version successful find the dll in the "C:\Windows\winsxs\x86_microsoft.vc80.debugcrt_1fc8b3b9a1e18e3b_8.0.50727.762_none_24c8a196583ff03b"
Second, if I copy MSVCP80.dll and MSVCR80.dll to the release/bin folder I got an error: "R6034 an application has made an attempt to load the c runtime library incorrectly" and "The application was unable to start correctly (0xc0000142)"
So, there the problem? Is any DLL missing in my system? Or it is a build issue? Why debug is Ok bur release is failed?
I have an Android Studio NDK module with about 200 small C files I'm trying to build as a native library. When I do a build either from within Android Studio or from the command line with gradlew, the build process hangs part way thru compiling one of the files. Which file it hangs on is random from build to build. When the build hangs the only recourse is to kill the clang process(es) and try again. On rare occasions it will actually complete.
One guess I have is that there is some windows issue with multiple simultaneous compiles for the module. Is there a way to force make to use -j1 to test this?
Are there other reasons the build would hang?
Environment - Windows 10, Android Studio 2.3.3, Gradle 3.4.1
When I trying to install karma on windows 7. I am getting following message
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere. [C:\Users\user\AppData\Roaming\npm\node_modules\karma\
node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\bind
ing.sln]
I installed .NET Framework 2.0 Software Development Kit (SDK) (x86) . still getting same error
Keep
Calm
and
Continue
Using
Karma
Here's the Karma owner's (Vojta Jina) comment on the issue:
this is just optional compilation of native module to speed things up.
Even without native module it will still work.
In any case, not a Karma issue, so closing. If you want to compile
native modules, use linux/mac ;-)
Btw. regarding your getting the same error even after SDK install, possibly VCBuild.exe and/or C++ compiler is not added to path.