RAD Studio .dproj absolute paths break cross-machine builds

Portable project configuration

Teams using RAD Studio need a repeatable development environment where project files open cleanly on any workstation without manual path adjustments. The .dproj format stores build configurations and search paths, but the XML often contains absolute filesystem references tied to the original machine's directory structure.

Path resolution uncertainty

Library Path entries in Tools > Options apply globally per IDE installation, while project-specific paths live inside each .dproj. When a repository is cloned to a different root folder, hardcoded absolute paths in the project file cause missing-unit or missing-library errors. The IDE does not automatically convert these to relative paths or expand shared environment variables.

Open questions

• What is the supported method for authoring .dproj files so that search paths resolve relatively from the project directory across machines?
• How should Library Path globals be coordinated with project-relative paths to avoid duplication and drift?
• Can Project Groups enforce a consistent path-resolution strategy for shared dependencies without per-machine IDE configuration?