Skip to content
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

Path separators in target output. #7

Closed
DanielDavis5 opened this issue Nov 21, 2023 · 5 comments
Closed

Path separators in target output. #7

DanielDavis5 opened this issue Nov 21, 2023 · 5 comments

Comments

@DanielDavis5
Copy link

Has outputting to sub-directories in the build directory been considered?

Related

@annacrombie
Copy link
Owner

This would be trivial to implement in muon, the main problem being that relying on it would make your build incompatible with meson. I have been toying with the idea of adding an option like -Dmuon_extensions=enabled or something that would let you experiment, but I would discourage projects from relying on it.

I'm actually way less ideological about things than the core meson people (particularly jpakkane), but my hands are tied as long as muon is subordinate to meson. Even if muon magically became the primary meson implementation, unless it was that the vast majority of people were using muon exclusively I wouldn't want to make this kind of change due to potentially fracturing the community.

I do wonder though if muon does budge on some long-standing issues with poor motivation like this, would it help force the meson team to budge? 🤔.

@DanielDavis5
Copy link
Author

Unlike some of the items listed here, this would not be breaking mesons compatibility. Removing the check appears to have no consequence.

code

@annacrombie
Copy link
Owner

True, although unlike the things mentioned in differences.md, if you relied on this, your project would no longer build with meson.

@DanielDavis5
Copy link
Author

OK sorry. I figured some of those were breaking changes but I suppose not. In any case, thanks for the feedback.

@DanielDavis5
Copy link
Author

Wrong close tag.

@DanielDavis5 DanielDavis5 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants