<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yeah I know macports has an emacs app port that builds a gui. That’s fine if I just wanted <div class="">to use emacs. But I want to build emacs-27 from source. More of an exercise and because I </div><div class="">want to play around with the new features.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 3, 2020, at 6:07 PM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" style="font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">On 3 Jun 2020, at 9:10 pm, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:<br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On Jun 3, 2020, at 05:38, Carlo Tambuatco wrote:<br class=""><br class="">I’m attempting to build emacs-27 from source and I would like to have AppKit support for running natively on macOS and Gtk3 support.<br class=""><br class="">These are the gtk3 libraries I’ve got installed:<br class=""><br class="">gtk-osx-application-common-gtk3 @2.0.8_0 (active)<br class="">gtk-osx-application-gtk3 @2.0.8_0 (active)<br class="">gtk3 @3.24.20_0+quartz (active)<br class="">gwenhywfar4-gtk3 @4.20.2_0 (active)<br class=""><br class="">This is the warning I got during the configure step of compilation:<span class="Apple-converted-space"> </span><br class=""><br class="">checking for X... no<br class="">checking AppKit/AppKit.h usability... no<br class="">checking AppKit/AppKit.h presence... yes<br class="">configure: WARNING: AppKit/AppKit.h: present but cannot be compiled<br class="">configure: WARNING: AppKit/AppKit.h: check for missing prerequisite headers?<br class="">configure: WARNING: AppKit/AppKit.h: see the Autoconf documentation<br class="">configure: WARNING: AppKit/AppKit.h: section "Present But Cannot Be Compiled"<br class="">configure: WARNING: AppKit/AppKit.h: proceeding with the compiler's result<br class="">configure: WARNING: ## ------------------------------------ ##<br class="">configure: WARNING: ## Report this to <a href="mailto:bug-gnu-emacs@gnu.org" class="">bug-gnu-emacs@gnu.org</a> ##<br class="">configure: WARNING: ## ------------------------------------ ##<br class="">checking for AppKit/AppKit.h... no<br class="">configure: error: The include files (AppKit/AppKit.h etc) that<br class="">are required for a Nextstep build are missing or cannot be compiled.<br class="">Either fix this, or re-configure with the option '--without-ns’.<br class=""></blockquote><br class="">The config.log file is where I would look to understand why this is happening.<br class=""><br class=""><br class=""><blockquote type="cite" class="">And configure says I do not have X installed:<br class=""><br class="">checking for X… no<br class=""><br class="">I also have ImageMagick installed, so I would like to link to that during the build also.<br class=""></blockquote><br class="">Any reason why you don't want to use the emacs or emacs-devel ports that are already in MacPorts? They do have an +imagemagick variant you can use.<br class=""></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Also note there is the emacs-app port that builds a native gui version. Sounds like exactly what is being asked for...</span><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Chris</span><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" style="font-family: Tahoma; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""><br class=""><blockquote type="cite" class="">So, I would like to know if there are extra devel libraries I need from macports and if I already have the relevant<span class="Apple-converted-space"> </span><br class="">libraries, how do I link to them when building emacs-27…?<br class=""></blockquote><br class="">Just to make sure we're on the same page about terminology, if you're referring to the -devel packages offered in some Linux package management systems, which provide headers and other files needed to build something against a library whereas the actual library files would be in a non-devel package, MacPorts doesn't do it that way. In MacPorts, the headers, libraries and binaries will all be together in a single port.<br class=""><br class="">We do have some -devel ports, as I mentioned emacs-devel above, but they have a different purpose in MacPorts: The -devel port will offer a (usually more recent) development version of the software while the non-devel port will offer a stable version of the software.<br class=""><br class="">AppKit, being a part of macOS, won't be in a port; it'll just be there in the OS.</blockquote></div></blockquote></div><br class=""></div></body></html>