 <ul> <li><p>my libraries are in SVN, and I usually check them out for (branch them into) a project at ../libraries relative to the project. This keeps the scope of the includes dirs small and to the point. </p></li> <li><p>In the real source (.pas), paths are totally forbidden.</p></li> <li><p>no project related paths in global delphi searchpath (only per project, or they are truly universally shared sources/components)</p></li> <li><p>I hate poluting source with hardcoded paths, so I usually have only a few units in the project, always with relative paths. Not the VSS w:\ drive substitutes hack please! Typically these are the units that pull in framework parts or are needed due to visual inheritance or form initialization.</p></li> <li><p>Unfortunately, relative paths <em>can</em> be dangerous with Delphi, because they are relative to the working directory, which can change according to Delphi dialogs (e.g. Open). The solution is simple, have an include file with an unique name in the main project.</p></li> </ul>