Build break in vmiterators

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Post Reply
lemming
Posts: 19
Joined: Sat Nov 10, 2018 11:29 pm

Build break in vmiterators

Post by lemming »

Commit SHA: 0d891b6289088b60c341880cb7419c7ade07a1d5

VS 2017, building x64 RelWithDebInfo

Error: LNK2019
Message: unresolved external symbol "public: int __cdecl sector_t::Index(void)const " (?Index@sector_t@@QEBAHXZ) referenced in function "class DSectorTagIterator * __cdecl Create<class DSectorTagIterator,int &,struct line_t * &>(int &,struct line_t * &)" (??$Create@VDSectorTagIterator@@AEAHAEAPEAUline_t@@@@YAPEAVDSectorTagIterator@@AEAHAEAPEAUline_t@@@Z)
Project: zdoom
File: C:\git\gzdoom\build\src\vmiterators.obj
Line: 1
lemming
Posts: 19
Joined: Sat Nov 10, 2018 11:29 pm

Re: Build break in vmiterators

Post by lemming »

Buildlog attached.

Edit: I suspect the break was probably caused by https://github.com/coelckers/gzdoom/com ... 3d69b67c9c. Commit hash 3b5ce4ecca5d12018bf129968b1bbbd2cf1bcda6, which immediately precedes that, builds fine on my machine.
Attachments
buildlog.txt
(2.61 KiB) Downloaded 17 times
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49073
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: Build break in vmiterators

Post by Graf Zahl »

This only happens on Release builds which is why I missed it.
Post Reply

Return to “Closed Bugs [GZDoom]”