all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Some Emacs outside Emacs
Date: Thu, 28 Jul 2022 10:53:10 +0300	[thread overview]
Message-ID: <83h731ad21.fsf@gnu.org> (raw)
In-Reply-To: <87sfml692a.fsf@elite.giraud> (message from Manuel Giraud on Thu,  28 Jul 2022 08:33:01 +0200)

> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Date: Thu, 28 Jul 2022 08:33:01 +0200
> 
> I'm trying to access some Emacs functions from lwlib.  So far, I'm able
> to get the frame for a given menu but whenever I try to access into that
> frame I get the following error from the compiler:
> 
> --8<---------------cut here---------------start------------->8---
> xlwmenu.c:1175:11: error: incomplete definition of type 'struct Lisp_X'
>             fs = FRAME_XIC_FONTSET (frame);
>                  ^~~~~~~~~~~~~~~~~~~~~~~~~
> ../src/xterm.h:1225:34: note: expanded from macro 'FRAME_XIC_FONTSET'
> #define FRAME_XIC_FONTSET(f) ((f)->output_data.x->xic_xfs)
>                               ~~~^
> ./../src/lisp.h:300:16: note: forward declaration of 'struct Lisp_X'
> typedef struct Lisp_X *Lisp_Word;
>                ^
> --8<---------------cut here---------------end--------------->8---
> 
> AFAIU, "struct Lisp_X" is a non existent struct and we are just interest
> in the pointer.  Is it a matter of a compiler option? Something else?

What is 'frame' in your code? how was it defined?  There's no such
variable in the current code of xlwmenu.c, so I cannot know what you
did.

To use FRAME_XIC_FONTSET, its argument must be a pointer to
'struct frame'.



  reply	other threads:[~2022-07-28  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  6:33 Some Emacs outside Emacs Manuel Giraud
2022-07-28  7:53 ` Eli Zaretskii [this message]
2022-07-28  7:55 ` Andreas Schwab
2022-07-28  8:43   ` Manuel Giraud
2022-07-29 14:37     ` Stefan Monnier
2022-07-28  8:39 ` Po Lu

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

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

  git send-email \
    --in-reply-to=83h731ad21.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.