Closed nyue closed 9 months ago
Hey @nyue this is usually related to explicit template instatiation. We should probably turn this off on Windows. Try configuring with -D USE_EXPLICIT_INSTANTIATION=OFF
That works for me.
I have a new issue with the Windows build
The Ninja build encountered multiple build rules but only if I build the AX stuff.
Ah this looks to be a bug in our CMake, both the shared and static builds of AX are producing the same library name.
You can either disable the static/shared build with OPENVDB_AX_SHARED=ON|OFF
or OPENVDB_AX_STATIC=ON|OFF
or add:
if(WIN32)
set_target_properties(openvdb_ax_static PROPERTIES PREFIX "lib")
endif()
to somewhere in openvdb_ax/CMakeLists.txt:
I'll make the latter change to master
Environment
Operating System: (e.g. Windows 2019, macOS-10.15, Linux CentOS 7.4)
Windows 10
Version / Commit SHA: (e.g VDB 7.2, SHA: 1a2b3c4d5e...)
OpenVDB 11.0.0
CMake Version: (e.g. 3.18)
3.25
Compiler: (e.g. gcc 10, msvc 2019)
VS 2019
Describe the problem
Linker error
vdb_print is not critical to me at this point so I can remove it from the build but reporting this anyway.