all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: 64-bit build on Windows
Date: Thu, 26 Jan 2017 20:05:45 +0100	[thread overview]
Message-ID: <86a8adhcae.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STUwsyazdQdZqbL6Tedxb1v18Pu+oVxoOq2nL8y7osqdA@mail.gmail.com> (Juanma Barranquero's message of "Sat, 21 Jan 2017 19:37:34 +0100")

Juanma Barranquero <lekktu@gmail.com> writes:

> On Fri, Jan 20, 2017 at 3:32 PM, Óscar Fuentes <ofv@wanadoo.es> wrote:
>
>> I have no idea about PKG_CONFIG_PATH. The MSYS2 recipe does not mention
>> it and seems to work just fine.
>
> Our instructions in nt/INSTALL.W64 do not talk about pkg-config, but they
> show PKG_CONFIG_PATH used with configure:
>
>   PKG_CONFIG_PATH=/mingw64/lib/pkgconfig \
>   ./configure --prefix=/c/emacs/emacs-25 --without-imagemagick

I think it is safe to drop the line with pkg-config as Msys2 does the
right thing here.  In file /etc/profile, you find these lines
(unnecessary ones snipped):

source '/etc/msystem'
case "${MSYSTEM}" in
MINGW32)
  MINGW_MOUNT_POINT="${MINGW_PREFIX}"
  PKG_CONFIG_PATH="${MINGW_MOUNT_POINT}/lib/pkgconfig:${MINGW_MOUNT_POINT}/share/pkgconfig"
  ;;
MINGW64)
  MINGW_MOUNT_POINT="${MINGW_PREFIX}"
  PKG_CONFIG_PATH="${MINGW_MOUNT_POINT}/lib/pkgconfig:${MINGW_MOUNT_POINT}/share/pkgconfig"
  ;;
*)
  PKG_CONFIG_PATH="/usr/lib/pkgconfig:/usr/share/pkgconfig:/lib/pkgconfig"
esac

${MINGW_PREFIX} is set in /etc/msystem to /mingw32 or /mingw64.

I would suggest to put a line there saying that Dbus should be disabled
on Windows.  There was a bug report for AUCTeX where a .tex file could
not be opened because Emacs was compiled without disabling Dbus.[1,2]

Best, Arash

Footnotes: 
[1]  http://lists.gnu.org/archive/html/bug-auctex/2016-09/msg00008.html

[2]  https://sourceforge.net/p/emacsbinw64/discussion/general/thread/87c80d2f/



  reply	other threads:[~2017-01-26 19:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20  1:40 64-bit build on Windows Juanma Barranquero
2017-01-20  8:06 ` Eli Zaretskii
2017-01-21 18:29   ` Juanma Barranquero
2017-01-21 18:38     ` Eli Zaretskii
2017-01-20 13:42 ` Phillip Lord
2017-01-20 14:32   ` Óscar Fuentes
2017-01-20 15:54     ` Eli Zaretskii
2017-01-20 19:51       ` Fabrice Popineau
2017-01-21 18:25         ` Eli Zaretskii
2017-01-21 19:04           ` Fabrice Popineau
2017-01-21 19:15             ` Juanma Barranquero
2017-01-21 19:23               ` Fabrice Popineau
2017-01-21 19:30                 ` Juanma Barranquero
2017-01-21 19:55                 ` Eli Zaretskii
2017-01-21 20:40                   ` Fabrice Popineau
2017-01-22 16:50                     ` Eli Zaretskii
2017-01-22 20:38                       ` Fabrice Popineau
2017-01-22 21:22                         ` Paul Eggert
2017-01-22 21:39                           ` Fabrice Popineau
2017-01-23  3:37                           ` Eli Zaretskii
2017-01-23  3:30                         ` Eli Zaretskii
2017-01-21 18:57       ` Juanma Barranquero
2017-01-21 19:52         ` Eli Zaretskii
2017-01-21 21:15           ` Juanma Barranquero
2017-01-21 21:42           ` Juanma Barranquero
2017-01-21 22:30             ` Nikolay Kudryavtsev
2017-01-21 22:43             ` Óscar Fuentes
2017-01-22  3:38               ` Eli Zaretskii
2017-01-21 21:18         ` Juanma Barranquero
2017-01-22 17:50           ` Stephen Leake
2017-01-22 18:07             ` Eli Zaretskii
2017-01-22 20:30               ` Fabrice Popineau
2017-01-21 18:37     ` Juanma Barranquero
2017-01-26 19:05       ` Arash Esbati [this message]
2017-01-27  6:07         ` Fabrice Popineau
  -- strict thread matches above, loose matches on Subject: below --
2017-01-21 23:12 Angelo Graziosi

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=86a8adhcae.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=ofv@wanadoo.es \
    /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.