Joseph S. Myers wrote: > On Thu, 6 Aug 2009, Janis Johnson wrote: > >> I've been thinking about that lately, it would be useful for several >> kinds of functionality. We'd want effective targets for the language >> for using different options and for providing different error/warning >> checks for each language. I haven't looked into how to handle it with >> DejaGnu, maybe something like gcc.shared and a [symbolic] link to it >> called g++.shared; do links work with Subversion? > > Whether or not links work with Subversion, they don't in my experience > work well with "diff" (it likes to dereference them when comparing two > trees, so showing diffs to the same files more than once) and I wouldn't > recommend relying on storage of links or other special sorts of files in a > particular version control system, so possibly constraining future > conversions to other systems. It's quite possible links are also > problematic on some supported build systems.
I think MinGW would end up copying all the files into the linked tree. Possibly we could modify the algorithm that enumerates directories matching "$tool.*" to look for (e.g.) "*$tool.*" and then name directories like "c.c++.dg"? cheers, DaveK