Hi Stephan,
> What shell are you using, hombre? "VERBOSE=TRUE dmake" is ca. as many
> keystrokes as "dmake verbose=true" (not counting the little finger's
> duty on the caps key). ;)
Uhm. Learned something new today ;)
Ciao
Frank
--
- Frank Schönheit, Software Engineer frank.schoen
> you'recertainly quicker with "dmake verbose=true"
> than with "export VERBOSE=TRUE ; dmake ; export VERBOSE=".
However, "VERBOSE=TRUE dmake" is as quick;)
--tml
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For a
On 10/23/09 08:44, Frank Schoenheit, Sun Microsystems Germany wrote:
Then, if you really need that output for a given directory, you're
certainly quicker with "dmake verbose=true" than with "export
VERBOSE=TRUE ; dmake ; export VERBOSE=".
What shell are you using, hombre? "VERBOSE=TRUE dmake"
Hi Stephan,
> My gut feeling (admittedly) is that it is not too uncommon that some
> poor (inexperienced) soul pastes some stretch of its (default) build
> output into a mail to d...@ooo crying for help on why their build break,
> and the details of the executed command lines do give us clues t
Hi Stephan,
> (And having three ways to request something
> would be worse than having two ways, which already is worse than having
> only one way. So while we are at it, if you stick with an environment
> variable, what good is it to additionally have the dmake switch?)
Consistency, for one. S
On 10/22/09 15:12, Thorsten Behrens wrote:
I admit that you're likely one of those special cases where there
_will_ be build breakages caused by solenv & invocation details, at
least as long as you're working on the OOo layering; but won't you
agree that the majority of devs are unaffected by thi
Stephan Bergmann wrote:
> Yes, I know. A bit lame to not step in earlier. However, I had not
> been aware that you would make it the default to produce less
> information, so thought this would not really affect me and hence
> had kept my thoughts about those activities to myself...
>
Hi Stephan
Hi Stephan,
> Too much trouble. (Plus, I will definitely not globally set an
> environment variable "VERBOSE" to anything. Who knows what strange side
> effect that would have on completely unrelated programs. If you had at
> least named it "OOO_VERBOSE"...)
I think we can easily change thi
On 10/22/09 13:33, Frank Schoenheit, Sun Microsystems Germany wrote:
IMO, that should be reason to rather spend energy in improving the
precision of the output than in suppressing useful output.
I expected this earlier from you :)
Yes, I know. A bit lame to not step in earlier. However, I h
Hi Stephan,
> IMO, that should be reason to rather spend energy in improving the
> precision of the output than in suppressing useful output.
I expected this earlier from you :)
Since our definitions of "useful" differ in this context, I suggest you
set VERBOSE=TRUE in your login script, where
On 10/22/09 12:46, Frank Schoenheit, Sun Microsystems Germany wrote:
Hi Christian,
If you need to use some magic environment variable to see why the
build did broke, the default is wrong. My 0,02€.
I think so, too.
Sure. Unfortunately my experience is that with the parallel builds, and
the u
Hi Christian,
> The bots should use that - if not, complain at the admins of the
> corresponding bots.
Okay, will have a look on this when I next time have a build problem on
a bot.
> If you need to use some magic environment variable to see why the
> build did broke, the default is wrong. My 0,
Hi Frank, *,
On Thu, Oct 22, 2009 at 8:07 AM, Frank Schoenheit, Sun Microsystems
Germany wrote:
>
>> build --html --dontgraboutput
>> that way the output will not be interleaved
>
> Hmm, never tried that, and admittedly somehow cannot believe that the
> output of the different processes is /not/
On Thu, 2009-10-22 at 08:07 +0200, Frank Schoenheit, Sun Microsystems
Germany wrote:
> The more verbose the output is, the more difficult
> it is to actually find the line which *caused* the error, not just the
> error message, simply because all those parallel processes output is mixed.
One possi
Hi Christian,
> build --html --dontgraboutput
> that way the output will not be interleaved
Hmm, never tried that, and admittedly somehow cannot believe that the
output of the different processes is /not/ interleaved then, but even if
so: You cannot specify this when you start a build on a build
Hi Frank, *,
2009/10/21 Frank Schönheit :
> [...] a build.pl-feature to prefix the output of all spawned sub processes
> with
> a unique (process-)ID would be much more helpful in finding errors in
> the build logs of multi-process builds.)
build --html --dontgraboutput
that way the output will
Hi,
Starting with DEV300.m63, the build system of OpenOffice.org supports
three different build verbosity levels, which can be controlled by an
environment variable or a dmake parameter.
A description of the different levels can be found at
http://wiki.services.openoffice.org/wiki/Build_Verbosity
17 matches
Mail list logo
