I am writing a setup application for an extension on Windows. I want to
run unopkg.com from within my setup application but I seem unable to
read any output from it in case it fails. My setup application is unable
to get any output from the normal stdout and stderr pipes when doing e.g.
unopkg.com blabla
When running the above command interactively in a command prompt I do
get an error message back. However, when running it interactively and
trying to redirect e.g. stdout by
unopkg.com blabla > c:\temp\unopkg_log.txt
the result is nothing at all - neither on screen nor in
c:\temp\unipkg_log.txt (zero bytes).
I also tried the --log-file option but that does not redirect the error
messages so I cannot detect success or failure that way.
Is this something that should be filed as a bug or is there some secret
workaround ?
Observed on Windows XP with OpenOffice.org 3.1.0 (build 9399) and also
DEV300_m50.
Kind regards
-- Jan Holst Jensen
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
