Re: [PATCH 07/10] cmake (Windows): complain when encountering an unknown compiler
- From
Sibi Siddharthan <sibisiddharthan.github@gmail.com>
- Date
- Sep 25, 2020, 17:29 UTC
- Message-ID
- <CAKiG+9XqJ92rjVczBG9ByVK_KRfJeToO0pFb3RhFpom2ChFE-g@mail.gmail.com>
- In-Reply-To
- <dddfa3a9b48fa24466a20952d485be1a7f515019.1601044118.git.gitgitgadget@gmail.com>
On Fri, Sep 25, 2020 at 7:58 PM Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
Show 14 quoted lines
> > From: Johannes Schindelin <johannes.schindelin@gmx.de> > > We have some custom handling regarding the link options, which are > specific to each compiler. > > Therefore: let's not just continue without setting the link options when > configuring for a currently unhandled compiler, but error out. > > Note: for some reason, the `invalidcontinue.obj` trick seems not to work > in this developer's hands when building Git in Debug mode: the assertion > dialog that is supposed to be suppressed still pops up, complaining > about the `entry` variable being uninitialized when it is used in > `config.c`'s line 1961.
Does this happen when running Git under the Visual Studio debugger? If so this might help _CrtSetReportMode(_CRT_ASSERT,0);
After digging a bit more I found out that _CRTDBG_MODE_DEBUG is environment sensitive. It depends on how the debugger handles DbgPrintEx().
Thank You, Sibi Siddharthan