<gtsml.owevwr@googlemail.com> wrote:
>Is there a way to make sure that a corrupted dlll due to build stop
>always recompile afterward?

<gtsml.owevwr@googlemail.com> wrote in message
news:1168614859.800547.94620@i15g2000cwa.googlegroups.com...
> Hi,
>
> I often have to stop builds of a dll before completion and sometimes
> that leaves the DLLs in a bad state:
> - it is obviously "half compiled" and therefore corrupted
> - but the timestamp is correct so it doesn't recompile when a new build
> is done
>
> Then I have to use depends.exe to find the corrupted dll, delete it and
> recompile.
> That is a bit cumbersome really...
>
> Is there a way to make sure that a corrupted dlll due to build stop
> always recompile afterward?
>
> Thanks
>

<gtsml.owevwr@googlemail.com> wrote in message
news:1168793853.629449.151290@l53g2000cwa.googlegroups.com...
> Deleting the DLL using an build-event or a simple Clean or rebuild will
> indeed solve the problem.
> But the compilation and linking time of the DLLs I'm working on are
> just too big to consider that solution.
>
> Note that the DLLs eventually gets corrupted only when I stop a build
> during the *linking* stage.
> Has anybody ever experienced that issue?
>
> Frank
>

Scot T Brennecke wrote:

> I would never expect the linker to give you predictable results if you interrupt it. If you
> absolutely must interrupt it, then you must be prepared to clean up after doing so. If your
> compiling and linking are too slow, then perhaps you need to be looking for a hardware solution
> (faster processor, hard drive, network card, memory, etc.) that resolves the bottleneck.
>
> <gtsml.owevwr@googlemail.com> wrote in message
> news:1168793853.629449.151290@l53g2000cwa.googlegroups.com...
> > Deleting the DLL using an build-event or a simple Clean or rebuild will
> > indeed solve the problem.
> > But the compilation and linking time of the DLLs I'm working on are
> > just too big to consider that solution.
> >
> > Note that the DLLs eventually gets corrupted only when I stop a build
> > during the *linking* stage.
> > Has anybody ever experienced that issue?
> >
> > Frank
> >