Re: Off Topic (was: Should this package be included into the NS port?)

[Alan Third]

On Wed, May 23, 2018 at 12:30:08PM +1000, Van L wrote:
> Something to improve and explain the configure options specific to a
> great experience on the platform. I use the following by ritural
> trial and error and don’t know why. I couldn’t put the sicp.info
> file in /usr/share/info despite su-ing and don’t know why.
> 
>   #+BEGIN_EXAMPLE
>     CC=clang ./configure \
>       --disable-acl \
>       --prefix="$HOME/2018/Applications" \
>       --with-xpm \
>       --with-jpeg \
>       --with-tiff \
>       --with-gif \
>       --with-png \
>       --with-xml2 \
>       --with-imagemagick \
>       --with-xft \
>       --with-libotf \
>       --with-ns \
>       --with-zlib \
>       --without-selinux \
>       --without-gpm \
>       --without-dbus \
>       --without-gsettings \
>       --without-libsystemd \
>       --with-mailutils \
>       --with-x \
>       --with-x-toolkit="lucid" \
>     #    --without-compress-install \
>     #    --without-x \
>     #    --disable-ns-self-contained \
>     #    --without-gnutls \
>     #    --with-modules \
> 
>   #+END_EXAMPLE

I’ve seen this kind of incantation used before and I have to be
honest, I’ve no idea why. I just use:

    ./configure

and it works fine. I notice you’re building with both --with-ns and
--with-x, and I’ve no idea what actually happens in that case...

> >> and mention the Mac port.
> > 
> > Seems unlikely given it’s not part of GNU Emacs.
> 
> Detailing where and why Mac port does better than the GNU Emacs sets a target 
> to better.

IMO it’s better to raise bug reports about things that don’t work so
well in the NS port with concrete examples.

BTW you might find the TODO file interesting, it discusses a number of
issues in the NS port.
-- 
Alan Third