Use config-specific PTX output paths
When using a multi-config generator, these config-specific definitions make the Debug and Release PTX semantically different, but csgoptix_ptx still copies every config to the single ${PROJECT_BINARY_DIR}/ptx/CSGOptiX7.ptx and sysrap/config_path.h.in:4 makes runtime lookup use that shared directory. After building one config and then running a binary from another, the binary loads whichever PTX was copied last, so Release can still run non-PRODUCTION PTX or Debug can silently lose the DEBUG_* instrumentation. Please include the config in the PTX output/search path or otherwise keep the artifacts separate.
Originally posted by @chatgpt-codex-connector[bot] in #380 (comment)
When using a multi-config generator, these config-specific definitions make the Debug and Release PTX semantically different, but
csgoptix_ptxstill copies every config to the single${PROJECT_BINARY_DIR}/ptx/CSGOptiX7.ptxandsysrap/config_path.h.in:4makes runtime lookup use that shared directory. After building one config and then running a binary from another, the binary loads whichever PTX was copied last, so Release can still run non-PRODUCTIONPTX or Debug can silently lose theDEBUG_*instrumentation. Please include the config in the PTX output/search path or otherwise keep the artifacts separate.Originally posted by @chatgpt-codex-connector[bot] in #380 (comment)