Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
error: unresolved external <various stdlib/stdio functions>
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
1>entry.obj : error LNK2001: unresolved external symbol exit
1>entry.obj : error LNK2001: unresolved external symbol ftell
1>entry.obj : error LNK2001: unresolved external symbol fopen
1>entry.obj : error LNK2001: unresolved external symbol __acrt_iob_func
1>entry.obj : error LNK2001: unresolved external symbol fclose
1>entry.obj : error LNK2001: unresolved external symbol fseek
1>entry.obj : error LNK2001: unresolved external symbol __stdio_common_vfprintf
1>entry.obj : error LNK2001: unresolved external symbol qsort
1>entry.obj : error LNK2001: unresolved external symbol __stdio_common_vsprintf
1>entry.obj : error LNK2001: unresolved external symbol free
1>entry.obj : error LNK2001: unresolved external symbol fread
1>entry.obj : error LNK2001: unresolved external symbol _wassert
1>entry.obj : error LNK2001: unresolved external symbol malloc
note: this is only when i compile with visual studio rather than build.bat
Contributor guide
Research direction
Compare the Visual Studio compilation path with build.bat, starting with build.bat and the unresolved symbols reported for entry.obj. Reproduce the linker failure in Visual Studio and identify the build difference responsible for the missing stdlib/stdio symbols. Done means Visual Studio builds without these unresolved externals while the existing build.bat path remains working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100