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

[Eliot Miranda]

Hi Holger,

> On Aug 25, 2017, at 8:10 AM, Holger Freyther <holger at freyther.de> wrote:
> 
> 
> 
>> 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?

Clearly it isn't.  If it does always link then it's a bug.  But beware; there needs to be dependencies on things like the makefile, plugins.int, etc to get things to be remade when things change.  I remember I had difficulties here when I was first using the makefiles.  So if you try and fix this check that you can move some plugin from plugins.int to plugins.ext and vice verse and the relevant files do get rebuilt appropriately.

> What dependency might not be easily trackable?
> 
> holger