Re: Cannot activate incremental link - please help

From: Matt Dillard (matt.dillard_at_gmail.com)
Date: 02/04/05 

Date: 4 Feb 2005 07:48:58 -0800

A follow-up to this older post, for future reference:
I experienced the same problem with a project I'm working on -
incremental linking would never kick in despite having the project
setting turned on, even when I made a trivial change to a non-library
cpp file. This is using VC++ 7.1.

In the project I was working on, I had the linker set up to ignore the
default library nafxcwd.lib, and then I explicitly added it to the
libraries to link against list. This was to prevent some "new" and
"delete" symbol conflicts in MFC's library and the C runtime library
(see Microsoft's Knowledge Base article Q148652 for more info).

I discovered that this caused the linker to think that project settings
had changed every single time it went to link. By changing the linker
settings to not ignore the default library nafxcwd.lib, the project
still linked successfully, and this time incrementally, as well. Note
that this means I was not exactly following Microsoft's recommended
practice in their KB article, but it still links and runs okay -
perhaps that KB article is geared toward an older version of their
linker.

Matt

Alex Shturm wrote:
> Actually we don't use the concept of "project" (in VS terms). We have
a
> lot of source files that are compiled and linked using command-line
runs
> of the compiler and linker, using make and makefile.
>
> Non-incremental link takes about 10 min on a 2.5 GHz 1Gb RAM machine,

> which makes development pretty painful.
>
> In my experiment I've tried to change just one source file and run
the
> same make/makefile, so only one object file was recompiled (no
libraries
> were changed). Still the linker did not do incremental linking... :(
>
> Alex
>
> Rudy Ray Moore wrote:
>
> >Incremental linking doesn't work when you change a library in your
> >workspace.
> >
> >Only expect incremental linking when you change *only* a file in
your
> >"startup project." A change in any other project will trigger a
full link.
> >
> >Linking is so much slower in VS7.1/.net/c++/2003 that you really
notice
> >those full links!
> >
> >Chris
> >
> >
> >
> >

Relevant Pages

  • Re: A way to decrease executable sizes?
    ... >Is there any way to make the linker reject all the code that isn't needed? ... When you create a project that is composed of several primary source files, ... of object file: a "library" file. ... the libraries is /not/ necessarily one we want, ...
    (comp.lang.cpp)
  • Re: data transfer
    ... Files that end with '.src' or '.c' are source files, raw material in source form for the compiler to turn into relocatable code that the linker can use. ... Files that end in 'obj' and perhaps other extensions depending on your system are object code, assembled from pieces -- your own code and code from libraries -- by the linker. ...
    (comp.dsp)
  • Re: Defining many classes in a single file
    ... And one can declare just as many in a header file. ... Another reason for one class one file is due to linker ... smallest resolution. ... In this case, you can have libraries. ...
    (comp.lang.cpp)
  • FreeBSD 5.1 BETA 2 make cvsup-without-gui fails
    ... checking if the linker is GNU ld... ... checking whether the linker supports shared libraries... ... checking if libtool supports shared libraries... ...
    (freebsd-current)
  • Re: orphaned port?
    ... checking if the linker is GNU ld... ... updating cache .././config.cache ... checking if libtool supports shared libraries... ...
    (freebsd-questions)