[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Library "libcvs" Windows Link Warnings Report

From: Conrad T. Pino
Subject: RE: Library "libcvs" Windows Link Warnings Report
Date: Wed, 12 May 2004 01:32:32 -0700

Hi Derek,

> From: Derek Robert Price
> Sent: Monday, April 19, 2004 06:37
> >>From: Conrad T. Pino [mailto:Conrad@Pino.com]
> >>
> >>The Visual C++ 6.0 (VC6) Integrated Development Environment (IDE) Debug
> >>build of this library generates a multitude of "LNK4006" linker warnings.
> >>The full warning list follows at the end of this message.
> >>
> >>"LNK4006" warnings occur for *every* source (.c) file in this project.
> >>This is consistent with each input (.obj) file being listed twice in
> >>the linker's input file list.  There is no redundancy in .dsp file.
> >>
> >>Even more interesting is "LNK4006" warnings do NOT occur in the batch
> >>build using .dep/.mak files generated from .dsp file.
> >>
> >>IMO these "LNK4006" warnings are a *feature* of VC6 IDE only.
> >
> >While testing for a different topic I noted "LNK4006" warnings do occur
> >in the VC6 IDE Debug build but NOT the VC6 IDE Release build!!!

The above still seems to be true but I've not fully retested.

> How hard would this be to fix using the fix-msvc-build.pl script?

I don't understand what "this" means since "fix-msvc-mak.pl" fixes
.dep/.mak files and "LNK4006" issue doesn't occur in batch build and
I was hoping you could elaborate on whatever I've missed.

> If
> you have time, it might be nice to set a default of RECURSE=1 in the
> cvsnt.mak file as well so that `nmake clean' recurses by default.

I'm happy to since it's already done.  May I take the credit anyway? :)

> Derek


reply via email to

[Prev in Thread] Current Thread [Next in Thread]