Re: [dev] Debug output

2010-10-26 Thread Oliver Brinzing
Hi,

 Windows suppresses stdio in GUI programs. As a workaround you may copy
 solver/wntmsci*/bin/guistdio.com to your OOo installation's program
 directory, name it soffice.com and start soffice.com instead of
 soffice.exe

why not adding the guistdio.com to oo dev builds ?

Regards

Oliver
-- 

GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45



signature.asc
Description: OpenPGP digital signature


Re: [dev] Debug output

2010-10-26 Thread Tor Lillqvist
 Windows suppresses stdio in GUI programs. 

You can change that after having built soffice.bin (and soffice.exe):

editbin /subsystem:console \path\to\executable

then you will get a console window always opened for the executable in 
question, and any output written to stdout will be visible there.

(I don't remember now if editbin is confused by soffice.bin not having an .exe 
suffix; you might need to temporarily rename if to foo.exe before running 
editbin on it, and then back.)

--tml



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] Debug output

2010-10-25 Thread Eike Rathke
Hi Jan,

On Sunday, 2010-10-24 14:52:28 +0430, Jan private wrote:

 my C++ extension writes debug information to std::cout. When running
 openoffice.rg from a Linux terminal this works fine. But when I run
 soffice.exe from a Windows command prompt, there is no output. Is there
 any simple way to get debugging output in Windows?

Windows suppresses stdio in GUI programs. As a workaround you may copy
solver/wntmsci*/bin/guistdio.com to your OOo installation's program
directory, name it soffice.com and start soffice.com instead of
soffice.exe

  Eike

-- 
 OOo Calc core developer. Number formatter stricken i18n transpositionizer.
 Signature key 0x87F8D412 : 2F58 5236 DB02 F335 8304  7D6C 65C9 F9B5 87F8 D412
 OpenOffice.org Engineering at Oracle: http://blogs.sun.com/GullFOSS
 --
 Please don't send mail to the old e...@sun.com account that I used for mailing
 lists, it phased out. Use eike.rat...@oracle.com instead. Thanks.


pgpUoF9UOv1aY.pgp
Description: PGP signature


[dev] Debug output

2010-10-24 Thread Jan private
Hello,

my C++ extension writes debug information to std::cout. When running
openoffice.rg from a Linux terminal this works fine. But when I run
soffice.exe from a Windows command prompt, there is no output. Is there
any simple way to get debugging output in Windows?

Thanks,
Jan



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] Debug output

2010-10-24 Thread kushal likhi
hi,
.
use Visual C++ debugger.
its the best debugger.
OR , as an alternate you can save a log file along the process. i have done
a Simple logWriter implementation, see the files logWriter.cxx/logWriter.hxx
in the link below. Its very easy to use, you can copy these files and use
them in your code. they will buffer the log string unless save path is
defined, as soon as save path is defined it will write the previous log
string and real time logging in that file will start.
you will also find examples how logging is done in the code htmlex.cxx/hxx.
http://wiki.services.openoffice.org/wiki/OpenOffice.org_Internship/Projects/2010/Customizable_html_export_for_Impress
.
but still Visual C++ debugger is the best. :)
.
regards
kushal
.
On Sun, Oct 24, 2010 at 3:52 PM, Jan private jrheinlaen...@gmx.de wrote:

 Hello,

 my C++ extension writes debug information to std::cout. When running
 openoffice.rg from a Linux terminal this works fine. But when I run
 soffice.exe from a Windows command prompt, there is no output. Is there
 any simple way to get debugging output in Windows?

 Thanks,
Jan



 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
 For additional commands, e-mail: dev-h...@openoffice.org