Any ideas on reducing link times?
-
One of our projects is getting so large that development has become quite cumbersome due to the time it takes to link it. The project is an ocx that statically links MFC, CRT and a few other large libraries. Linking often takes a minimum of 45 seconds on my workstation (Dual P3-733, 384M ram, 10K rpm disks). I have tried everything and can't find anyway of reduceing the link times. The OCX is 20 megs in debug, 5 megs in release. Does anyone have any suggestions, or am is this typical for a project of this size? Chris Hafey PS - We have incremental linking turned on and using a dynamically linked version is not an option
-
One of our projects is getting so large that development has become quite cumbersome due to the time it takes to link it. The project is an ocx that statically links MFC, CRT and a few other large libraries. Linking often takes a minimum of 45 seconds on my workstation (Dual P3-733, 384M ram, 10K rpm disks). I have tried everything and can't find anyway of reduceing the link times. The OCX is 20 megs in debug, 5 megs in release. Does anyone have any suggestions, or am is this typical for a project of this size? Chris Hafey PS - We have incremental linking turned on and using a dynamically linked version is not an option
One thing that really reduces compile/link times is multible disks and a RAID. I have 3 SCSI disks, with 2 of them in a Win2k software RAID 0 (Stripe Set), and it goes like 75% faster :) - Anders Money talks, but all mine ever says is "Goodbye!"
-
One thing that really reduces compile/link times is multible disks and a RAID. I have 3 SCSI disks, with 2 of them in a Win2k software RAID 0 (Stripe Set), and it goes like 75% faster :) - Anders Money talks, but all mine ever says is "Goodbye!"
If you are using large number of dlls you can use the delayload feature in VC6++. Dll rebasing can also help performance. When linking, it helps if ALL the files are on the same local drive... Also, I noticed in my include/lib paths, I had a large number of redundant paths, taking these out, helped greatly. Just things that helped me. Gerry.
-
If you are using large number of dlls you can use the delayload feature in VC6++. Dll rebasing can also help performance. When linking, it helps if ALL the files are on the same local drive... Also, I noticed in my include/lib paths, I had a large number of redundant paths, taking these out, helped greatly. Just things that helped me. Gerry.
I doubt that delay load will speed up link times. Delayload speeds up 'apparent' load times. It does this because the linker inserts extra code into the DLL to handle delay loading. The fact that the linker has more to do when delay loading makes me think this option will not decrease link time. The linker still has to resolve the same number of symbols as with the non delay-loaded case, but also has to write the delay load stubs (one per function per delay loaded DLL) and the delay load handler (one per delay loaded DLL). Stephen Kellett Since I can't post on the forums, for the guy that was interested in UK developer magazines, I can't offer any help, but contact Parkway Gordon (not sure of web address but try the obvious... and try google). Parkway Gordon are based in the UK and handle magazine subs for most of the better American mags, and the service is superb. Not connected in anyway except as a very happy customer.