Much better after the last commit !!

Start: 12:20
End Build: 12:21
Start Fixup: 12:21
End Fixup: 12:22
Start Verify: 12:21
End Verify: 12:22
ET: ~1 minutes

Total ET: 12:20 to 12:22 ( Mucho Better!!! ~2 Minutes)

The build flew past both the fix-up and verify, probably less that a few 
seconds of so.

I didn't use the rinstall builds in the past, I always used ( for 
testing new builds ) the Debug target, just for this reason, other than 
testing the WSJT-Suite installs, I always built the Release Install 
Target for those.

I did a search for dumpbin.exe, and do not have it installed, though I 
do have VS 15 installed on this box, as it's Win-10. I did a custom VS  
install, and I don't recall if I installed all the VC++ components or not.

On 7/28/2015 12:16 PM, Bill Somerville wrote:
> On 28/07/2015 19:06, Bill Somerville wrote:
>> On 28/07/2015 19:03, Greg Beam wrote:
>>> Hi Bill,
>> Hi Greg,
>>> Here's the crude times, just eyeballing the system clock. Bare in mind,
>>> this particular box is an old / slow 2.4 Ghz Quad Core clocked up to 3.0
>>> Ghz.
>>>
>>> Start: 11:39
>>> End Configure & Build: 11:41
>>> ET: ~2m
>>>
>>> Start Fixup: 11:41
>>> End Fixup: 11:49
>>> ET: ~8m
>>>
>>> Start Verify: 11:49
>>> End Verify: 11:54
>>> ET: ~5m
>>>
>>> Total ET: 11:39 to 11:54 ( == SLOW!! ~15 Minutes )
>>>
>>> The same box, on Linux, takes roughly 1.0 to 1.5 minutes or less.
>> Should be roughly the same on Windows but having the fixup use objdump
>> to determine dependent DLLs will slow it down at least that much.
> This is serious enough to warrant a quick hack, I have checked in a
> change that should speed things up a lot for those would don't have
> dumpbin.exe available and also for those using MinGW 4.9 which breaks
> dumpbin.exe anyway. It is not my final fix as I need to prepare
> something suitable for submission to the CMake developers but hopefully
> it will work for you and others for now.
>>> 73's
>>> Greg, KI7MT
>> 73
>> Bill
>> G4WJS.
>
73's
Greg, KI7MT

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to