-
-
Notifications
You must be signed in to change notification settings - Fork 238
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
Restore normal Makefile behavior for .erl files #861
Comments
Now that OTP has implemented the compile server, is this behavior something you plan to change? |
Yes initially as an option and then possibly by default if it all goes well. But I am busy with other things at the moment. |
That would be great! But even without that change, maybe it would be good to change the
Totally understand being busy :) let us know if you would like pull requests... |
IIRC PRs are more than welcome otherwise. Feel free to do the entire compile server work because I'm going to be busy for a while. |
Thanks @essen. To be more explicit about the "doesn't quite catch everything": if you add
then any You are right about I and @mbj4668 spent an hour taking a stab at the compile server thing, but we realized that it takes quite a bit more re-architecting than we initially thought (on account of how the dependencies are setup currently). So we parked it for now, also too busy:) Cheers! |
Please open a separate ticket about |
Okay, thanks! I'll try to make a minimal reproduction and open a separate ticket about that. |
We spent some more time on the compile server, and managed to get it to work, so I created a PR with the code we came up with. The biggest (?) problem is that ERL_FILES contains both the original source files and generated files (from yrl etc). |
Plan is to get the compile server work in sometimes next year. |
For .erl and similar files we group everything under one target in order to pass them all to
erlc
at once. A new Erlang/OTP PR would allow us to restore normal behavior with one file per target, in turn enabling more scenarios and making Erlang.mk less surprising.erlang/otp#2361
The PR is not yet in a release so this mode of operations should not be the default for quite some time or we'll end up slowing down everyone's builds.
We can most likely enable this erlc server by default since Erlang.mk uses the same options for all the files in a project. It would still be good to allow a project to disable this of course.
The text was updated successfully, but these errors were encountered: