You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIUC, currently, all relative paths for packages (pkg.path) are considered relative to the manifest file. But in cases they are provided by a [sources] entry they should in fact be treated relative to the project file. This only matters if the project and manifest file are in different directories. That situation can occur when using the manifest = entry in the project file or when using the subproject functionality in #3841.
This is a bit annoying because I think it means we need to remember from where the path entry was retrieved.
The text was updated successfully, but these errors were encountered:
KristofferC
changed the title
Probable bug in relative paths in [sources]
Bug in relative paths in [sources]Aug 12, 2024
IIUC, currently, all relative paths for packages (
pkg.path
) are considered relative to the manifest file. But in cases they are provided by a[sources]
entry they should in fact be treated relative to the project file. This only matters if the project and manifest file are in different directories. That situation can occur when using themanifest =
entry in the project file or when using the subproject functionality in #3841.This is a bit annoying because I think it means we need to remember from where the path entry was retrieved.
The text was updated successfully, but these errors were encountered: