stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <>
Subject Re: library and build sizes on Windows
Date Mon, 19 Nov 2007 05:46:35 GMT

I've committed a script to build and run our examples, locales, and tests:

You can see the expected format by running on UNIX. We're not using
it for our nightly builds yet but I plan/hope to transition to it this week.
Once that's done we need to do the same for Windows.


Martin Sebor wrote:
> Farid Zaripov wrote:
>>> -----Original Message-----
>>> From: Martin Sebor [] On Behalf Of Martin Sebor
>>> Sent: Monday, November 12, 2007 7:18 AM
>>> To:
>>> 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

View this message in context:
Sent from the stdcxx-dev mailing list archive at

View raw message