CMake error when libassimp-dev is installed on Ubuntu 20.04

[Raymond de Vries]

Hi,

Now that VSG and the companion projects (except vsgSDL which is not
public?) are building fine, I tried to build vsgXchange after I
installed libassimp-dev on Ubuntu 20.04.

I get the following error on cmake. It seems like I can 'make' but then
I get strange results, e.g. compiling GDAL.cpp ?!

-- Configuring done
CMake Error in src/CMakeLists.txt:
  Imported target "assimp::assimp" includes non-existent path

    "/usr/lib/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/CMakeLists.txt:
  Imported target "assimp::assimp" includes non-existent path

    "/usr/lib/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



-- Generating done


Cheers, thanks,
Raymond

Btw in the mean time I will try more...

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

[ptrfun (Stephen)]

Hi, 
Just a heads up about vsgSDL (my project). It's still in a very early state!
There's no make/cmake files yet, no real example, still no proper error handling, and other things. I planned if I can to this weekend publish some very important updates. I started all of the code for this library as part of my game engine project, so those features will naturally be added along with my own project, but I need to make it independent of my project of course. 

Some of the updates will include:
1. CMake/Make files and config, info, tutorial (short)
2. A real example or maybe two
3. Better error handling
4. Some decisions about handling continuous keyboard inputs for single-hit ones, and how the programmer can control vsgSDL
5. Some very important updates and decisions about Vulkan SDL loader
6. Other: Header guards maybe, some Visual Studio specific header stuff like pragma once 
And more.. 
There's a thread I made a while ago "vsgSDL first release" and I'll probably post and update there once I commit to github. 

As far as the other stuff goes, I think those problems are maybe just a matter of path/environment variables
Good luck

[Robert Osfield]

Hi Raymond,

It's been a while since I tried to install assimp from the Ubunutu repositories.  When I last attempted this the version was too old for the vsgXchange to properly pick up on.  I don't recall the exact issue, but have a vague recollection that some older versions of Assimp have broken cmake support, but I may be thinking of another library.

Could you post the exactly command line you used to install ffmpeg and build vsgXchange, I could have a bash at reproducing these steps and then I can see what happens first hand.

As older Assimp versions can be a bit broken for vsgXchange's needs I pull down Assimp from github and build it myself.

Cheers,

Robert.