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

The option was recently renamed to native-compilation #36

Closed
wants to merge 1 commit into from

Conversation

tjsousa
Copy link

@tjsousa tjsousa commented Apr 5, 2021

Native compilation would not be detected when configuring without this change.

Native compilation would not be detected when configuring without this change.
@jimeh
Copy link
Owner

jimeh commented Apr 5, 2021

Thanks for the submission, though this is already addressed by commit 581594d in such a way that it can compile both old a new source trees by detecting which of the two flags is needed to enable native compilation.

The build-emacs-for-macos command accepts a git ref (branch, tag, or commit from the emacs-mirror/emacs repo), rather than configure options. It has its own set of options though which control certain aspects of how it compiles Emacs.

So I'm afraid I will need to reject this change, as it would actually yield an error cause the branch is stilled named feature/native-comp:

$ ./build-emacs-for-macos feature/native-compilation
ERROR: Failed to get commit info about: feature/native-compilation

Feel free to reply here or open a new issue if you've got any problems though :)

@jimeh jimeh closed this Apr 5, 2021
@tjsousa
Copy link
Author

tjsousa commented Apr 5, 2021

That makes sense. Thank you for the explanation, for some reason I wasn't able to compile with native compilation support by copying the latest git sha from #6 (comment) and somehow was able to compile by changing the feature name (but it seems I was confusing the name of the argument with the branch name).

@jimeh
Copy link
Owner

jimeh commented Apr 5, 2021

Ah right, yes, the --git-sha option overrides the git ref lookup, making it just use the given git ref as a "name" for the final archive. I've been meaning to refactor that for a while as it's led to a decent bit of confusion.

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.

2 participants