Include flags with relative directories always resolve relative to workspace

Problem

If a SourceFileConfiguration includes a entry in compilerFragments like /I..\foo, cpptools will attempt to resolve that include directory relative to the VS Code workspace root and silently discard the flag if the directory does not exist. However, it's possible that the compiler process was invoked with a different working directory than the workspace root, and the relative include directory would have resolved successfully relative to the compiler's working directory.

Suggested fix

Add a new readonly directory?: string; property to SourceFileConfiguration that specifies the working directory of the compiler process. Relative paths in compilerFragments should resolve relative to directory, if it is defined.

Commencez par localiser la déclaration de SourceFileConfiguration et le code qui résout compilerFragments par rapport à la racine de l’espace de travail de VS Code. Vérifiez comment les répertoires de travail du compilateur sont représentés, puis assurez-vous qu’un répertoire défini est utilisé pour les chemins d’inclusion relatifs et que la nouvelle propriété facultative est exposée dans l’API publique.