command line build up-to-date when it shouldn't be

Hot Topic

Debugging during Linking
COM port
Is it possible to...
worked fine for me, failed for them
Very Beginner
2005 upgrade ports Floating Point Consistency incorrectly
Newbie generics question
System.StackOverflowException
Dependency checker for 64-bit executables
MFC extension DLL project with /clr option causes link error on _DllMain

Visual C++

Can VC6 use VC.net dll?
Fortran Dll
dllexport and function templates specializations
logf problem?
MFC app with Windows Forms and User Control - what am I missing?
How to get all the Child Control of the Window Opened
Problem with _CrtSetReportHook on VC++ 2005
Adding ActiveX support to a project that doesn't support it!!!
Microsoft Visual C++ Runtime Library error question
Evil Error Link 2005 problem on release configuration; Debug config works great!?!

command line build up-to-date when it shouldn't be

I have a problem where a command line build of a *.vcproj file using the VCBuild task returns "BaseLib - up-to-date" when it really is not. BaseLib.vcproj produces the output library BaseLib.lib, and one of the *.cpp files in the project includes BaseLib.h. BaseLib.h has a last modified date of 5/30/2006, and BaseLib.lib has a modification date of 5/16/2006. The project is out-of-date right BaseLib.h *is* explicitly in the project.

However, if I open up the BaseLib.vcproj in Visual Studio 2005 and do a build-all then it does properly decide to rebuild everything.

Is anybody aware of this apparent bug, and is there a work-around



Answer this question

command line build up-to-date when it shouldn't be

  • praveen_josh

    yes, it sounds like a bug. you can report bugs to us at http://connect.microsoft.com/feedback/default.aspx SiteID=210

    please provide a repro case (project & source files) if at all possible. bugs of this nature are usually quite difficult for us to reproduce without a sample case.

    thanks,

    josh

    VC++ project system developer



  • Paulovsky

    I've encountered a problem and I'm wondering if any of you can help.

    I have a project: BaseLib.vcproj. I'm simplifying a bit, but it as a file BaseLib.cpp and BaseLib.h, and produces the static library BaseLib.lib. BaseLib.h has a modification date of 5/30/2006, and BaseLib.lib file a date of 5/15/2006. This project is out of date right

    What I've noticed is that if I invoke VCBuild to do the build that it says the project is up to date, but if I open the project file in Visual Studio 2005 then it detects that something needs to be built, and it properly builds the project. I don't have any

    Is this maybe a bug in VCBuild If so does anybody know of a workaround


  • RodRav

    joshep wrote:

    yes, it sounds like a bug. you can report bugs to us at http://connect.microsoft.com/feedback/default.aspx SiteID=210

    please provide a repro case (project & source files) if at all possible. bugs of this nature are usually quite difficult for us to reproduce without a sample case.

    thanks,

    josh

    VC++ project system developer

    I agree. I submitted a defect (with a sample program to reproduce) and hopefully it will be addressed. It's number 278903.

  • ColSchmoll

    I've merged this into the same question that was asked last week, and moved it to the VC forum since this is a VCBuild issue.

    Neil



  • LiquidBlaze

    There are problems related to vcbuild when it comes to one of the following:

    A vcbuild /rebuild should alleviate most issues related to command line building.



  • netexplorer

    Thanks for the reply. Unfortunately I don't do any of these things. It's a very simple project - just a Wizard generated MFC project with *no* changes whatsoever. It appears as if modifications to any *.cpp files trigger a rebuild, but a modification to a *.h file does not :-(.

  • Will K

    Moving this to the C++ forum since it's about VCBuild.

    Neil



  • command line build up-to-date when it shouldn't be
Answer this question