The project is always out of date.

[Ed]

Hi, guys,
I add some new projects. No source file, but only some copy operation
in Post Event.
The project is to do some file deployment for some third party
library.

When I compile the solution, VC assumes the project is always out of
date and execute the Post Event always. It’s boring, the copy
operation will happen always, even if there is no modification in the
solution.

Do you have any ideas?

Thanks!
Ed.

[SvenC]

Re: The project is always out of date.

Hi Ed,

I add some new projects. No source file, but only some copy
operation in Post Event. The project is to do some file deployment
for some third party library.
>
When I compile the solution, VC assumes the project is always out of
date and execute the Post Event always. It’s boring, the copy
operation will happen always, even if there is no modification in the
solution.
>
Do you have any ideas?

How should the project now that it is up to date or not? You will
always need some source file which has some output files associated
so that file dates can be compared: if output-date < source-date
build the source.
You could add a dummy c file which you only change when you
got a new third party library. So you will get an exe or dll dependant
on your project type which can be compared to the c file date.
To explicity deploy the third party lib again you will need to choose
rebuild for that project.

--
SvenC

[Ed]

Re: The project is always out of date.

On Jul 28, 3:23 pm, "SvenC" <Sv...@nospam.n ospamwrote:

Hi Ed,
>

I add some new projects. No source file, but only some copy
operation in Post Event. The project is to do some file deployment
for some third party library.

>

When I compile the solution, VC assumes the project is always out of
date and execute the Post Event always. It’s boring, the copy
operation will happen always, even if there is no modification in the
solution.

>

Do you have any ideas?

>
How should the project now that it is up to date or not? You will
always need some source file which has some output files associated
so that file dates can be compared: if output-date < source-date
build the source.
You could add a dummy c file which you only change when you
got a new third party library. So you will get an exe or dll dependant
on your project type which can be compared to the c file date.
To explicity deploy the third party lib again you will need to choose
rebuild for that project.
>
--
SvenC

Thank you, SvenC.
That means the project must have an output file, lib, dll, or exe?

[SvenC]

Re: The project is always out of date.

Hi Ed,

>>When I compile the solution, VC assumes the project is always out of
>>date and execute the Post Event always. It’s boring, the copy
>>operation will happen always, even if there is no modification in
>>the solution.

>>

>>Do you have any ideas?

>>
>How should the project now that it is up to date or not? You will

....

>You could add a dummy c file which you only change when you
>got a new third party library. So you will get an exe or dll
>dependant on your project type which can be compared to the c file
>date.

...

That means the project must have an output file, lib, dll, or exe?

Yes, that gives the build process a reference file to see if the build is
up to date or not.

--
SvenC