blocks|key|1161023|text|当我试图将X64构建添加到从VS2003转换而来的项目中时，我在VS2008中遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161024|我查看了在谷歌上搜索这个错误时找到的所有东西(目标机器，VC%2B%2BDirectories，DUMPBIN....)一切看起来都很好。|1161025|最后，我创建了一个新的测试项目，并做了相同的更改，它似乎起作用了。|1161026|在vcproj文件之间进行比较发现了问题...|1161027|我转换后的项目在“链接器”->“命令行”下将/MACHINE:i386设置为附加选项。因此，设置了两个/MACHINE选项(+x64和i386)，另一个选项优先。|1161028|移除它并在Linker->Advanced->Target+Machine下正确设置它会使问题消失。|1161029|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I experienced the same problem in VS2008 when I tried to add a X64 build to a project converted from VS2003.

I looked at everything found when searching for this error on Google (Target machine, VC++Directories, DUMPBIN....) and everything looked OK.

Finally I created a new test project and did the same changes and it seemed to work.

Doing a diff between the vcproj files revealed the problem....

My converted project had /MACHINE:i386 set as additional option set under Linker->Command Line. Thus there was two /MACHINE options set (both x64 and i386) and the additional one took preference.

Removing this and setting it properly under Linker->Advanced->Target Machine made the problem disappeared.

blocks|key|1161826|text|所有的项目设置似乎都很完美，但我还是得到了错误。查看.vcxproj文件并搜索"x86“发现了问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1161827|<Lib>
++<AdditionalOptions>+/machine:X86+%25(AdditionalOptions)</AdditionalOptions>
</Lib>|code-block|syntax|javascript|1161828|对所有匹配项的快速搜索/替换(十个单独的文件设置)修复了该问题。|1161829|entityMap^0|Q|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

All project settings seemed perfect, but I still got the error. Looking into the <code>.vcxproj</code> file and searching for "x86" revealed the problem:

<pre><code>&lt;Lib&gt;
 &lt;AdditionalOptions&gt; /machine:X86 %(AdditionalOptions)&lt;/AdditionalOptions&gt;
&lt;/Lib&gt;
</code></pre>

A quick search/replace for all occurrances (ten individual file settings) fixed the problem.

blocks|key|946963|text|当您链接到x64+(这是目标机器类型)时，您可能有一个针对x86+(这是模块机类型)的.OBJ或.LIB文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|946964|对.OBJ文件使用DUMPBIN+/HEADERS，并检查文件头值块中的machine条目。|946965|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You probably have one .OBJ or .LIB file that's targeted for x64 (that's the module machine type) while you're linking for x86 (that's the target machine type).

Use DUMPBIN /HEADERS on your .OBJ files and check for the machine entry in the FILE HEADER VALUES block.

blocks|key|1161478|text|在Visual+Studio2012+%2B/-中，“配置属性”.Linker.“命令行”的属性页包含一个标记为"Additional+Options“的框。如果您正在构建x64，请确保该框不包含/MACHINE:I386。My+projects包含并生成了相关错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161479|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In Visual Studio 2012 +/-, the property page for "Configuration Properties'.Linker."Command Line" contains a box labeled "Additional Options". If you're building x64, make sure that box doesn't contain /MACHINE:I386. My projects did and it generated the error in question.

blocks|key|1161123|text|我在构建QT时遇到了这个问题。我在某处读到的说明建议我使用VS命令提示符配置nmake。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161124|我选择了x64命令提示符并毫不费力地执行了configure。当我尝试nmake时，它给出了这个错误。|1161125|我认为一些组件是为32位预先构建的。该错误甚至报告了哪些模块是为x86构建的。|1161126|我使用了32位的默认VS命令提示符，它起作用了。|1161127|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I came across this problem when building QT. The instructions I read somewhere suggested that I configure nmake using VS command prompt.

I chose the x64 command prompt and performed configure without much hassle. When i tried nmake, it gave this error. 

I think some of the components were pre-built for 32-bit. The error even reported which modules were built for x86. 

I used the 32 bit default VS command prompt and it worked.

blocks|key|947130|text|"project+property+-+CUDA+Runtime+API+-+GPU+-+NVCC+Compilation+Type"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|947131|设置64位编译选项-m64+-cubin|unstyled|offset|length|style|CODE|947132|这个提示在编译日志中。如下所示：|947133|nvcc.exe+~~~~~~+-machine+32+-ccbin+~~~~~|947134|"-machine+32"就是问题所在。|947135|首先设置64位编译选项，然后重新设置混合编译选项。然后你就可以看到成功了。|947136|entityMap^0|0|9|B|0|0|0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|V|8|@$G|W|H|X|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$B|C]]|$1|O|3|P|5|F|7|10|8|@$G|11|H|12|I|J]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|F|7|14|8|@]|9|@]|A|$]]]|T|$]]

<pre><code>"project property - CUDA Runtime API - GPU - NVCC Compilation Type"
</code></pre>

Set the 64 bit compile option <code>-m64 -cubin</code>

The hint is at compile log.
Like this:

<pre><code>nvcc.exe ~~~~~~ -machine 32 -ccbin ~~~~~
</code></pre>

That <code>"-machine 32"</code> is problem.

First set 64bit compile option,
next re setting hybrid compile option.
Then u can see the succeed.

blocks|key|947392|text|在Visual+Studio+2013中，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|947393|1)检查项目属性页/配置属性/链接器/所有选项，并更正所有未配置的机器和目录。|947394|2)查看项目属性页/+Configuration+Properties+/+Linker+/+Input并更正所有未配置的目录。|947395|参见示例1)|947396|📷|atomic|offset|length|947397|​|947398|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d544686cd4ee4e7714b355dda248117a.jpeg/|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|11|8|@]|9|@$K|12|L|13|1|14]]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V|W|-4]]]]

In Visual Studio 2013, 

1) Check in the Project Property Pages / Configuration Properties / Linker / All Options and correct all the miss configured machine and directories.

2) Check in the Project Property Pages / Configuration Properties / Linker / Input and correct all the miss configured directories.

See example of 1) 
<img src="https://i.imgur.com/TMXKA6X.jpg"/>

blocks|key|1161174|text|如果您的解决方案具有lib项目，请在属性->库->常规中检查目标计算机属性|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161175|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your solution has lib projects check Target Machine property in Property->Librarian->General

blocks|key|947936|text|vcxproj文件可能包含'MACHINE:i386‘使用编辑器编辑vcxproj文件。去掉它！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|947937|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

vcxproj file may contain 'MACHINE:i386'
Edit vcxproj file with editor. remove it !

blocks|key|948298|text|在我的例子中，将环境变量PROCESSOR_ARCHITECTURE设置为AMD64解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|948299|https://social.msdn.microsoft.com/Forums/en-US/f9303904-81ce-405d-85b3-b66d97e49971|948300|entityMap|0|LINK|mutability|MUTABLE|url^0|C|M|11|5|0|0|2B|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@$9|U|A|V|1|W]]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|G]]]]

In my case, setting environment variable <code>PROCESSOR_ARCHITECTURE</code> to <code>AMD64</code>
fixed the problem.
<a href="https://social.msdn.microsoft.com/Forums/en-US/f9303904-81ce-405d-85b3-b66d97e49971" rel="nofollow noreferrer">https://social.msdn.microsoft.com/Forums/en-US/f9303904-81ce-405d-85b3-b66d97e49971</a>

blocks|key|1161365|text|除了Jhonson的列表之外，还要检查图书馆的文件夹|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161366|在visual+studio中，从主菜单中选择“工具”>“选项”。选择项目和解决方案>+VC%2B%2B目录。从Platform下拉列表中选择x64。|1161367|$(VCInstallDir)lib\AMD64;
$(VCInstallDir)atlmfc\lib\amd64;
$(WindowsSdkDir)lib\x64;|code-block|syntax|javascript|1161368|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In addition to Jhonson's list, also check library's folders

In visual studio, select Tools > Options from the main menu. select Projects and Solutions > VC++ Directories. Select x64 from the Platform dropdown.

<pre><code>$(VCInstallDir)lib\AMD64;
$(VCInstallDir)atlmfc\lib\amd64;
$(WindowsSdkDir)lib\x64;
</code></pre>

blocks|key|1161593|text|这在今天发生在我身上，因为我在x86模式下添加了一个库目录，并且意外地删除了继承的目录，将它们改为硬编码。然后在切换到x64之后，我的VC%2B%2B目录仍然是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161594|"...;$(VC_LibraryPath_x86);$(WindowsSDK_LibraryPath_x86);“|1161595|而不是_x64。|1161596|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This happened to me today because I had added a library directory while still in x86 mode, and accidently removed the inherited directories, making them hardcoded instead.
Then after switching to x64, my VC++ Directories still read:

"...;$(VC_LibraryPath_x86);$(WindowsSDK_LibraryPath_x86);"

instead of the _x64.

blocks|key|1161640|text|首先，尝试以下操作:+1.转到配置管理器并创建一个新的x64+(如果它还没有的话)。2.选择x64解决方案。3.转到项目属性，然后链接器->高级选择x64计算机。4.现在重新构建解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161641|如果仍然如此，您将得到相同的错误。尝试清理解决方案，然后重新生成并打开visual+studio，您将看到最近打开的项目列表，右键单击该项目并将其从该列表中删除。现在转到解决方案，并再次重新打开该解决方案。|1161642|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

First of all try the following things:
1. goto configuration Manager and create a new x64 if it is not already there.
2. select the x64 solution.
3. go to project properties and then Linker->Advanced select x64 machine.
4. Now rebuild the solution.

If still you are getting the same error. try clean solution and then rebuild again and open visual studio you will get list of recent opened project , right click on the project and remove it from there. Now go to the solution and reopen the solution again.

blocks|key|947766|text|这是一个非常令人沮丧和恼人问题，但是一旦您理解了它，它就变得非常简单:您正在构建一种体系结构类型(在您的示例中为x64)，尽管它已被作为另一种类型(例如x86)的目标，但在您的构建过程中仍然存在一些元素。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|947767|您可以通过查看哪个obj文件导致崩溃来剖析问题的根源，并从那里开始查找问题。每个obj都会有一个类似的源代码:+cpp，c，asm等等。可能会有一些特殊的构建事件在使用错误的工具。在属性表中检查它。|947768|在浏览C+Johnson的待办事项清单之前，我会先去那里看看。|947769|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It's a very frustrating and annoying problem but once you understand it, it's quite simple: you have some element in you're build that building one architecture type (in your case x64) despite the fact that it's been target for another type (say x86).

You can dissect the source of your problem by looking at which obj file is causing the crash and start looking for the problem there. Every obj will have a source code analog: either in cpp, c, asm etc. There may be special build events around it that are using the wrong tool. Check for that in the property sheets. 

I'd look there first before going through C Johnson list of things to do.

blocks|key|948039|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948040|📷|atomic|offset|length|948041|我在Visual+Studio2013中将Win32改为*64解决了这个问题。|948042|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5c1d5e0f5772ba6332b1e5295047d054.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

<a href="https://i.stack.imgur.com/68BdV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/68BdV.png" alt=""></a>
I solved this problem by changing Win32 to *64 in Visual Studio 2013.

blocks|key|1162158|text|上面有很多好的建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1162159|另外，如果您正在尝试在x86+Win32中构建：|1162160|确保您在Program+Files(+x86+)中链接的任何库实际上都是x86库，因为它们不一定是...|1162161|例如，我在C:\Program+Files+(+x86+)\Microsoft+Visual+Studio\2019\Professional\SDK中链接的一个库文件抛出了这个错误，最终我在C:\Program+Files+(x86)\Windows+Kits\10\+lib+\10.0.18362.0\um\x86中找到了它的x86版本，一切工作正常。|1162162|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Many good suggestions above. 

Also if you are trying to build in x86 Win32: 

Make sure that any libraries you link to in Program Files(x86) are actually x86 libraries because they are not necessarily... 

For example a lib file I linked to in C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\SDK threw that error, eventually I found an x86 version of it in C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x86 and everything worked fine.

blocks|key|1162192|text|我的目标是一个用C语言编写的x64+Windows10文本模式DOSBox应用程序。使用"Visual+Studio2019社区“通过DOS提示"nmake+-f+makefile”进行编译。错误是相似的，但在相反的方面：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1162193|fatal+error+LNK1112:+module+machine+type+'x32'+conflicts+with+target+machine+type+'X64'|code-block|syntax|javascript|1162194|可以在另一台计算机上使用VC%2B%2B+2010进行编译。但在此计算机上通过"Visual+Studio+2019社区“失败。因此，我的设置是正确的，并且以上所有答案都不起作用。|1162195|我想跟大家分享一下，解决方案是这样的一个make.bat：|1162196|call+"c:\Program+Files+(x86)\Microsoft+Visual+Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat"+
nmake+-f+makefile|1162197|你会发现有很多其他的vcvarsxxxx.bat，只有这一个单词。|1162198|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

My target is a x64 Windows 10 text mode DOSBox application in C language.
Using &quot;Visual Studio 2019 Community&quot; to compile through DOS prompt &quot;nmake -f makefile&quot;.
The error is similar but on the opposite side:
<pre><code>fatal error LNK1112: module machine type 'x32' conflicts with target machine type 'X64'
</code></pre>
It's ok to compile by VC++ 2010 on another computer. But failed on this computer by &quot;Visual Studio 2019 Community&quot;. So my settings are correct and all above answers do not work.
I'd like to share you that the solution is a make.bat like this:
<pre><code>call &quot;c:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat&quot; 
nmake -f makefile
</code></pre>
You will find there are many other vcvarsxxxx.bat, only this one words.

blocks|key|948378|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948379|📷|atomic|offset|length|948380|948381|属性->配置管理器->+ActiveSolutionPlatform。在这里选择x64+.thats+all。|948382|它应该照顾到所有的依赖项，并且编译应该能够顺利地工作|948383|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ceef093fdb8bd1a9a87ced2511136370.png|imageAlt^0|0|0|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@$E|W|F|X|1|Y]]|A|$]]|$1|G|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

<a href="https://i.stack.imgur.com/srXfi.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/srXfi.png" alt="" /></a>
Properties-&gt;configurationManager-&gt; ActiveSolutionPlatform . Here select x64 .thats all.
It should take care of all dependencies and compilation should work smoothly

blocks|key|1161151|text|模块机器类型是在其上编译的机器，目标机器类型是为其构建二进制文件的体系结构x86或x64。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161152|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

module machine type is the machine on which you are compiling and the target machine type is the the architecture x86 or x64 for which you are building your binaries.

blocks|key|1161527|text|如果将项目设置为在项目属性->配置属性->常规中具有相同的中间目录，也可能会出现此问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161528|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This problem may also happen if your project set up to have the same intermediate directories in Project Properties -> Configuration Properties -> General

blocks|key|1161774|text|当我将我的VS2008解决方案转换为VS2010并将win32配置更改为X64时会发生这种情况，在我的旧解决方案中，我有mfcs90d.lib+(配置->链接器->输入->附加依赖项)，因为我使用的是VS010，所以我在VS2010文件夹中检查了它是mfcs100d.lib，所以我在(配置->链接器->输入->附加依赖项)中将mfcs90d.lib更改为mfcs100d.lib，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161775|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

this happens to me when i convert my VS2008 solution to VS2010 &amp; change win32 configuration to X64, in my old solution I have mfcs90d.lib (Configuration->Linker->Input->Additional dependencies), as I am using VS010 i just checked in VS2010 folder where it is mfcs100d.lib, so I changed mfcs90d.lib to mfcs100d.lib in (Configuration->Linker->Input->Additional dependencies) it worked fine.

blocks|key|948089|text|对于那些使用QT+Creator的人来说，问题是相同的(如@c-johnson所描述的)。确保工具包中MSVC的编译器设置设置为x86，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948090|​|948091|📷|atomic|offset|length|948092|948093|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5dfd99854ffe6a423c81430736894179.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

For those who are with QT Creator, the issue is same (as described by @c-johnson).
Make sure the compiler settings for MSVC in your kit is set to x86 as shown below.

<a href="https://i.stack.imgur.com/Mw91J.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Mw91J.png" alt="QT Creator Kit Settings for MSVC x86 compiler"></a>

blocks|key|947019|text|操作系统是什么？如果它是windows+x64，那么您需要确保安装了CUDA+x64，因此VS2008应该在x64模式下编译项目……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|947020|CUDA将只在windows中安装x64或x86|947021|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

what is the OS? if it is a windows x64 then you need to make sure that CUDA x64 was installed and thus that VS2008 should compile the project in x64 mode...

CUDA will only install x64 OR x86 in windows

blocks|key|948244|text|我已经为自己解决了这个问题，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948245|首先，我遵循了这个问题的其他答案，但得出的结论是所有项目设置都是正确的。|948246|然后，我用编辑器检查了.vcxproj文件，注意到两个(调试和发布)+x64配置的<+Link+>属性没有指定<+TargetMachine+>，而Win32配置都包含<+TargetMachine+>+MachineX86+<+/TargetMachine+>。|948247|然而，我已经验证了，从Visual+Studio的属性>配置属性>链接器>高级>目标计算机，x64配置显示为MachineX64+(/MACHINE:X64)。|948248|因此，我编辑了.vcxproj文件，使其在两个x64配置中包含<+TargetMachine+>+MachineX64+<+/TargetMachine+>。返回到Visual+Studio项目属性对话框，我注意到MachineX64+(/MACHINE:X64)设置和以前一样，只是现在它显示为粗体(显然意味着该值不是默认值)。|948249|我重建了它，它起作用了。|948250|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I have fixed this problem for myself as follows.
First of all, I followed the other answers for this question, only to conclude that all the project settings were correct.
Then I inspected the .vcxproj file with an editor and noticed that the &lt; Link &gt; properties for the two (Debug and Release) x64 configurations did not specify &lt; TargetMachine &gt;, while the Win32 configurations both contained &lt; TargetMachine &gt; MachineX86 &lt; /TargetMachine &gt;.
However, I had already verified, looking from Visual Studio at Properties &gt; Configuration Properties &gt; Linker &gt; Advanced &gt; Target Machine, that the x64 configurations said MachineX64 (/MACHINE:X64).
So, I edited the .vcxproj file to include &lt; TargetMachine &gt; MachineX64 &lt; /TargetMachine &gt; in the two x64 configs. Going back to the Visual Studio project properties dialog, I noticed that the MachineX64 (/MACHINE:X64) setting was there as before, except that now it showed in bold (apparently meaning that the value is not the default one).
I rebuilt, and it worked.

I'm using CUDA (VC++, Visual studio 2008sp1) to debug a FEM program. The program can only run on a Win32 platform, for the insufficiency of cuda. I think the library files linked are all compiled on the x86 platform, but when I compile it, I get the error message "fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'". 

I have tried to convert the platform to x64, but it didn't work. Please tell me: what is "module machine type" and what is "target machine type"? How can I overcome it?

fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'

Visual Studio

编译器

Windows

我正在使用CUDA (VC++，Visual studio 2008sp1)来调试一个有限元程序。由于cuda的不足，该程序只能在Win32平台上运行。我认为链接的库文件都是在x86平台上编译的，但是当我编译它时，我得到错误消息"fatal error LNK1112: module machine type 'x64‘conflicts with target machine type 'X86

问致命错误LNK1112:模块计算机类型'x64‘与目标计算机类型'X86’冲突
EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误LNK1112:模块计算机类型'x64‘与目标计算机类型'X86’冲突EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误LNK1112:模块计算机类型'x64‘与目标计算机类型'X86’冲突
EN