[gdal-dev] /MD vs /MDd for DEBUG MSVC builds

Mateusz Loskot mateusz at loskot.net
Wed Sep 27 15:20:34 PDT 2017


On 28 Sep 2017 00:10, "Jeff McKenna" <jmckenna at gatewaygeomatics.com> wrote:

On 2017-09-27 4:52 PM, Mateusz Loskot wrote:

> On 27 September 2017 at 21:38, Even Rouault <even.rouault at spatialys.com>
> wrote:
>
>>
>> Once again someone raised an issue about the MSVC runtime we use for
>> DEBUG=1
>> builds: https://trac.osgeo.org/gdal/ticket/7059
>>
>> [...]
>> Personnaly I believe I've never used a Windows build, so I'm mostly
>> indifferent
>>
>> Any opinion about using the debug MSVC runtime (/MDd) for DEBUG=1 builds
>> instead of the current release runtime (/MD) ?
>>
>
> Even,
>
> Yesterday, I started thinking about adding an extra build configuration to
> NMAKE
> makefile, controlled via command line defines, to enable such proper/full
> debug
> build for Windows.
>
> IMO, debug builds w/o /MDd are somewhat unexpected or exotic.
> As one of Windows users and developers, I'd vote for the default
> MSVC configuration for debug builds of GDAL.
>
> This would also help a bit with binary packages for Visual C++,
> currently, it requires nmake.opt patching.
> https://github.com/Microsoft/vcpkg/pull/1879
>
> Best regards,
>
>
To clarify: Mateusz you mean that debug builds should be changed to /MDd,
correct?  I somehow read your response as you also want to change the
default build in nmake to be the debug build.  Or, maybe my brain is tired
ha :)  -jeff



Jeff, yes that is what I was trying to say,  to change the debug defaults
only.

Perhaps I shouldn't paste the link to vcpkg as the flags patched there are
different, not relevant here.

However, one may want to also package and offer debug binaries for MSVC
like Python 3.5 or 3.6+, and /MDd would definitely be a must as that is the
MSVC way.

Mat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170928/a0465b72/attachment.html>


More information about the gdal-dev mailing list