From stdcxx-dev-return-3355-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Wed May 16 14:52:22 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 84071 invoked from network); 16 May 2007 14:52:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 May 2007 14:52:21 -0000 Received: (qmail 55853 invoked by uid 500); 16 May 2007 14:52:27 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 55846 invoked by uid 500); 16 May 2007 14:52:27 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 55827 invoked by uid 99); 16 May 2007 14:52:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 07:52:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 07:52:20 -0700 Received: from [10.70.3.48] ([10.70.3.48]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l4GEpGX7023314 for ; Wed, 16 May 2007 14:51:16 GMT Message-ID: <464B1A8F.6030409@roguewave.com> Date: Wed, 16 May 2007 08:51:59 -0600 From: Andrew Black User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: unprintable characters in Windows build logs References: <461F0438.2070700@roguewave.com> <4638B61C.30703@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64387D838D@epmsa009.minsk.epam.com> <4648824D.4060002@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64387D8476@epmsa009.minsk.epam.com> <46489627.9020508@roguewave.com> In-Reply-To: <46489627.9020508@roguewave.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Martin Sebor wrote: > Farid Zaripov wrote: >> >> I'm afraid the only way to get rid of them is postprocess output >> using some script. > > I see. I'm not sure it's worth the trouble unless we already do > some other preprocessing on these or other files. What do you > think? > >> That characters is coming during cleanup step. Windows build scripts >> doesn't contain >> such step. I suppose that night build system invokes cleanup step >> after invoking the >> build_msvc-x.x.bat batch file. This batch file invokes build.wsf >> script and then makelog.wsf >> script. I can add "/clean" switñh to the build.wsf script and add >> invoking "build.wsf /clean" >> àfter invoking makelog.wsf within build_msvc-x.x.bat batch file. I don't think adding this switch to the generated build_foo.bat script would help me much, as I run my own script on the result logs to extract the information I want from them, and I copy several files to alternate locations prior to calling devenv with the /clean switch. > > I suppose the nightly build script that invokes the Windows > infrastructure could do this type of postprocessing for us > since it already does do some processing (I think it does). > Andrew, what are your thoughts? At this time, the log file on windows is essentially a redirection of the console output to a file. It would be possible to post-process this output similar to how we do so on unix, but we don't have anything doing such processing on windows at this time. > FWIW, I don't think this particular issue is a major or even > moderately serious problem, but it seems like eliminating control > characters would make the infrastructure more robust in general. > > Martin