Project compile helper
`cuda-doctor build`
build shields developers from hand-authoring the right flags for new hardware and from accidentally compiling against the wrong toolchain.
What build should abstract away
- Selecting the correct toolkit and compiler path.
- Choosing the right architecture target for the detected GPU.
- Avoiding stale defaults that miss support for new hardware generations.
- Failing early when the local machine cannot build for the requested workload.
Why it matters
The point of build is not to replace existing build systems. It is to reconcile them with the actual machine. For new NVIDIA hardware, the largest waste is often not a compiler crash, but a successful build that targeted the wrong architecture or toolkit.
Expected usage
cd my-cuda-project
cuda-doctor buildBuild with local reality
On newer GPUs, build should align flags and toolchain settings with the machine that will actually execute the binary.
Related docs
Execution
validate
Prove that device selection, memory transfer, kernel launch, and runtime behavior work on the local GPU.
Diagnose
doctor
Run a full environment diagnosis for the GPU, driver, toolkit, runtime, build chain, and validation risk.
Start here
Quickstart
Install cuda-doctor, diagnose the machine, repair what is compatible, then prove GPU execution works.