I'm getting the following error while building FireBreath Solution file .
The C Compiler Identification is unknown and
The CXX Compiler Identification is unknown
Can any one help me figuring out where am I doing wrong.
Note: 1) I have VS professional installed with c++ compilers and libraries
This may help
start visual-studio-2012 command prompt (e.g. Win64)
run cmake command with appropriate generator (e.g. -G "Visual Studio 12 Win64")
My research indicates that this is most likely a broken visual studio installation. You can try uninstalling / reinstalling, but if that doesn't work you might try making a new question that isn't tied to firebreath or plugins (which leads people to think they need to know something about firebreath or plugins to help you) and just asks about the error you're getting with cmake, since hte issue is actually that cmake isn't finding Visual Studio.
I have had this happen to me once before with VS2010 and to be honest I just ended up reinstalling the system. There is a thread about a similar issue where someone fixed it by copying an installation from another computer.
Other than that, I really have no idea.
Related
I recently updated to the latest version of XCode and Xamarin Xamarin.iOS 10.0.0.1 (29910bb) running Visual Studio Professional 2015 Version 14.0.25431.01 Update 3. Both my Mac (build machine) and PC are fully up to date. Now that i have update i am no longer able to compile/build for anything but the simulator.
Compiler Error.
> C:\Program Files
> (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(1028,3): error :
> Failed to read file attributes for
> "/Users/mod/Library/Caches/Xamarin/Resources/Images.xcassets"
As a test i copied the solutions file over to the build machine and with no modifications it compiles and runs any of the targets.
I have also tried deleting the builds directory on the build machine and no help.
Anyone know what the work around is for this?
I have come across is this issue and what seems to possibly be related to on Xamarin Forums. The thing I found in my case was related to image assets within a library I was trying to use. I was able to remove the image assets and relocate to main project and that seemed to resolve the build issue.
This problem, like you have found is very recent. For what's it worth, I have also found that command line tools have numerous issues as they seem to lag behind the GUI provided in either Xamarin Studio or Visual Studio.
Good luck
As mentioned here I had to delete the folder ~/Library/Caches/Xamarin/mtbs/builds on the Mac used for the builds.
After a rebuild it worked again.
when i try to run a application developed in vc++ on windows7,i get popup window saying that"the program can not be started because MSVCR80D.dll is missing from your computer,try reinstalling the program to fix this issue."
I googled it,it says that this DDL may not be present in your system or it has been got corrupted,Now i searched this file, i get this file at 20 different folder in win7.
I am not getting which file has been corrupted or if it is missing then where it is mising?
can anybody tell in which folder ,this DDL is missing or might be corrupted?
Thanks in advance. .
You're trying to run a Debug version of your program on a machine which does not have VS installed. The MS*D.dll files are not redistributable - they are installed were VS is installed. If you want to run executables on other machines, compile them as Release. You might still need to deploy some files (depending on how you're linking to the CRT), but that won't be a problem.
Never ever distribute your DEBUG builds to customers. Always distribute Release build.
Yes, of course, in develoment environment having multiple machines, you may share Debug builds to other developers - provided others developers have debugging-tools (like VS) installed on their system along with Debug-binaries of shared DLLs (like MSVCRxx).
Are you using the same computer that compiled the program? If not, you need visual studio redistributable files to run it.
Search the internet for your version of visual studio or visual c++ redist, you'll find it.
i am new in using the Visual Leak Detector, after creating the settings as per the documentations for Visual C++ 6, and running the program in the debug mode
the error
"The application has failed to start because vld_x86.dll was not found.Re-installing the application may fix this problem"
i have reinstalled and included the path for the dll in the VC6 settings.
thanks in advance for the help.
After searching for the answer myself for quite a long time, two things finally corrected the problem for me. First, if you haven't already restarted Visual Studio after including these new files and libraries, then you should do so. Second, when I went to look into my computer to see what was added to my path in environment variables, it had add the win64. and I run win32. Hope that was descriptive enough and helps.
the include is correct and needed as far as i know.
i was having the same problem and could solve it by copying all files in vld's "bin" directory into the same folder as the executable i wanted to check for leaks.
not a very elegant way but working, i hope it works for you aswell!
Does anyone have any clue as to what this might mean?
(ClCompile target) -> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(147,5): error MSB6006: "CL.exe" exited with code -1073741515.
It builds fine on my dev box but fails due to this error on our CI box. It's running on .NET 3.5.
Any help would be MUCH appreciated.
See this Microsoft Feedback report. From the article:
The error definitley needs to be a better one. What it should be telling you is that a tool failed. The issue is most likley that you don't have the Visual Studio 2008 bits on your box. So, when the project was re-targeted to the v90 platform toolset (which is the set of Visual Studio 2008 tools; can be installed with the proper version of the Windows SDK that goes with Visual Studio 2008 which I believe is v6.0A) and the tools were not installed, the build failed because it could not find the tools.
The reason that it re-targets to the v90 toolset is because that is the compiler that matches with the version that corresponded to the v2.0 CLR.
Based on where we are in the current cycle, we can't change the message. But, since we need to improve the error message in this scenario, I have resolved as postponed so that we can look at this in the next cycle.
I know this is an old question but I stumbled across a similar crash:
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(147,5): error MSB6006: "CL.exe" exited with code -1073740777.
Entirely reproducible and extremely annoying. In my case it seems to have been related to the insanely long include path list my client uses (over 16Kb of include path text, several hundred include paths to search) and when I cleaned this up and reduced the overall size the crash went away.
My suspicion is therefore that Microsoft have a 16Kb buffer somewhere in their compiler that when full simply bombs. Hope that helps someone.
This is the error Dependency Walker gives me on an executable that I am building with VC++ 2005 Express Edition. When trying to run the .exe, I get:
This application has failed to start because the application configuration
is incorrect. Reinstalling the application may fix this problem.
(I am new to the manifest/SxS/etc. way of doing things post VC++ 2003.)
EDIT:
I am running on the same machine I am building the .exe with. In Event Viewer, I have the unhelpful:
Faulting application blah.exe, version 0.0.0.0, faulting module blah.exe,
version 0.0.0.0, fault address 0x004239b0.
Open the properties sheet for your project, go to the Configuration Properties -> C/C++ -> Code Generation page, and change the Runtime Library selection to /MT or /MTd so that your project does not use the DLL runtime libraries.
The C/C++ DLL runtimes used by VS2003 and up are not automatically distributed with the latest version of the OS and are a real pain to install and get working without this kind of problem. statically link the c-runtime and just avoid the total mess that is manifests and version specific runtime dlls.
I've had this problem. The solution has two steps:
1. Compile your program in "Release" mode instead of "Debug" mode (there's usually a combo-box in the toolbar)
2. Download from Microsoft their Redistributable Package of runtime components. Make sure to download the x86 edition for 32-bit computers and the x64 edition for 64-bit computers/OSes. Install this package on the target computer, and your application should run fine
P.S. This is a SxS thing
P.P.S. Alternatively, use a different compiler (like GCC, for example with Dev-Cpp) to compile your program's source, and your headaches will disappear.
Sorry to bump an old question, but I was able to get around this exact issue and thought I'd post a solution in case someone else needs it...
Even after installing Microsoft's redistributable DLLs I was getting this error, the fix was to copy the
C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\Microsoft.VC80.CRT
folder into the application's directory on the target PC. After that, no more problems.
BTW, the DLL that was giving me issues was a 3rd-party DLL that had never had problems before on over 100 other computers... go figure.
Run Event Viewer: it'll have more information.
Probably you've attempted to run your program on a machine that doesn't have the VC redistributables installed, or you're attempting to run a debug build on a machine that doesn't have Visual Studio installed (the debug libraries aren't redistributable).
I have had the same issue with VS 2008-built debug binaries on other winxp sp3 machines.
I first tried installing the client machine with vc redist package,as it seemed sensible. Annoyingly, it didn't work.
I tried copying all the dependent dlls to the application's directory - still didn't work
After being struck over this issue for hours, I found that the latest VS builds require manifests and policies to link with the dlls. After copying them into their respective "C:\WINDOWS\WinSxS\" folders, I got it working.
The problem was caused due to the fact that the vc redist package did not install debug versions of dlls, they somehow thought its up to the programmer to figure out.