@rhaschke Sorry I wasn't able to find time to iterate on #99 and here is a version based on your change to make it work on Windows build.

@rhaschke Hi, it turned out on Windows build, assimp is discovered by using CMake config file so the pkg-config code path is not really getting exercised. Anyway, I am pushing a new change which should accommodate both. Let me know what you think.

Ok, if Windows detects assimp via a cmake config, what is the actual problem. Shouldn't this work out of the box?

On Windows build, we are using assimp v4.1 (the same like Ubuntu bionic using) and just as many libraries they are producing the CMake config intead of pkg-config for Windows build. And from assimp, its CMake Config is like this: https://github.com/assimp/assimp/blob/v4.1.0/assimp-config.cmake.in#L42-L51

As you can see, the ${ASSIMP_LIBRARIES} is defined to be just as the library name like assimp-vc140-mt and the library directory is defined in another CMake variable ${ASSIMP_LIBRARY_DIRS}. However, ${ASSIMP_LIBRARY_DIRS} was not in the target's link directory, so duing linking stage, it cannot find where the library actually is.

@rhaschke Thanks. The comments are added.