Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Received-SPF: pass (nike.apache.org: domain of orwittmann@googlemail.com
 designates 209.85.214.47 as permitted sender)
Message-ID: <5097EF8F.20309@googlemail.com>
Date: Mon, 05 Nov 2012 17:55:43 +0100
From: Oliver-Rainer Wittmann <orwittmann@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org>
Subject: Re: Looking for guide to debug with MS Visual Studio Express
References: <50910D1F.90608@t-online.de> <50911C46.4030007@googlemail.com>
 <5092A1F6.6060305@googlemail.com> <5096BC28.1060208@t-online.de>
In-Reply-To: <5096BC28.1060208@t-online.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,


On 04.11.2012 20:04, Regina Henschel wrote:
> Hi Andre,
>
> Andre Fischer schrieb:
>> On 31.10.2012 13:40, Oliver-Rainer Wittmann wrote:
>>> Hi,
>>>
>>> On 31.10.2012 12:35, Regina Henschel wrote:
>>>> Hi all,
>>>>
>>>> I read that debugging with MS Visual Studio works well. Is there
>>>> somewhere a
>>>> guide for dummies how to do it?
>>>>
>>>
>>> The following steps should give you a start:
>>> - Have your AOO build installed on the system.
>>> - Build the module of interest with debug information
>>> - Copy the resulting DLLs and PDB files of the module into the
>>> corresponding directory of the installation.
>>> -- for "gbuild" modules like sw you find the DLLs and PDB files in
>>> /main/solver/350/wntmsci12/workdir/LinkTarget/Library/
>>> -- for "dmake" modules like sd you find the DLLs and PDB files in
>>> /main/[module]/wntmsci12/bin/
>>
>> I do it a little differently from here on because I am a lazy person who
>> wants to press just one key to start debugging:
>>
>> - Start Visual Studio
>>    The Express version is just fine.  I have been using it for most of
>> my debugging for years.
>>
>> - File->New Project
>>
>> - In the new dialog:
>>    - In left list "Installed Templates" choose Visual C++->General
>>    - In center list choose "Empty Project"
>>    - In field near the bottom "Location" enter a path where the solution
>> files will be stored.
>>    - In the field above that, "Name", enter the name of the new project,
>> eg "aoo35"
>>    - Click OK to close dialog
>>
>> - Now the main window shows a new view.
>> - In the "Solution Explorer" on the left side you will now see an entry
>> in bold typeface named "aoo35".
>> - I usually delete the entries below it "Header Files", "Resource
>> Files", "Source Files".  These are used only when Visual Studio is used
>> for editing. But that is just for my convenience
>> - Right click on the "aoo35" entry.
>> - Click "Properties"
>>
>> - In the "aoo35 Property Pages" dialog:
>>    - Select "Configuration Properties->Debugging" in the left box.
>>    - In the center box change values for "Command" to
>>      "<office-installation-path>/OpenOffice.org 3/program/soffice.bin"
>>      The .bin is important, do not use .exe
>>    - Set value for "Environment" to
>>      "PATH=<office-installation-path>/OpenOffice.org 3/URE/bin"
>>    - [optional] Set value of "Command Arguments" to <filename> to load a
>> file when AOO starts or to eg "-impress" to start AOO with the Impress
>> application.
>>    - Click OK to close dialog
>>
>>
>> Now you are all set
>> Just press "F5" to start Apache OpenOffice.
>
> I have followed your guide. I find all items you have mentioned :)
> I now get some informations from MSVC. I have copied them to the issue
> https://issues.apache.org/ooo/show_bug.cgi?id=121139
> Any tips what I can do in addition to get useful informations?
>

I saw first your comment on the issue.
Please have a look at my reply in the issue.

Best regards, Oliver.