MatX: [BUG] Visual studio fails to compile unit tests/examples

Describe the bug CMake generates a solution that fails to compile 11 of 20 projects on VS2022.

From #147 :

The problem is not that nvcc is being passed an incorrect flag, but rather that fvisibility is not valid on VS. We use the option -forward-unknown-to-host-compiler, so any unknown parameter (of which this is one), nvcc will automatically forward to VS.

To Reproduce Steps to reproduce the behavior:

cmake -DMATX_BUILD_TESTS=ON -DMATX_BUILD_BENCHMARKS=ON -DMATX_BUILD_EXAMPLES=ON -DMATX_BUILD_DOCS=OFF -DCMAKE_CUDA_ARCHITECTURES=52 -DCMAKE_BUILD_TYPE=Debug ..

Expected behavior Expect to successfully compile all unit tests & examples.

Code snippers output log attached.

System details (please complete the following information):

  • Windows 10 Pro
  • CMake 3.22.1
  • VS2022 (MSVC 19.30.30706.0)
  • CUDA 11.6
  • pybind11 2.6.2

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 5
  • Comments: 32

Most upvoted comments

hi @sahuang, I was able to compile and run on wsl 2 with cuda installed.

@tbensonatl Our typical scenario is: input signal bandwidth : 72 MHz channel count 1000,with diffrent bandwidth (10Khz~20MHz) Channels may not necessarily be equally spaced this is a ddc Service that can meet the diverse ddc needs of users