-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Subproject_dir must not contain a path segment" in master breaks projects #2719
Comments
I just now was debugging an issue someone found in the Vibe.d project when compiling it with Meson (see vibe-d/vibe.d#1983 (comment) for reference). So, I guess there is definitely some issue here with using a nested subproject directory, but this issue was only introduced with Meson 0.43 and isn't present in prior versions. |
Any news on this one? I would really like to know what the course of action is (I can't even submit a patch without knowing what the Meson maintainers would like to do). |
I guess we can change the check to ensure that there are no |
That would work for me, and also ensure the subproject dir stays in the project's source tree and not some random location. So, check that |
The previous change disallowed any subdirectories for subproject dirs, and therefore broke a couple of projects making use of that. This change still prevents people from setting subproject dirs that are not in the project's source tree, while allowing to specify any path within the project's directory again. Resolves: #2719
Hi!
The new check introduced in c178a57 breaks existing projects which place their subprojects' wrap files in project subdirectories, e.g.
contrib/subprojects
.I've seen this quite often and actually used that particular path myself (why create another toplevel directory if there already is a directory dedicated for similar stuff?).
While I agree that paths like
../dummy
in there are awful, I think disallowing putting the files in any subdirectory is a bit aggressive. Can the check be relaxed to only check for the "is an absolute path used" and "is a relative path used that goes beyond the source_root" cases, or is there an obvious bug in using a level-2-subdirectory in source_root?The text was updated successfully, but these errors were encountered: