MegaGlest Forum

MegaGlest => Bug reports => Closed bug reports => Topic started by: Omega on 19 July 2014, 14:08:32

Title: [lack info] [31def0dc1a] Preprocessor inconsistencies when compiling MSVS debug
Post by: Omega on 19 July 2014, 14:08:32
ExceptionHandler::handle(LPEXCEPTION_POINTERS) in main.cpp references stackdumper(), which is only visible if _DEBUG is not defined. As a result, there's compile time errors when compiling in debug mode.

This is on branch develop (I presume that's the active development branch; couldn't find any info about how the project uses branches) as of rev 31def0dc1a. This is applicable to MSVS 2010 (should affect all MSVS versions).

EDIT: Actually, it turns out that the code inside the #IFDEFs doesn't compile, anyway. It uses non-existent variables. It's not clear why.
Title: Re: [31def0dc1a] Preprocessor inconsistencies when compiling MSVS debug
Post by: filux on 19 July 2014, 16:30:56
...I presume that's the active development branch; couldn't find any info about how the project uses branches...
Very official and common way, go there (http://nvie.com/posts/a-successful-git-branching-model/) and read "The main branches" paragraph first. I haven't idea why it isn't written on the beginning  ::).
Title: Re: [31def0dc1a] Preprocessor inconsistencies when compiling MSVS debug
Post by: Omega on 19 July 2014, 17:23:01
...I presume that's the active development branch; couldn't find any info about how the project uses branches...
Very official and common way, go there (http://nvie.com/posts/a-successful-git-branching-model/) and read "The main branches" paragraph first. I haven't idea why it isn't written on the beginning  ::).
Oh, I know, I use Git all the time. I'm a CS student and currently employed at my university to bring in heavy refactoring to this Java simulation system that was programmed by C programmers.

I mentioned the branches because I've seen a lot of projects use them in crazy ways (the simulation system that I mentioned was originally developed for months by some very smart people without version control).