-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
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 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? 🤔. |
True, although unlike the things mentioned in differences.md, if you relied on this, your project would no longer build with meson. |
OK sorry. I figured some of those were breaking changes but I suppose not. In any case, thanks for the feedback. |
Wrong close tag. |
Has outputting to sub-directories in the build directory been considered?
Related
The text was updated successfully, but these errors were encountered: