-
Notifications
You must be signed in to change notification settings - Fork 131
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
More clarity of the build process #7
Comments
Not necessarily... but you definitely need
|
Thanks. |
I tried It gave me the error reported in the previous issue:
Then I tried to compile Emacs from source, which went fine. Run |
It has to be |
The build should work, if you run |
Thanks. The package successfully compiles without the However, after adding I then tried to evaluate
|
Is your emacs compiled with module support? Does the value of |
Thanks. I'm using emacs-mac. The value of
No module support, it seems. |
@srustamo you can add module support with |
@racktear thanks. I raised this issue in emacs-mac repo. |
@srustamo yes, you are correct. The command you mention there should do the trick. |
@srustamo I've actually tried to do it myself, and failed, as emacs-mac misses the emacs-module.h, despite being built with module support. I've sent a pull request to the homebrew formula that fixes it: railwaycat/homebrew-emacsmacport#112 You can edit your local brew formula with |
Thanks. Your PR is not merged yet. Adding PR code manually with
|
The Readme is not clear about the build process. There's a bit more clarity added in this issue.
So, do we need to build emacs from source to add emacs-libvterm? The above issue seems to indicate that not.
How do I go about building this package?
The text was updated successfully, but these errors were encountered: