This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Managing Linked resources without saving absolute file paths in a file under revision control

I apologize for the loaded title, maybe the question is best asked through an example. What is the preferred method for accomplishing the following scenario:

  • Several projects exist that share several modules but are different enough to warrant separate source repositories. 
  • The shared modules exist as a separate repository that can be cloned anywhere on a developers filesystem (Lets call it the SDK).
  • Two developers are working on the same project (Lets say an MSP430 project in CCS) and have a copy of the SDK located in two different places on their computers.
  • They must configured a path variable that points to the location of SDK (Which is linked into the project).

How is this accomplished without inserting conflicting paths into the .project file?

I initially created a Windows environment variable that pointed to the SDK. After attempting to link a folder based on the environment variable, I discovered this doesn't appear possible with Eclipse as a path variable must be created that is essentially a copy of the environment variable (Thus defeating the purpose of an environment variable and also inserting absolute paths into the .project file).

This seems like a problem that crops up all of the time, so I must be missing something simple.

Thanks,