ActiveMQ CPP and Visual Studio 2003
I've have a requirement to get AMQ to work with some code that requires VS 7.1, however I'm having a difficult time getting it and various Apache libraries like apr etc to build using VS 7.1. There is a vs2008 solution/project for AMQ-CPP, I've used that as a template and tried to create one for VS 7.1,
However when trying to build, I get errors like the following:
"\amq\activemq-cpp-library-3.4.1\src\main\activemq\util\primitivemap.cpp(70): fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c', line 148)"
In short has anyone been able to build and successfully run AMQ with VS 7.1? Is the compiler supported?
I've gone through the FAQ (found nothing to indicate one way or the other) and posted questions on their ML but to no avail.
Any info or links would be great.
http://activemq.apache.org/cms/index.html
VS2003 is not supported, there are just to many C++ spec incompatibilities in that version to allow the code to compile.
Related
When I build a project by visual studio 2013, it runs properly. But I encounter following errors after building with visual studio 2015. How can I solve this problem?
fatal error C1001: An internal error has occurred in the compiler.
Command line error D8040: error creating or communicating with child process
C1001 is an "ICE", an Internal Compiler Error. It means your code generated a fatal bug in the compiler. Are you using VS 2015, VS 2015 Update 1, or VS 2015 Update 2?
One way to find which version of the compiler you have installed is to run the Developer Command Prompt for VS 2015 and then run the following command: cl -Bv and note which versions are reported. VS 2015 Update 2 is 19.00.23918.0
An "ICE" is always a bug. If your code is doing something wrong, the compiler should emit an error or a warning, not crash out. It's also possible your code is just fine, and there's been a new bug introduced in the compiler since VS 2013. There's been a lot of work done to the compiler to fully support C++11 as well as support the upcoming C++14/C++17 drafts.
You should file a bug on VS Connect. See this article for directions on creating a good repro. This blog post is also a great write-up of how to narrow down compiler problems.
In most cases, it's very difficult to repro an ICE with just a few lines of code, and is only triggered in very specific contexts. This is why the instructions above are all about providing a minimal repro that captures the essence of the problem. You can also try a newer build compiler to see if the problem has already been fixed.
Many thanks Walbourn. Your solutions are so effective. I resolved this problem by the following settings in visual studio 2015:
1- Disable c/c++->general->Multi-processor compilation
2- Disable c/c++->general->optimization
3- Disable c/c++->language->open mp support
The probable reason could be long project path.
I've recently discovered Emscripten as a way of writing native code and running it in a web browser.
I'd like to work with an IDE for code completion and be able to customize the build process for Emscripten.
The only tool I've found to build Emscripten this way is with VS2010 which has very limited c++11 support so that's not desirable.
I thought of using VS2013 and writing a custom build script but I've never used VS so I'm unsure how to do that or if it's even possible.
What are people using to work with Emscripten?
Not sure if you are aware of this. On the requirements page, the following is stated:
Visual Studio 2010 is required! Visual Studio 2012 and Visual Studio 2013 do not correctly compile Fastcomp. This issue will be fixed (eventually) when Fastcomp is migrated to use a LLVM 3.4 or later.
I'm trying to run code analysis for the first time on my native C++ application. I'm developing using Visual Studio 2013 Ultimate and compiling using the Visual C++ Compiler Nov 2013 CTP (CTP_Nov2013), which is the latest (I believe) compiler from MS for C++11. When trying to run Code Analysis I receive the following warning:
warning D9040: ignoring option '/analyze'; Code Analysis warnings are not available in this edition of the compiler
So I'm wondering if it's because I'm using this new compiler that it's not able to run code analysis or what. But I couldn't find any answers by briefly Googling. The MSDN for Visual Studio says code analysis works for all version of VS except Express. Any help would be appreciated, and if it's a "No it doesn't work with that compiler" then that's fine. Just wondering. Thanks!
It seems to work only for x86 builds. If you're doing an x64 build, it won't be available.
As an extension on one of my earlier projects that required printing PDF files from command line, I now need to print them duplex.
Therefore I have found an open source piece of software called SumatraPDF and added a patch using Visual Studio Express 2012 that enables duplex settings in command line and compiled. This software works completely on Windows 7 64bit however on Windows Server 2003 64bit it returns an error message:
C:\Program Files (x86)\SumatraPDF\SumatraPDF.exe is not a valid Win32 application.
I have found examples on the internet of others having this issue when compiling applications using VSE2012 and have tried to follow the advice given. This being to change the project platform to Windows XP (v110_xp) after installing VS Service Pack 3, however to do this I would have to change the project configuration type from Makefile to Application (.exe) and after testing this causes errors during compilation.
I have now also implemented #Hans advice with the same result.
If anyone can help I would be most appreciative.
Thanks.
NB - I have looked at other questions regarding this subject and did not feel any supplied me with a solution, apologies if I have overlooked it.
I am in the process of evaluating an upgrade to Windows SDK 7.1
Part of my team's legacy codebase is a large number of ATL web services, which are still maintained using Visual Studio 2005 because (I am told) ATL web services are not supported in versions beyond 2005.
When I pointed the IDE to SDK 7.1, I began to receive the following link error:
uuid.lib(cguid_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module
I haven't been able to find much on the web related to this problem in VS2005 and SDK 7.1.
I found some forum posts from back in 2005 about the same error -- they seemed to indicate an SDK incompatibility.
Based on the download page, I was under the impression that Windows SDK 7.1 could be used with Visual Studio 2005 (although I do note the "Not all features work with all versions of Visual Studio" disclaimer).
Is this a known issue, or have I got something configured incorrectly?
I was hoping someone could share their experience or suggest how/if I might be able to resolve this.
EDIT:
I discovered that this problem is circumvented by disabling /DEBUG on the linker command line. While allowing the build to complete, this is suboptimal as it precludes debugging during future maintenance.
The hotfix listed here appears to address the link error. Not sure how I missed it before.
Including here in case anyone ever searches for it using similar language.