Re: Toplevel link-only project does not get linked during build
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Fri, 17 Nov 2006 07:50:28 -0800
Well, Visual Studio is not without bugs so that could be happening.
Usually, when I've had similar problems it's because I copied a project file
from another and renamed it or did something similar to get VS confused (it
used to have it's own numeric ID for the project that got duplicated so two
or more projects would look like the same one).
Tom
"Gernot" <Gernot@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AA545269-B9E9-436A-AAAE-D8F4D4CFDD12@xxxxxxxxxxxxxxxx
Thanks for the response, Tom. Forcing the link in a post-build step would
solve the problem, but is quite inconvenient to set up. About the linker
thinking the files are up to date: I don't think so. The behavior is the
same, even in the initial build when none of the output files even exist.
I'd
tend to say I'm simply seeing buggy behavior in Visual Studio. A logical
explanation for the phenomenon eludes me so far.
"Tom Serface" wrote:
I'd guess the linker is thinking the files are up to date. You could
force
the link in a post build step or perhaps delete the Project T file so it
has
to be recreated in a pre-build step.
Tom
.
- References:
- Re: Toplevel link-only project does not get linked during build
- From: Tom Serface
- Re: Toplevel link-only project does not get linked during build
- Prev by Date: Problem with cryptoapi
- Next by Date: Re: Microsoft Visual C++ Runtime Library Runtime Error
- Previous by thread: Re: Toplevel link-only project does not get linked during build
- Next by thread: VC++ 2005 Express updates
- Index(es):
Relevant Pages
|