Re: [patch] NUMAQ subarchification

Martin J. Bligh
2003-03-16T03:15:09Z

>> It is the place designed for code belonging only to one subarch.
>>
>> > Last time I looked (and I don't think anyone has fixed it since)
>> > it requires copying files all over the place, making an unmaintainable
>> > nightmare. Either subarch needs fixing first, or we don't use it.
>
> I agree that duplicating files into different subarch dirs sure isn't the
> way to go.
>
>> The problem you have (your setup.c and topology.c are identical to the
>> default) was originally going to be solved using VPATH. Unfortunately,
>> that got broken along the way in the new build scheme, so the best I
>> think you can do is add this to the summit Makefile
>
> I think VPATH has never been meant to be used for anything like this, it
> could be make to work, though it would interfere with the separate src/obj
> thing. But I don't think it's a good idea, we'll have object files
> magically appear without any visible source file, that's just too obscure.
>
> I can basically see two options at this point:
>
>> $(obj)/setup.c: $(src)/../mach-default/setup.c
>> cat $< $@
>
> Something like this, but using ln -sf would be nicer, since that avoids
> someone editing the wrong file by mistake.

GNU diff doesn't seem to understand soft links, so I don't think that's
feasible unfortunately. The ../mach-default stuff still requires you to
edit each subarch's makefile when adding a file to any subarch, which is
a pain in the butt, but better than the duplicated files by a long way.

Another comprimise solution for now might be to leave the Makefile entries
with ifdefs in the main Makefile (just as we do without subarch), but just
move the subarch files into the subarch dirs ... at least until we get a
better plan sorted out? That'll mean much less reshuffling when it's fixed.

M.