Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index


Hi,

On 27.07.2020 19:17, anshu khare wrote:

So recently I built Libreoffice in Microsoft Visual Studio on Windows.

LibreOffice is build in Cygwin terminal on Windows; Visual Studio IDE
cannot do a full build (although can do a limited rebuild after initial
full build had been completed).


I want to know if soffice.bin is the console window for Libreoffice.sln
project.

Since version 6.3, soffice.bin process is a console process, and it is
attached to the debugging console window created by Visual Studio when
you start it from the IDE in IDE integration scenatio, if that's what
you are asking.


If not, then please tell me where to find the console window to generate
the output of a simple printf statement.

It all lacks the background, why are you asking? Obviously the first
thing to do would be to add some printf somewhere, make sure it gets
executed, and see if it appears on the console. But you omit this
information, so I can only guess that you have tried that (a patch of
your attempted changes would be helpful, or better a gerrit change), and
somehow failed ... and that's why you ask, right?

SAL_WARN/INFO/etc could be also useful; or using Visual Studio
debugger's breakpoints properties allowing you to make the breakpoint to
output something to IDE output window and continue (thus eliminating a
need to change source code, build, then test).

-- 
Best regards,
Mike Kaganski

Attachment: pEpkey.asc
Description: application/pgp-keys


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.