|
From: | Alex Matei |
Subject: | bug#45821: Emacs UDP support on Windows |
Date: | Mon, 2 Jan 2023 15:59:23 +0000 |
I like the
nt/INSTALL.W64 file but somehow I found
Step-by-step instructions to build Emacs for Windows 64 bit with MSYS2 and MinGW-w64. Now `native-comp` supported. (github.com) more useful. I was wondering if we are allowed to add links to such gists / blogposts? (I understand that they can become obsolete
at some point, but a section like useful references would be nice)
My problem with patching:
For me, having a good walkthrough with examples is really useful and that’s why I am asking if we can include links to such blogposts:
I am hoping others could find this useful too when they first take a look at building Emacs themselves. Sent from Mail for Windows From: Eli Zaretskii <eliz@gnu.org>
Sent: Monday, January 2, 2023 4:07:50 AM To: Alex Matei <matei.alexandru@live.com> Cc: rpluim@gmail.com <rpluim@gmail.com>; 45821@debbugs.gnu.org <45821@debbugs.gnu.org> Subject: Re: bug#45821: Emacs UDP support on Windows > Cc: "45821@debbugs.gnu.org" <45821@debbugs.gnu.org>
> From: Alex Matei <matei.alexandru@live.com> > Date: Sun, 1 Jan 2023 23:01:04 +0000 > > * Can we make the documentation for developing for Emacs more discoverable? Maybe with a markdown > / .org README? Which development documentation did you find hard to discover? Please be more specific. > * Are we allowed to update the README with more up-to date information, on the series of MYSYS > packages needed to be downloaded, and potentially with links to blog posts that describe the process in That was already done a few days ago, please look at the latest Git repository, in the nt/INSTALL.W64 file. > * Can we add sections about creating/ applying patches to the README? This stuff is in CONTRIBUTE. > * I had a bit of work to discover how `git am` works , and the whole business of email patches, etc. This is not specific to Emacs, so I don't think it's our job to teach this. You can always ask on emacs-devel if you have problems figuring this stuff out. > * It would be great if all of this will be part of the original README The purpose of README is different, and it's already quite large. We describe this in CONTRIBUTE. > * Where can I find more information about logging from C code? Use the function 'message'. > * Ideally I would like to compile Emacs with some new C functions, and then easily observe the behavior of > these functions I use the debugger when I need this. It is much more flexible and dfoesn't require me to decide up front what exactly I want to log. |
[Prev in Thread] | Current Thread | [Next in Thread] |