Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4744CB08.9020207@roguewave.com>
Date: Wed, 21 Nov 2007 17:19:20 -0700
From: Martin Sebor <sebor@roguewave.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: [PING] Re: library and build sizes on Windows
References: <4737E219.5010001@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE64380134EDA6@epmsa009.minsk.epam.com>
 <4739E091.1050707@roguewave.com>
In-Reply-To: <4739E091.1050707@roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

So would be it possible to change the Windows build infrastructure
to spit out the date and time in the same format as on UNIX? I.e.,

     ### date:
     Wed Oct 31 09:38:50 UTC 2007

Including the "### date:" part. The exact format of the timestamp
itself doesn't have to be exactly the same just as long as it
includes the time as well as the date, and it's all on the same
line.

If it's not easy, what would be? It's trivial to change the UNIX
format.

Martin

Martin Sebor wrote:
> Farid Zaripov wrote:
>>> -----Original Message-----
>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
>>> Sent: Monday, November 12, 2007 7:18 AM
>>> To: stdcxx-dev@incubator.apache.org
>>> Subject: library and build sizes on Windows
>>>
>>> I enhanced the cross-build scripts to extract the date of the build 
>>> and the sizes of the library and of the bildspace (before and after 
>>> running the clean target). This works on UNIX but not on Windows 
>>> where the date has a different format 
>>
>> On unix:
>> -----------------------
>> ### date:
>> Wed Oct 31 09:38:50 UTC 2007
>> -----------------------
>>
>> On windows:
>> -----------------------
>> Wed Nov 07 22:23:49 2007: Loading solution...
>> -----------------------
>>
>>   The difference in date format is the only UTC before year on unix :)
> 
> Right. The problem is the line above it. The script looks for the RE
> "^### date:" and takes the whole line below it as the date. We could
> have it look for the Windows-specific string on Windows (and strip
> what follows the timestamp) and the UNIX one on UNIX but I'd rather
> we standardize on the same data format than complicate the script
> logic.
> 
>>
>>> and the sizes aren't being reported. Would it be possible to change 
>>> the Windows infrastructure to add this info to the logs?
>>
>>   The cleaning targets performing by the BATMAN, so to add the sizes
>> to the logs the BATMAN scripts should be changed.
> 
> Okay. We'll move this part (the script that runs the whole build)
> to stdcxx very soon so we'll have direct control over its format.
> 
> Martin