I am moving the Visual SourceSafe code repository to Subversion and I am facing a problem.
Here is a simplified layout of our current source tree (in VSS):
project_root\
|-libs\
|-tools\
|-arch_1\
| |-include
| |-source
|-arch_2\
|-include
|-source
My problem is in our two folders arch_. Each folder arch_will be created for a different hardware architecture, but the contents of the two folders are almost identical. Files in arch_2are simply VSS associations with files in arch_1, and only a small fraction of the exceptions. The work is usually checked in arch_1and out of the folder , and the VSS links verify that any code checked here is also updated in the folder arch_2.
Moving into Subversion, is there anything that will behave like VSS links? That is, is there a way to have two files in separate folders magically linked to each other, so that they will always be synchronized with each other (changes in one will affect the other)?
Note. I know that the correct answer here is to fix the build system. The build system in this project was built about ten years ago when our compiler / build system was not intelligent enough to compile the same folder full of source code for two different architectures. Thanksmake , . , , ( VSS ). Subversion , , , ( !).
!
:. externals , , , . -, , / , .