On 22/11/11 15:51, Tor Lillqvist wrote:
if the MSVC debug stuff is indeed too difficult, then just comment it
out, put in a comment that says FIXME, and re-enable the
--enable-dbgutil stuff, that way windows devs at last get some
assertions and internal consistency checks.
But you can't build it with --enable-dbgutil ... configure.in says:
# Compiling with MSVC using --enable-dbgutil (i.e. using the
# debugging runtime, and defining _DEBUG when compiling) just
# causes too many compilation errors. After having spent some
# months slowly fixing them one by one, having reached sw, I give
# up. Feel free to try again.
--tml
hi Tor,
sorry, apparently i have difficulties expressing myself clearly:
what i meant was that, given that (if i understand you correctly)
--enable-dbgutil not working on windows is caused not by any code in LO
but only by use of the MSVC debug runtime, then --enable-dbgutil should
just not enable the MSVC debug runtime on windows.
Context
- Re: [Libreoffice] Assertions and Logging (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.