Maybe try and write out the complete path for the github repo when using straight, I am using the abo e packages (except vertico) and have not had any issues
brew install emacs-plus@28 --with-native-comp
might be a more standard "easy" approach on MacOS.TBH the emacs-plus install didn't work for me (the Emacs.app produced failed with `LSOpenURLsWithRole failed`), whereas build-emacs-for-macos did work.
I suppose
brew tap d12frosted/emacs-plus
first? (I haven't tried it yet, and not sure I will.)
Re:Bringing GNU Emacs to Native Code (2020)
by TacticalCoder on Sunday May 02, 2021 @12:31AM
(#27012369)
Can't help as I'm on Linux (also I use ivy/avy/counsel and not consult/marginalia/vertico).
Out of curiosity, why did you reply?
Note: this was on an Intel mac; anyone with an M1 tried this yet?
I did run into some problems with some newer packages on the GNU ELPA. (Specifically consult, marginalia, and vertico by github.com/minad) Straight.el complained about not being able to find the packages. Any suggestions on what I might try to fix this?
[1]: https://github.com/jimeh/build-emacs-for-macos