I posted the following on 6/18/18, but failed to set the reply-to to
include the cmake list server.
Thanks for replying.
After I posted to this list I wondered if it was an issue with MinGW. I
hadn't had any issues with MinGW before but compiled a quick 'hello
world' to check. Worked fine, no
I don't know what the turn-around time is, but you and others might
consider submitting the exe as a false positive:
https://www.microsoft.com/en-us/wdsi/filesubmission
(If you are blocked by this issue, try adding an exclusion rule:
https://support.microsoft.com/en-au/help/4028485/windows-10-add
I'm wondering if anyone has followed up on the issue regarding cmake triggering
Windows Defender using the MinGW compiler. It's a problem that I'm running
into as well.
Please be advised that this email may contain confidential information. If you
are not the i
On 06/14/2018 04:43 PM, Steve wrote:
> When I run '/cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release ..'
> Windows Defender triggers and reports: Trojan:Win32/Fuerboos.C!cl on file:
> D:\DDS-master\AMM_Modules\build\CMakeFiles\3.11.3\CompilerIdC\a.exe
Strange. That `a.exe` is an executable c
Windows 10, Windows and Defender updates current.
CMake version 3.11.3
I'm preparing build environment for AMM (Advanced Modular Manikin)
https://github.com/AdvancedModularManikin/DDS/AMM_Modules
My tool chain is MinGW 6.3.0
I followed the build instructions up to cmake and changed /"Unix
M
