VC ++ 2008 project is always "out of date"

In one solution, I have two VC ++ projects. Project A has linker inputs, which are .obj files compiled by project B.

Visual Studio (2008) always informs me that the project is "outdated", and offers me to ask if I want to rebuild it, every time I want to run / debug / build / etc. Even immediately after creating the whole solution: I make a successful complete assembly, and then click "Create" again, and he wants to redirect project A.

How can I prevent this? Does anyone understand what is going on here?

+5
source share
3 answers

I think the solution is to stop using .obj files from another project. Instead, point the code that is common to both projects A and B to your own static library C and link both A and B to it.

+2
source

I had this problem with Visual Studio 2010 (with or without SP1) and thanks to Ted Nugent I was able to fix it. The trick is to check if all of the C ++ header files listed in the project still exist and delete nonexistent ones. Apparently this is a compiler error.

+2
source

- . , , . . , , , ( , ), .

"" unix.

include. "" .

+1

All Articles