You can re-open the issue if you would like to have more discussion there.
The build step does not always re-run. If you have an update step
before the build step, then the update step always re-runs, and the
build step after it, but many external projects do not have an update
step, or anything
Ok, I'll double-check this next monday. That's why I was confused.
On the second thought if you have a list of sources you can add them as
dependencies in addition to build rule, then step will be re-run as
expected. May be it's my case.
Anyways I need to do some more investigation.
Best
The typical ExternalProject is a bit of a black-box to the containing
project, and a list of sources is something most users will not
have... That's another reason why I am skeptical as to the usefulness
of this feature to the general ExternalProject consumer.
On Fri, Aug 12, 2011 at 11:24 AM,
It is, if you use it for 3rd-party libraries.
But some people (including me :)) may use it to build different parts of
single project with different compilers (I have one library which should be
built with VC6 and the rest of the project with VC2010, but I change code in
each place with same
