-
Notifications
You must be signed in to change notification settings - Fork 39
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
Switch the build system to dune #74
Conversation
And merging ppx_tools_versioned into ppx_tools can be done separately, imho. |
What do you think about merging this one before the release (the one with 4.08 support)? |
Rebased one more time, please take a look. |
Maybe @kit-ty-kate or @gasche can take a look? |
This PR feels too big (adds too many new things) for me to review it properly. Could it be split into two? One for just dune and one for the "bit of glue code so that ppx_tools.metaquot can be easily used with dune"? |
Also looking at it, it seems that the |
Or if not in two PRs, at least two commits |
I removed the |
I don't think it is strictly necessary. I've just tried it myself and ended up with this branch: master...kit-ty-kate:dune It is almost exactly a 1 to 1 equivalent to the Makefile version. I'd much rather have that for now than merge this PR in one go, but that's just my view on the subject. What do you think of spliting this PR into my branch and a new PR with the change in your branch on top? |
Ok, I will rebase once your PR got merged. Thank you! |
Irrelevant then, closing. |
Rebased #67