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

Switch the build system to dune #74

Closed
wants to merge 2 commits into from
Closed

Conversation

XVilka
Copy link

@XVilka XVilka commented Jul 1, 2019

Rebased #67

@XVilka
Copy link
Author

XVilka commented Jul 1, 2019

And merging ppx_tools_versioned into ppx_tools can be done separately, imho.

@XVilka
Copy link
Author

XVilka commented Jul 5, 2019

What do you think about merging this one before the release (the one with 4.08 support)?

@XVilka
Copy link
Author

XVilka commented Jan 14, 2020

Rebased one more time, please take a look.

@XVilka
Copy link
Author

XVilka commented Jan 14, 2020

Maybe @kit-ty-kate or @gasche can take a look?

@kit-ty-kate
Copy link
Collaborator

kit-ty-kate commented Jan 14, 2020

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"?

@kit-ty-kate
Copy link
Collaborator

kit-ty-kate commented Jan 14, 2020

Also looking at it, it seems that the .depend and META files are still present. Could they be removed in the first PR?

@kit-ty-kate
Copy link
Collaborator

Or if not in two PRs, at least two commits

@XVilka
Copy link
Author

XVilka commented Jan 15, 2020

I removed the .depend and META.
Regarding the metaquot changes - they are still necessary because the original buildsystem was providing the metaquot, so split would break the build. And these changes are kind of trivial anyway, wouldn't reduce the main commit size much.

@kit-ty-kate
Copy link
Collaborator

Regarding the metaquot changes - they are still necessary because the original buildsystem was providing the metaquot, so split would break the build. And these changes are kind of trivial anyway, wouldn't reduce the main commit size much.

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?

@XVilka
Copy link
Author

XVilka commented Jan 21, 2020

Ok, I will rebase once your PR got merged. Thank you!

@XVilka
Copy link
Author

XVilka commented Feb 12, 2020

Irrelevant then, closing.

@XVilka XVilka closed this Feb 12, 2020
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

Successfully merging this pull request may close these issues.

3 participants