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

Question

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

User · Answer

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     VCInstallDir lib AMD64    VCInstallDir atlmfc lib amd64    WindowsSdkDir lib x64

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

vcxproj file may contain  MACHINE i386  Edit vcxproj file with editor  remove it

User · Answer

Since the problem is due to the difference in compilation and target machine specifications  x86  amp  x64  Follow the steps below     Open the C   project that you want to configure  Choose the Configuration Manager button to open the Configuration Manager dialog box  In the Active Solution Platform drop-down list  select the  option to open the New Solution Platform dialog box  In the Type or select the new platform drop-down list  select a 64-bit platform    It solved my problem

User · Answer

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

User · Answer

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  fatal error LNK1112  module machine type  x32  conflicts with target machine type  X64   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  call  quot c  Program Files  x86  Microsoft Visual Studio 2019 Community VC Auxiliary Build vcvars64 bat quot   nmake -f makefile  You will find there are many other vcvarsxxxx bat  only this one words

User · Answer

I solved this problem by changing Win32 to  64 in Visual Studio 2013

User · Answer

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

User · Answer

for some using command prompt  dos prompt  this might be helpful   call  C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  --help Error in script usage  The correct usage is       C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat   option    or      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat   option  store   or      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat   option   version number    or      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat   option  store  version number  where  option  is  x86   amd64   arm   x86 amd64   x86 arm   amd64 x86   amd64 arm where  version number  is either the full Windows 10 SDK version number or  8 1  to use the windows 8 1 SDK   The store parameter sets environment variables to support   store  rather than desktop  development    For example       C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x86 amd64      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x86 arm store      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x86 amd64 10 0 10240 0      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x86 arm store 10 0 10240 0      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x64 8 1      C  Program Files  x86  Microsoft Visual Studio 14 0 VC vcvarsall bat  x64 store 8 1   Please make sure either Visual Studio or C   Build SKU is installed    Also If you do like this   CL    1 2 3    EHsc   link user32 lib Gdi32 lib Winmm lib comctl32 lib   obj  SUBSYSTEM CONSOLE  MACHINE x86  you have to del   obj before  to avoid confusing linker with both 64 and 32 bit objects left over from prior compilations

User · Answer

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

User · Answer

I was using CMake  amp  then added a win32 configuration  The property page showed x86 but actually when opening the vcxproj file in a text editor it was x64  Manually changing to x86 solved this

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

In addition to C Johnson list I would add the following point   Check in Visual Studio  Project Properties -  Configuration Properties -  Linker -  Command line    Additional Options  should NOT contain  machine X86  I have such key  generated by CMake output  CMake generated x86 project  then I added x64 platform via Configuration Manager in Visual Studio 2010 - everything was created fine for the new platform except that the linker command line  specified  machine X86 separately

User · Answer

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

User · Answer

I wrote a blog entry about this  as I encountered this maddening problem  and finally yanked my system back into working order   These are the things to check  in this order    Check your properties options in your linker settings at  Properties   Configuration Properties   Linker   Advanced   Target Machine  Select MachineX64 if you are targeting a 64 bit build  or MachineX86 if you are making a 32 bit build  Select Build   Configuration Manager from the main menu in visual studio  Make sure your project has the correct platform specified  It is possible for the IDE to be set to build x64 but an individual project in the solution can be set to target win32  So yeah  visual studio leaves a lot of rope to hang yourself  but that s life  Check your library files that they really are of the type of platform are targeting  This can be used by using dumpbin exe which is in your visual studio VC bin directory  use the -headers option to dump all your functions  Look for the machine entry for each function  it should include x64 if it s a 64 bit build  In visual studio  select Tools   Options from the main menu  select Projects and Solutions   VC   Directories  Select x64 from the Platform dropdown  Make sure that the first entry is    VCInstallDir  bin x86 amd64 followed by   VCInstallDir  bin    Once I did step 4 everything worked again for me  The thing was I was encountering this problem on all my projects where I wanted to compile towards a 64 bit target

User · Answer

All project settings seemed perfect  but I still got the error  Looking into the  vcxproj file and searching for  x86  revealed the problem    lt Lib gt     lt AdditionalOptions gt   machine X86   AdditionalOptions  lt  AdditionalOptions gt   lt  Lib gt    A quick search replace for all occurrances  ten individual file settings  fixed the problem

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

project property - CUDA Runtime API - GPU - NVCC Compilation Type    Set the 64 bit compile option -m64 -cubin  The hint is at compile log  Like this   nvcc exe        -machine 32 -ccbin         That  -machine 32  is problem   First set 64bit compile option  next re setting hybrid compile option  Then u can see the succeed

User · Answer

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

User · Answer

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

User · Answer

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

[visual-c++] fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'

Examples related to visual-c++

Examples related to visual-c++-2008