![]() ![]() The dirty way of building universal is do two builds and then use lipo to stick them together. Macports has the framewoirk to do universal builds - they still maintain ports for ppc i386 x86_64 and now arm64 over OSX going back to Tiger in the best case. ![]() rust builds then you only get an intel build. If you are set up to get universal builkds on macports then if there is an arm build then you will get a universal one - if the arm does not work e.g. Is there an easy way to find the diffs between aquamacs and a GNU emacs 25.3.50.1?Īs for gnutls - macports builds it on Apple Silicon - I have a mac mini and got it. (and I don't use all Aquamacs changes)īut might it be easier to start with a emacs 27/8 build (which does build on Apple Silicon as I am using it) and add the aquamacs changes to that? I have taken some aquamacs setup to that - not much so not enough to build on. I am a longish time Aquamacs user but switched to current emacs - actually the mituhara port as Aquamacs development seemed to have stopped and I hit a problem with swiper - and I had time. There are probably some things I haven't though of yet. Figure out how to build gnutls, etc., as libraries in universal form (which I assume is theoretically possible, but I haven't looked into that).Figure out how to tweak the Aquamacs build for this. ![]() There may be some other dependencies we end up needing, but that's the big one.įor Aquamacs on M1 as a universal binary (which would be nice, but not essential to start): Better yet, have it building via Homebrew. See if gnutls and its package dependencies now works on M1.(This is somewhat limited, because you can't install packages this way, although you might be able to copy over the files from an x86 setup). See if Aquamacs will build and run for individual use on an M1 system, without including gnutls.Look into what's been done for other Emacs distributions on M1.I'm happy to work with anyone who wants to tackle any of it.įor Aquamacs on M1 as a separate distribution: I don't have an M1 system to work with yet. Here's an outline of the things I know need to be done for having Aquamacs native on M1/Apple Silicon. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented. Would it make sense to use rewrite emacs (the existing version), from a fork, and simply add the unique features of Aquamacs? I'm not sure if this is how Aquamacs works, but I do know Emacs does have a Universal Binary, thus it runs native on x86 and ARM 64 (I just picked up a m1 Mac on New Years day and I'm running it now and it's great). I did ok in my Programming languages course and will have to retake Systems II (c level code is hard!, but the first time around I learned a lot). You are too kind :) I'm relatively new to the Computer science field. > From what I understand, there are some issues with M1 compilation of some of the pieces we need for a full Aquamacs build. ![]() The Emacs build process calls for gcc, but Xcode is delivered with a "gcc" program that is just a wrapper for clang, so that's what actually gets called. > Not a stupid question at all! But it turns out we've been using clang for a long time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |