Re: 'make check' with Windows/MSVC build?

Fridrich Strba <fridrich.strba -AT- graduateinstitute.ch>
Wed, 11 Apr 2012 02:58:00 +0200

Hello,

On 10/04/12 20:02, Tor Lillqvist wrote:

Presumably not. The way I iterate edit-compile-test on Windows (when I
do it, which is not often lately) is to have a normal installation (in
a virtual machine), i.e. from an installer, and then manually replace
the DLL(s) I am debugging... and replace again after edit/compile...

Exactly the same proceeding here, and launching libreoffice and then toattach the debugger to soffice.bin is the most common way to debug.

F.

Context

'make check' with Windows/MSVC build? · Lubos Lunak
- Re: 'make check' with Windows/MSVC build? · Michael Stahl
  - Re: 'make check' with Windows/MSVC build? · Tor Lillqvist
    - Re: 'make check' with Windows/MSVC build? · Fridrich Strba
  - Re: 'make check' with Windows/MSVC build? · Stephan Bergmann
    - Re: 'make check' with Windows/MSVC build? · Noel Grandin
      - Windows build · Jan Holesovsky
    - Re: 'make check' with Windows/MSVC build? · Lubos Lunak
      - Re: 'make check' with Windows/MSVC build? · Caolán McNamara
        
        Re: 'make check' with Windows/MSVC build? · Stephan Bergmann
        
        Re: 'make check' with Windows/MSVC build? · Michael Meeks
        
        Re: 'make check' with Windows/MSVC build? · Stephan Bergmann
        Re: 'make check' with Windows/MSVC build? · Michael Meeks
        Re: 'make check' with Windows/MSVC build? · Caolán McNamara

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.