By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,296 Members | 1,457 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,296 IT Pros & Developers. It's quick & easy.

The project is always out of date.

P: n/a
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.
Jul 28 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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

Jul 28 '08 #2

P: n/a
Ed
On Jul 28, 3:23 pm, "SvenC" <Sv...@nospam.nospamwrote:
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?

Jul 29 '08 #3

P: n/a
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

Jul 29 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.