Re: OOo Build on Win: unopkg prints debug info

I didn't use debug=t and setting or not setting the DEBUG variable made no
differenceA as far as I can tell.

This message (http://markmail.org/message/eqk2lwr6ut4c3msb) from a SUN
employee suggests, that OSL_DEBUG_LEVEL will always be greate than 1 for
non-pro builds. Does this by any chance mean, that I have to use Visual
Studio Professional?

Any other ideas?

eymux



On Tue, Mar 15, 2011 at 9:37 AM, Stephan Bergmann <
[email protected]> wrote:

> On 03/15/11 09:24, Andor E wrote:
>
>> I'm building OOo 3.2.1 on Windows. For some reason unopkg and other
>> command line tools print trace info ("inserting new mapping") to the
>> console. I'm quite certain, that I didn't create a debug build. I've
>> even defined an envionment variable DEBUG=false. But it's still printing
>> these annoying lines. According to my build log the variable
>> OSL_DEBUG_LEVEL, which supposedly governs the trace output, is set to 0.
>> How do I disable the trace output?
>>
>
> Setting the DEBUG environment variable to any non-empty value (even
> "false") causes it to take effect (i.e., you do a debug build).
>
> -Stephan
>
> --
> -----------------------------------------------------------------
> To unsubscribe send email to [email protected]
> For additional commands send email to [email protected]
> with Subject: help
>
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help