juanjosegarciaripoll / emacs-build Goto Github PK

default is --with-X or --without-X?

Hello again!

I'm having problems getting Cairo enabled.
When running --with-all, the configure options seems to be correct.

Configuring Emacs with options
--with-zlib --with-gnutls --with-xml2 --with-lcms2 --with-json --with-harfbuzz --with-cairo --with-rsvg --with-png --with-gif --with-tiff --with-jpeg --with-xpm --disable-build-details --disable-silent-rules --without-dbus

But when the scripts prints out the table with all the features it says:
Does Emacs use cairo? no
So I guess something is not working as it should?
I can't really see why it isn't using Cairo when the configure options includes it. Do you have any idea?

Hi

Thanks for this script. I'm looking to move away from wsl2 and this is a great way forward. However, what have to be done to uninstall the packages installed by this script? Is it just a matter of unstalling msys2?
Furthermore, once pack-all action is executed, can I delete the zip files?

I have little experience with msys2, so apologies for the noob question.

If you try to use --with-cairo, you will get errors because --with-cairo is inserted into the features instead of cairo.

I propose to replace this line with:

        --with-*) add_feature `echo $1 | sed -e 's,--with-,,'`;;

would be better written as

    for f in $inactive; do echo "  --without-$f"; done

Otherwise the emacs-build.sh --help output looks odd (notice the missing dash in the last line when comparing with the lines above):

Emacs-build tool version 0.4.1, (c) 2020 Juan Jose Garcia-Ripoll
Usage:
... 8< snip 8< snip 8< ...
  --with-gnutls
  --with-zlib
  --without native-compilation

Hello, just something I that occured to med when using your release package.

I had problems connecting to Melpa with SSL, by using https://, the error seemed to indicate gnutls so I downloaded the newest version from https://gnutls.org/download.html (3.7.0:mingw64) and replaced the files in /bin with those from the 3.7.0:mingw64 and that fixed the problem.

Just for your information!

HI

My query is partly relevant to the issue here: #5.

The title pretty much says it all. It's an error message I get when your build script tries to compile w32image.c in the Emacs src directory because of the include of w32common.h in the same directory. It's a line in an enum declaration without an explicit initializer, i.e., it defaults to 0. The compiler complains and the build fails right at that step. FWIW, I'm building fejfighter/emacs and it's nearly there. I'll only go thru the few changes I made in minimal detail because ultmimately in the end they didn't solve the problem. fejfighter/emacs is a pgtk+nativecomp build. So I needed to go into emacs-build.sh (I know not what you had in mind at all) and change the repo to point to that and also change the branch to pgtk-nativecomp. That doesn't seem to cause any problems at all. I, of coursse, had to use a customized cmd of two lines to get it to do the right thing but the details aren't important. Ultimately (I think) I tracked it down to the gcc warning flag -Wno-missing-field-initializers so to deal with that I had to go into configure.ac and comment the relevant line out. I was sure that would take care of it. It hasn't. I might mention that I successfully built fejfighter/emacs on Ubuntu 21.04 despite the wellknown relevant bug in Ubuntu.

There appear to be a bunch of similar posts to Stack Overflow etc. all to do wth various problems related to Wndows installs of lots of different software (including notably SciPy) based on msys64 and mingw64 in the msys2 distribution. It would be hard to establish without providing lots of urls to check but the most intelligent suggestion Iv'e come across is that it has to do with new style headers than the (older) version of gcc can handle. Since the Emacs version is 28.0.50 IIRC that seems very possible.

So in conclusion two questions:

1. Do you have any insight into this about a possible workaround I might try if what I've outlined is indeed the problem without having to find alternative header files (which I always find to be a maintenance nightmare at least)? In particular, can I adjust your script to get a newer version of gcc (if that's indeed ultimately the problem)?
2. What in general is the correct overall strategy for "adjusting" your script for use cases you didn't originally envisage?

FWIW, I think your script is awesome!

Thanks very much in advance for any light at all you can shed on my two questions

Best regards
Mike

Hi

I see it in emacs-build.cmd, but not in the README file. Is it working properly?

Thanks,