Files
ANSCORE/tests/CMakeLists.txt
nghianguyenandClaude Opus 5 6abe6d6694 fix(build): configure without CUDA instead of failing at generate
tests/CMakeLists.txt added every test directory unconditionally, so a
machine with no CUDA toolkit — every macOS one — died at generate time on
"links to CUDA::cudart but the target was not found", taking the
cross-platform targets down with it.

Gate each test the way its subject is already gated: the five that need
the toolkit behind ANSCORE_HAS_CUDA, the ANSIO one behind WIN32, and the
ANSONVIF one behind both. ANSONVIF itself uses no CUDA; its test names
CUDA::cudart and CUDA::nvjpeg only because it drives capture through
ANSCV and was copied from the ANSCV test.

Two non-test targets had the same problem. ANSCV genuinely needs the
toolkit — ANSGpuFrameOps.h includes <cuda_runtime.h> unconditionally and
calls cudaMemcpy2D/cudaMallocPitch — so it moves into the existing CUDA
block beside the engine modules. ANSLibsLoader binds cudart at runtime
and ships its own stubs, but still compiles against the runtime header
for the types and links CUDA::cudart_static, so it is gated too.

Also call enable_testing(), which the project never did: without it the
add_test() under tests/ reached nothing and ctest found no tests. Plain
enable_testing(), not include(CTest), to avoid its extra targets.

A CUDA machine is unchanged: every gate holds there, ANSCV keeps its
place in the subdirectory order, and the only new output is
CTestTestfile.cmake.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-12 23:38:57 +10:00

36 lines
1.3 KiB
CMake

# ANSCORE Unit Tests
#
# A test is gated exactly like the code it exercises (see the top-level
# CMakeLists): tests for the CUDA-only modules, or that name CUDA::* targets
# themselves, are added only when ANSCORE_HAS_CUDA; tests for the Windows-only
# integrations only on WIN32. Without these gates a non-CUDA configure (macOS,
# any machine with no toolkit) fails at generate time on "links to CUDA::cudart
# but the target was not found", which blocks the cross-platform targets too.
# Cross-platform
add_subdirectory(ANSUtilities-UnitTest)
add_subdirectory(ANSRabbitMQ-UnitTest)
add_subdirectory(ANSLS-UnitTest)
add_subdirectory(ANSModelPackage-UnitTest)
add_subdirectory(ANSODTRE-UnitTest)
# Windows-only — integrations/ANSIO is built on WIN32 only
if(WIN32)
add_subdirectory(ANSIO-UnitTest)
endif()
# CUDA-only — modules/ANSCV, ANSODEngine, ANSOCR, ANSFR and ANSLPR
if(ANSCORE_HAS_CUDA)
add_subdirectory(ANSCV-UnitTest)
add_subdirectory(ANSODEngine-UnitTest)
add_subdirectory(ANSFR-UnitTest)
add_subdirectory(ANSLPR-UnitTest)
add_subdirectory(ANSOCR-UnitTest)
# integrations/ANSONVIF itself uses no CUDA — the test does, because it
# drives capture through ANSCV. Hence both gates.
if(WIN32)
add_subdirectory(ANSONVIF-UnitTest)
endif()
endif()