Advertisement

Building Assimp in Visual Studio

Started by July 04, 2014 10:17 PM
3 comments, last by Kimmi 10 years, 7 months ago

Hi,

Looking at the Assimp website it suggests that Assimp builds for several versions of Visual Studio upto and including VS2012 (VS11), however when I download the full install I don't see any solution files or instructions on how to build it.

Has anyone built it from the Visual Studio IDE, and if so please can you share your instructions on how you did it?

Thanks in advance

Ben

Since nobody has replied yet, I'll attempt to answer this for you (however I do not use either VS or assimp, but I did download the latter)...

There is a binary download for Assimp, have you tried using that, since you won't need to build it? Otherwise, use cmake since according to the install file it is the preferable method for building assimp. I couldn't read the full installation as I don't have doxygen installed here.

Advertisement

Thanks LennyLen

Yes I initially downloaded the binary install but it only includes the release lib files and not the debug versions. I'm not sure if this is an issue though.

I eventually found the build instructions (Not in the most obvious place I have to say), and so I'll try using CMake later (HAving never used it before).

Thanks for your help

Ben

Just for future reference if anyone else has the same question.... I downloaded CMake and followed the instructions here:

http://assimp.sourceforge.net/lib_html/cmake_build.html

And to my surprise it actually worked. By worked I mean that it generates Solution\Project files for the versions of Visual Studio you select (As well as different target platforms, such as x86 or x64) and they build just fine.

The solution\project files it generates are a good starting point, and it builds, but they're a bit of a mess as they use absolute full paths instead of solution relative directories etc, but it's only a minute of 2's work to tidy that up.

Thanks

Ben

Hi,

the cmake-build environment will be testst for each commit to github. We are only maintain this way to build.

Kimmi

A complicate solution may indicate a not understood problem.


[twitter]KimKulling[/twitter]

This topic is closed to new replies.

Advertisement