visual-c++-2012

fatal error LNK1104: cannot open file 'mfc110d.lib'

偶尔善良 提交于 2019-12-04 20:31:57
I am currently developing a program in VS c++ 2012 ( Ultimate trial version). It uses 3rd part lib ( Qt5.1.1 x64 and openCV 2.4.5 ). When I try to build it it gives " fatal error LNK1104: cannot open file 'mfc110d.lib'". I tried to find this lib but it seems that it does not exist on my machine. This project was initially developed on a different machine. Have anyone met this problem before? Solved! Indeed, MFC was not installed by default. I had to go to Control Panel-> Uninstall a program -> Visual Studio 2012 right click -> Change . Then check Install MFC and that's it. Thank you all for

How to make Visual Studio 2012 call the native 64-bit Visual C++ compiler instead of the 32-bit x64 cross-compiler?

廉价感情. 提交于 2019-12-04 13:02:58
问题 Visual Studio 2012 seems to always call the 32-bit version of cl.exe located at %ProgramFiles(x86)%\Microsoft Visual Studio 11.0\VC\bin\x86_amd64 ) instead of the 64-bit one located at %ProgramFiles(x86)%\Microsoft Visual Studio 11.0\VC\bin\amd64 . I tried prepending $(VCInstallDir)bin\amd64 to the beginning of the "Executable Directories" list in the VC++ Directories section of the Microsoft.Cpp.x64.user property sheet, but that doesn't work at all -- when I rebuild I get this error: TRACKER

VC++ 2012: How to include version info from version.inc (maintained separately) into the .rc file

Deadly 提交于 2019-12-04 03:12:57
Summary: Having the version details defined in the separately maintained version.inc via preprocessor macros... How to include the macro values into the resource version definition block? My version.inc file is stored in UTF-8 (i.e. pure ASCII in the case). Its full content is the following (the APS_ prefix here is related to the real name of the application, not to the .aps file generated by the resource compiler): #define APS_MAJORNUMBER 4 #define APS_MINORNUMBER 5 #define APS_BUILDNUMBER 0 #define APS_MODIFICATIONNUMBER 0 #define APS_BUILDEXT "wx" #define APS_DATEYEAR 2012 #define APS

how to convert XMMATRIX to D3DMATRIX in DirectX 9?

戏子无情 提交于 2019-12-02 07:38:34
问题 I learn DirectX (DirectX 9) from www.directxtutorial.com and using visual studio 2012 in windows 8. d3dx9 (d3dx) replace by other header like DirectXMath, therefore I replaced all that is needed, but there is a problem - convert XMMATRIX to D3DMATRIX. The problem code (The problem written - / problem! /): void render_frame(void) { // clear the window to a deep blue d3ddev->Clear(0, NULL, D3DCLEAR_TARGET, D3DCOLOR_XRGB(0, 0, 0), 1.0f, 0); d3ddev->BeginScene(); // begins the 3D scene // select

how to convert XMMATRIX to D3DMATRIX in DirectX 9?

早过忘川 提交于 2019-12-02 03:35:57
I learn DirectX (DirectX 9) from www.directxtutorial.com and using visual studio 2012 in windows 8. d3dx9 (d3dx) replace by other header like DirectXMath, therefore I replaced all that is needed, but there is a problem - convert XMMATRIX to D3DMATRIX. The problem code (The problem written - / problem! /): void render_frame(void) { // clear the window to a deep blue d3ddev->Clear(0, NULL, D3DCLEAR_TARGET, D3DCOLOR_XRGB(0, 0, 0), 1.0f, 0); d3ddev->BeginScene(); // begins the 3D scene // select which vertex format we are using d3ddev->SetFVF(CUSTOMFVF); // SET UP THE PIPELINE DirectX::XMMATRIX

C++11 filesystem (VS2012)

允我心安 提交于 2019-12-01 15:43:21
I am having a lot of trouble finding any documentation on the header included with vs2012. I see that it is mentioned here but they don't provide a link on how to use it. What I am really looking for is documentation for how to use it, with the visual studio implementation being preferred. Thanks The <filesystem> header is not part of C++11; it is a proposal for C++ TR2 based on the Boost.Filesystem library. Visual C++ 2012 includes an implementation of the proposed library. See the MSDN documentation for the <filesystem> header and the C++ TR2 proposal on which the implementation is based

decltype and member function (not pointer) type

折月煮酒 提交于 2019-12-01 13:01:53
struct C { int Foo(int i) { return i; } typedef decltype(C::Foo) type; }; Since there is no such type as a member function type (there isn't, is there?), I expect C::type to be int (int) . But the following won't compile using the Visual C++ 2012 RC: std::function<C::type> f; So what type is decltype(C::Foo) ? The code is ill-formed: there are only a few ways that a member function name (e.g. C::Foo ) can be used, and this is not one of them (the complete list of valid uses can be found in the C++ language standard, see C++11 §5.1.1/12). In the context of your example, the only thing you can

decltype and member function (not pointer) type

♀尐吖头ヾ 提交于 2019-12-01 11:51:04
问题 struct C { int Foo(int i) { return i; } typedef decltype(C::Foo) type; }; Since there is no such type as a member function type (there isn't, is there?), I expect C::type to be int (int) . But the following won't compile using the Visual C++ 2012 RC: std::function<C::type> f; So what type is decltype(C::Foo) ? 回答1: The code is ill-formed: there are only a few ways that a member function name (e.g. C::Foo ) can be used, and this is not one of them (the complete list of valid uses can be found

Possible compiler bug in Visual C++ 2012 (x86)?

做~自己de王妃 提交于 2019-11-30 16:53:13
I'm currently experiencing random floating point errors when compiling for x86 targets using VC++ 11 (CTP Update 1) . See the short example "test.cpp" below, and compile using: cl /GL /O2 /EHsc test.cpp /link /MACHINE:X86 The output should be 10 == 10 , but it produces 10 == 0 when /GL (whole program optimization) is enabled. The problem seems to be that get_scaling_factor() pushes the result on the floating point stack, but the calling function is expecting it in the SSE register XMM0 . Question : am I missing something obvious, or is this really a bug? The test program, of course, doesn't

Possible compiler bug in Visual C++ 2012 (x86)?

我与影子孤独终老i 提交于 2019-11-30 16:23:16
问题 I'm currently experiencing random floating point errors when compiling for x86 targets using VC++ 11 (CTP Update 1) . See the short example "test.cpp" below, and compile using: cl /GL /O2 /EHsc test.cpp /link /MACHINE:X86 The output should be 10 == 10 , but it produces 10 == 0 when /GL (whole program optimization) is enabled. The problem seems to be that get_scaling_factor() pushes the result on the floating point stack, but the calling function is expecting it in the SSE register XMM0 .