From: Elijah G <eg642616@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: How to link new libraries when building emacs
Date: Fri, 5 Apr 2024 16:53:18 -0600 [thread overview]
Message-ID: <CACnP4N+agx84zZdZX7bCw1VwFHm8w4=vVY9XFEvYOt8RYB9JoA@mail.gmail.com> (raw)
In-Reply-To: <86ttkg5qv1.fsf@gnu.org>
On Thu, Apr 4, 2024 at 11:19 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Elijah G <eg642616@gmail.com>
> > Date: Thu, 4 Apr 2024 16:47:07 -0600
> > Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
> >
> > On Thu, Apr 4, 2024 at 12:47 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > > I'm guessing that using Direct2D will need a whole new font back-end,
> > > since we'd need a different implementation of the main drawing methods
> > > exported by the font driver.
> >
> > I guess so, Also it needs DirectDraw (dwrite.h) which sadly most
> > of their functions to draw are made in C++ AFAIS,
>
> Yes, it seems so. It's the main reason we didn't try to use them in
> Emacs.
What a shame, I'll try to do a new back-end for Directdraw,
i can't promise it, but I hope I succeed.
> > i think I'll need to create a new header like w32direct2d.h
> > I wonder how to import another C header, do i need to modify
> > autoconf files or something like that?.
>
> No need to change autoconf files, just add the header and use it in
> the C sources. Autoconf changes are needed only if some systems don't
> have a header file, but for header files that are part of Emacs, that
> cannot happen.
Thanks for the info.
prev parent reply other threads:[~2024-04-05 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACnP4N+4Z8O9TKYbEg5bttTyf0t_PQJ_sDW4GF8hcgcWMSfjwA@mail.gmail.com>
2024-04-03 5:52 ` How to link new libraries when building emacs Po Lu
2024-04-03 16:42 ` Elijah G
2024-04-04 0:28 ` Po Lu
2024-04-04 2:15 ` Elijah G
2024-04-04 3:15 ` Po Lu
2024-04-04 3:49 ` Elijah G
2024-04-04 4:25 ` Elijah G
2024-04-04 6:47 ` Eli Zaretskii
2024-04-04 22:47 ` Elijah G
2024-04-05 5:18 ` Eli Zaretskii
2024-04-05 22:53 ` Elijah G [this message]
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='CACnP4N+agx84zZdZX7bCw1VwFHm8w4=vVY9XFEvYOt8RYB9JoA@mail.gmail.com' \
--to=eg642616@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).