microsoft / microsoft/DirectX-Graphics-Samples
D3D12RaytracingMiniEngineSample: unresolved external symbol __std_init_once_link_alternate_names_and_abort
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.8k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
When building D3D12RaytracingMiniEngineSample, I am getting
Core.lib(FileUtility.obj) : error LNK2019: unresolved external symbol __std_init_once_link_alternate_names_and_abort referenced in function "public: __cdecl std::_Init_once_completer::~_Init_once_completer(void)" (??1_Init_once_completer@std@@QEAA@XZ)
Using VS 2022 Version 17.9.6, tried with both 10.0.20348.0 and 10.0.19041.0 Windows SDK and Visual Studio 2019 (v142) Toolset
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the D3D12RaytracingMiniEngineSample build with Visual Studio 2022 17.9.6, the listed Windows SDK versions, and the Visual Studio 2019 (v142) toolset. Investigate the reported linker failure in Core.lib(FileUtility.obj); done means the sample builds without the unresolved __std_init_once_link_alternate_names_and_abort error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100