Hello,
> I think that the only sustainable way to work with dependencies is to keep
> it simple. If C uses A and B it should depend on the right files from A and
> B regardless of any interdependencies between A and B.
I agree. I was trying to save myself some typing, but in good programming this is
always a bad idea! As someone pointed out to me, one can use scripts or alike to
extract the USE dependencies from a source file, but this means having to deal
with one more perl code I barely understand...
> This should be provided to us by the vendors.
Indeed. It is only now that I am really starting to do inter-compiler and
multicompiler everyday work, and am realizing the pain of it. I have of course
heard other people complain but always thought it was something that can be
handled. It is also an interesting question whether the standard could/should
regulate something like this. One would think though, as you suggested, that
vendors would be smarter and come along spontaneously...
Aleksandar
|