[Vm-dev] build.macos32x86/pharo.cog.spur and dependency tracking

Holger Freyther holger at freyther.de
Fri Aug 25 15:10:18 UTC 2017

> On 25. Aug 2017, at 23:07, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi Holger,

> A fair distance away :-). Each plugin and its support files get built with a separate make step which allows an external plugin to specify additional support libraries, include paths, etc.

okay, so a recursive make. But in each target it seems to unconditionally execute the linking step? Why is that necessary? What dependency might not be easily trackable?


More information about the Vm-dev mailing list