unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fejfighter <fejfighter@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Aleksandr Vityazev" <avityazev@disroot.org>,
	emacs-devel@gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
	eller.helmut@gmail.com
Subject: Re: MPS and pgtk
Date: Thu, 27 Jun 2024 10:26:51 +1000	[thread overview]
Message-ID: <CALohuRC3oOUy9OY_o999a_-ViZnQBxxgy8yYc2rjm_KoLbfDag@mail.gmail.com> (raw)
In-Reply-To: <ppcagpq2yl3eq2kd3dz4hx7mcpjnzp5k2d6krjm7kwpoc6y52z@om2qouj6mptb>


[-- Attachment #1.1: Type: text/plain, Size: 2471 bytes --]

I have been loosely tracking the branch, but not with much time to actively
participate.

Here's a simple patch that will get Aleksandr past the compile issue.
I think there are still a couple of places that may catch out parts of
gtk/wayland, but this is usually stable for a few minutes.
But this branch is fast moving so it's hard to track what's unique.

On Thu, Jun 27, 2024 at 8:39 AM Ergus <spacibba@aol.com> wrote:

> On Wed, Jun 26, 2024 at 06:38:03PM GMT, Gerd M�llmann wrote:
> >Aleksandr Vityazev <avityazev@disroot.org> writes:
> >
> >> Hello,
> >>
> >> I tried to build scratch/igc with the "--with-pgtk" flag
> >> got the following errors:
> >>
> >> make[3]: Leaving directory
> '/tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/admin/unidata'
> >>   CCLD     temacs
> >> ld: pgtkterm.o: in function `mark_pgtkterm':
> >>
> /tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:357:
> undefined reference to `mark_object'
> >> ld:
> /tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:358:
> undefined reference to `mark_object'
> >> ld:
> /tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:359:
> undefined reference to `mark_object'
> >> ld:
> /tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:360:
> undefined reference to `mark_object'
> >> ld:
> /tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:361:
> undefined reference to `mark_object'
> >> ld:
> pgtkterm.o:/tmp/guix-build-emacs-igc-31.0.50-0.544e031.drv-0/source/src/pgtkterm.c:369:
> more undefined references to `mark_object' follow
> >> collect2: error: ld returned 1 exit status
> >>
> >> The remaining configuration flags were as follows:
> >> --with-mps=yes
> >> --with-cairo
> >> --with-modules
> >> --with-native-compilation=no
> >> --disable-build-details
> >
> >Looks like pgtk is currently not supported, i.e. apparenlty no one
> >working on igc is using it, sorry.
> >
> This is wondering me because all the main distributions/desktops are
> moving (or have already moved) to Wayland.
>
> So, IMHO the pgtk support may be prioritized as it is the only way we
> support Wayland natively.
>
> Not sure if there are plans or alternatives under consideration to
> change/improve pgtk, but if igc becomes an issue for it... we may
> rethink if we really want it looking to the future?
>
> WDYT?
> Ergus
>
>

[-- Attachment #1.2: Type: text/html, Size: 3121 bytes --]

[-- Attachment #2: 0001-src-pgtkterm.c-mark_pgtkterm-exclude-from-MPS-builds.patch --]
[-- Type: text/x-patch, Size: 681 bytes --]

From 308ccb6145f390168f842f1b4135e0868d48d68b Mon Sep 17 00:00:00 2001
From: Jeff Walsh <fejfighter@gmail.com>
Date: Wed, 29 May 2024 12:40:03 +1000
Subject: [PATCH] * src/pgtkterm.c (mark_pgtkterm): exclude from MPS builds

---
 src/pgtkterm.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/pgtkterm.c b/src/pgtkterm.c
index 49b7ea406f8..7279f5d863b 100644
--- a/src/pgtkterm.c
+++ b/src/pgtkterm.c
@@ -336,6 +336,7 @@ evq_flush (struct input_event *hold_quit)
   return n;
 }
 
+#ifndef HAVE_MPS
 void
 mark_pgtkterm (void)
 {
@@ -369,6 +370,7 @@ mark_pgtkterm (void)
 	mark_object (device->name);
     }
 }
+#endif
 
 char *
 get_keysym_name (int keysym)
-- 
2.45.2


  reply	other threads:[~2024-06-27  0:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 12:56 MPS and pgtk Aleksandr Vityazev
2024-06-26 16:38 ` Gerd Möllmann
2024-06-26 22:38   ` Ergus
2024-06-27  0:26     ` Fejfighter [this message]
2024-06-27  3:59       ` Gerd Möllmann
2024-06-27  6:12         ` Eli Zaretskii
2024-06-27 19:07           ` Helmut Eller
2024-06-27 19:23             ` Gerd Möllmann
2024-06-28  3:13               ` Gerd Möllmann
2024-06-27  3:57     ` Gerd Möllmann
2024-06-27  6:08       ` Eli Zaretskii
2024-06-27  5:40     ` Eli Zaretskii
2024-06-27  6:09       ` Po Lu
2024-06-27 10:19       ` Arsen Arsenović
2024-06-27 10:36         ` Eli Zaretskii
2024-07-06  0:32           ` Konstantin Kharlamov
2024-06-27 12:26         ` Po Lu
2024-07-05 21:41         ` Björn Bidar
     [not found]         ` <871q47freu.fsf@>
2024-07-06  2:01           ` Daniel Colascione
2024-07-07  3:11           ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALohuRC3oOUy9OY_o999a_-ViZnQBxxgy8yYc2rjm_KoLbfDag@mail.gmail.com \
    --to=fejfighter@gmail.com \
    --cc=avityazev@disroot.org \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=spacibba@aol.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).