Not many of us use it,
True.
However, that doesn't mean you can't use Visual Studio for debugging, it is very simple to
just run VS and start a program and debug from it, and it will load the correct source files, etc.
In more detail, what works fine is: Start the LibreOffice you just
built (presumably with debugging information --enable-debug) by
running instdir/program/soffice.exe. Start Visual Studio, but don't
open or create any project or solution. (It makes no difference
whether you start LibreOffice or Visual Studio first.)
Then attach the soffice.bin (not soffice.exe) process in Visual
Studio. soffice.bin is the actual LibreOffice process. Then open the
source file(s) you want to debug in Visual Studio and set one or
several breakpoints. Then do whatever is needed in LibreOffice to
cause the breakpoint to be reached. Then debug.
Obviously, this way, attaching to an already running LibreOffice
process, you won't be able to debug the start-up code in LibreOffice.
But that is seldom what one would want to debug anyway.
I would really like to be able to use the comfort of Visual Studio to
browse around the source code
I am not sure if the Visual Studio "integration" even if it worked as
advertised would match your expectations. But I might be too
pessimistic. Maybe somebody who actually has used (or even worked on)
the integration can respond.
--tml
Context
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.