This is what I do. Other people might have different style of working. The instructions you quote seem to miss this point (or maybe you just didn't quote it, but I will mention it anyway):
0) source the winenv.set.sh file in the top-level build directory. I.e. cd there and give the command: . ./winenv.set.sh in your Bourne-style shell in Cygwin. You must do this before "build debug=true" as the "build" command is an alias defined in that winenv.set.sh file. > --------"copy the built libraries": What do I need to copy? The DLL files in wntmsci12.pro/bin that were rebult by your build debug=true command. Just check the timestamps. > --------"into your OOo installation": Which directory? Well, you need to install the OOo you just had built on the machine where you are going to run it for debugging. (This need not necessarily be the same machine as where you did the build and/or where you are going to run the Visual Studio debugger, you can also use remote debugging.) Depending on what module you built with debug=true, the DLLs that got built correspond to those installed in one of three locations. As I myself use an ooo-build -based build, I don't recall exactly the pathnames in an upstream build, but look for two folders like "OpenOffice.org" and "OpenOffice.org 3", if I recall correctly, under "Program Files" (well, typically, unless you specifically chose another location). In them you should find subfolders "program", "Basis\program" and "URE\bin". Copy the freshly built DLLs on top of those that the installer had installed. Pay attention that that you copy them in the right folder. For most stuff, it will be the first, just "program", but some more low-level ones are in the two others. > ---------"start the debugger with soffice.bin": How should I do it ? I find > soffice.bin under several directories such as 'desktop\wntmsci12.pro\bin'; > 'solver\300\wntmsci12.pro\bin'; > 'instsetoo_native\wntmsci12.pro\OpenOffice\msi\patchsoname_file\en-US\00'. This means the soffice.bin that got installed by the installer, in "program". Don't try to run OOo from the build tree. Unless you specifically need to debug the startup sequences, I think it's easiest to just start OOo from the Start Menu, by double-clicking on a document associated with it, etc. Then start Visual Studio and attach to the soffice.bin process, open one of the source files that contain the code you want to debug, set breakpoints, and do whatever is needed in OOo to make it hit that breakpoint. --tml --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
