Re: REPOST: extremely long link times

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: doug mansell (doug_mansell_at_hotmail.com)
Date: 07/28/04 

Date: Wed, 28 Jul 2004 10:23:22 +0800

Hi Steve,

I've had building speed issues in the past. Usually turns out not to be
the tools, but the environment.

are you building on or to a mapped or subst'd drive?
are you running anti-virus software?

Just a stab in the dark.... good luck.

Steve McLellan wrote:
> Hi,
>
> 1. Nope, and it's linking that's the problem - compiling's generally very
> fast. In any case, it's not getting anywhere near maxing the processor so
> it's not the workload slowing it down.
>
> 2. It is only recompiling the minimum but incremental linking apparently
> doesn't work under /clr.
>
> 3. I am now wondering whether it'd be better to split everything up into
> separate DLLs, but I don't want to for a couple of reasons. And besides,
> what puzzles me is why the linker seems to be sitting on its hands for a
> minute or two, without seeming to do any work.
>
> Cheers,
>
> Steve
>
> "Fireangel" <Fireangel@discussions.microsoft.com> wrote in message
> news:4F7E2010-A924-439C-B6BB-96CABE940FC5@microsoft.com...
>
>>I'm a fairly newbie to C++ and the like, so feel free to ignore...
>>
>>Some questions / comments:
>>
>>1. Are you using alot of #Define (or anything like that. Can't remember
>
> what they are actually called)?? I've had the displeasure of hacking
> somebodies old code that had ALOT of this stuff, and to compile it took
> close to 4 min. I went ahead and took out as much as I could (W/o killing
> the app), and it was a noticable change.
>
>>2. You may want to consider using the option "Enable Minimal Rebuild"
>
> under the projects configureation properties -> C/C++ -> Code Generation.
> If set to YES, the compiler will only create new OBJ for those files that
> have changed. It will keep the old OBJs and then link them. If you only
> change 1 file between, only 1 OBJ will be recreated (instead of them all).
> I think (not sure), but any files that include the file you change (Using
> #include) may have to be recompiled...
>
>>3. If you're just testing / debugging, why don't you make temp dll's for
>
> any part of the code that is "Done" or not being checked. For instance, I
> have a Map.dll that containes all my stuff related to geographical maps. I
> then include it as a referance, use #using, and that stuff never gets
> compiled. I then create a "include all" project that has all the code files
> in it. This does leave me with a lot of Test projects all over the place,
> but to test it does make it fairly fast.
>
>>
>>Can't think of anything else. Let me know if this helps...
>>
>>
>>GE
>>
>>"Steve McLellan" wrote:
>>
>>
>>>Hi,
>>>
>>>Sorry to repost, but this is becoming aggravating, and causing me a lot
>
> of
>
>>>wasted time. I've got a reasonably large mixed C++ project, and after a
>>>number of builds (but not a constant number) linking (and sometimes
>>>compiling) becomes immensely slow, and task manager shows that link.exe
>
> (or
>
>>>cl.exe) is barely using any processor time, but an awful lot of RAM
>
> (around
>
>>>150-200MB). I'm going to keep an eye on page faults since I can't think
>
> of
>
>>>anything else that could be causing this - the machine doesn't seem to
>
> be
>
>>>thrashing and is fairly responsive during building. Can anyone recommend
>>>anything?
>>>
>>>Thanks,
>>>
>>>Steve
>>>
>>>
>>>
>
>
>

Relevant Pages

  • Re: REPOST: extremely long link times
    ... and it's linking that's the problem - compiling's generally very ... somebodies old code that had ALOT of this stuff, and to compile it took ... only 1 OBJ will be recreated. ... This does leave me with a lot of Test projects all over the place, ...
    (microsoft.public.dotnet.languages.vc)
  • Re: REPOST: extremely long link times
    ... One of the office applications stalls until ... and it was a noticable change. ... the compiler will only create new OBJ for those files that ... This does leave me with a lot of Test projects all over the place, ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Over-riding equals method dilemma
    ... getting these compile errors/runtime errors if the code is changed as ... > public boolean equals(Object obj) { ... And as i mentioned equals/hashcode contract was mentioned in a different ...
    (comp.lang.java.programmer)
  • Re: djgpp on 386
    ... Nice to have references for things that far back so memory can't get too ... generates .OBJ directly). ... to compile it, and even then, you have to copy gstab.h to stab.h ... have to use DOS NASM because it can't shell the Win32 one (at least ...
    (comp.os.msdos.djgpp)
  • Re: Create assembly obj to link with Windows objs
    ... >Using MASM 5.1 and 6.x, I am able to compile and create an obj file. ... So, assuming that you really do have 16-bit MASM code, your choices are ...
    (comp.lang.asm.x86)