Assimp: Assimp x64, how can i get?

Created on 16 Jun 2015 · 14Comments · Source: assimp/assimp

Hey, I enjoy your library , but I did not get to build x64 version always get the error module machine type 'x64' conflicts with target machine type 'X86' assimp. All settings in VisualStudio checked , all right , but why is not built . Excuse me , if not to write the question .

Source

Maslik78

👍1

Most helpful comment

When you click Configure for the first time in a new build destination it will present you with a list of 'generators' (such as Visual Studio 14 2015). Scroll down a bit and select the Win64 version.

Apparently CMake doesn't support generating project files with both platforms in it so I just ran CMake twice to two separate binary folders.

IanNorris on 12 Aug 2016

👍4 ❤1

All 14 comments

I guess x64 ( lowercase ) against X64 (uppercase ).

kimkulling on 17 Jun 2015

I'm having same issue as well.

anshzinc on 18 Jun 2015

Sounds bad, I will check!

kimkulling on 20 Jun 2015

Have you generated your solution with CMake? And sorry, I didn't saw that you have x86 against x64. Visual Studio needs to have x64 libs from Asset Importer Lib as well. As far as I know we don't have a pre-build package for that configuraton so you should do this on your own.

kimkulling on 22 Jun 2015

Any updates?

kimkulling on 25 Jun 2015

You can generate the x86 project using Cmake. Then go in configuration manager in Visual Studio and make new configuration, in option you can copy it using x86. Change output name and intermediate paths in properties of the project. Same goes you have to change the machine target from x86 to x64. It should do the trick.

sahilagnihotri on 18 Sep 2015

I have the same problem.
I replaced all appropriate places with "$(Platform)\$(Configuration)" and tracked down any x86.

Hiwever, building the project assimp still fails to link.
Is there som typical specific I am missing?

Chrjstoph on 4 Mar 2016

I checked the assimp.vcxproj file and found under

the

/machine:X86 %(AdditionalOptions)

tag.

Might that be the culprit?
Deleting the tag introduces other errors

Chrjstoph on 4 Mar 2016

No this actually solved it!

this guy had the same problem:
http://stackoverflow.com/questions/2849517/linking-problem-fatal-error-lnk1112-module-machine-type-x64-conflicts-with-t

Chrjstoph on 4 Mar 2016

When you click Configure for the first time in a new build destination it will present you with a list of 'generators' (such as Visual Studio 14 2015). Scroll down a bit and select the Win64 version.

Apparently CMake doesn't support generating project files with both platforms in it so I just ran CMake twice to two separate binary folders.

IanNorris on 12 Aug 2016

👍4 ❤1

You can find a small doc here: http://kimkulling.de/?p=15

On Fri, Aug 12, 2016 at 1:15 AM, Ian Norris [email protected]
wrote:

When you click Configure for the first time in a new build destination it
will present you with a list of 'generators' (such as Visual Studio 14
2015). Scroll down a bit and select the Win64 version.

Apparently CMake doesn't support generating project files with both
platforms in it so I just ran CMake twice to two separate binary folders.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/assimp/assimp/issues/583#issuecomment-239321592, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACNy1EVFoVxoQg3KxrL82tuRu-z1D7Iiks5qe60JgaJpZM4FEKTg
.

kimkulling on 12 Aug 2016

Hi, after changing the dropdown to X64, you should change the following configuration (at least with visual studio)

Then, open assimp.vcxproj with a text editor and replace x86 to x64
And it should work

diegoalejandrogomez on 31 Jan 2017

If I changed the settings manually like how diegoalejandrogomez mentioned above. Visual Studio is not generating the .dll files. I instead changed the CMake configuration to Win64 while generating Visual Studio files. Visual Studio then outputs the .dll & .lib files upon building.