Timeline for How to build Emacs master branch (aka trunk) on MS-Windows
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2016 at 22:05 | comment | added | Brian Burns |
Okay, gnutls-available-p returns t using just the PATH setting, so I'll assume it's working for now - I'll submit a patch with the alternative method to copy the DLLs though, and possibly the gnutls exes, if those are needed, and update here later.
|
|
| Jan 9, 2016 at 21:00 | comment | added | lawlist |
In the most general sense without actually using it for email or something, the general test is with the function gnutls-available-p I understand the reason for simplicity when just referring to the system paths, but sometimes people may want to use the Emacs build on a different computer and they will wonder why images and stuff do not work out-of-the-box. There are lots of threads with people asking why pdf files look like gibberish in a regular buffer (i.e., because the lack png support), or why they can't do doc-view or preview in AUCTeX (same reason).
|
|
| Jan 9, 2016 at 20:48 | comment | added | Brian Burns |
Yeah, the original instructions were written that way, but Eli thought it better to use the PATH - lists.gnu.org/archive/html/bug-gnu-emacs/2015-12/msg01476.html. It is another option though - if you wanted to do it that way, you could just copy all the DLLs in the C:\msys64\mingw64\bin to the emacs bin folder - they're only about 32MB - cp /c/msys64/mingw64/bin/*.dll bin. I don't know much about gnutls though - is there a simple way to test it out?
|
|
| Jan 9, 2016 at 20:11 | comment | added | lawlist | Consider adding a step to copy over whatever .dll files that need to be placed in the same directly as the Emacs executable once the build is complete, so that Emacs doesn't need to rely upon on a system-wide defined path to find those files. Also, it is probably necessary to copy over the executable(s) for gnutls into the Emacs executable directory. The last steps should likely be fairly similar to the Emacs 32 build in the alternative answer. | |
| Jan 1, 2016 at 16:54 | history | answered | Brian Burns | CC BY-SA 3.0 |