[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MS-Windows build using Posix configury

From: Dani Moncayo
Subject: Re: MS-Windows build using Posix configury
Date: Thu, 16 May 2013 19:17:04 +0200

>>>>      It is always preferable to use --prefix to configure Emacs for
>>>>      some specific location of its installed tree; the default
>>>>      /usr/local is not suitable for Windows.
>>> What's going to happen if I disregard this recommendation? Will build
>>> fail?
>> No, I don't think the build will fail.  --prefix is only important for
>> "make install".
> If the installation will fail, maybe the prefix should default to some
> reasonable directory within the Emacs tree. Would it be hard to do that?

"/usr/local" is a valid directory specification in MSYS, so I don't
see why the installation should fail.   Omitting the --prefix in "make
install" should simply install Emacs under that directory.

>>>>   (We recommend that you refrain from installing the MSYS Texinfo
>>>>   package, which is part of msys-base, because it might produce mixed
>>>>   EOL format when installing Info files.  Instead, install the MinGW
>>>>   port of Texinfo, see the ezwinports URL below.)
>>> How am I supposed to do that? MinGW-Get installer only allows me to
>>> check or uncheck the whole "MSYS Base" category, not the individual
>>> packages.
>> I don't know; I don't use mingw-get.  Perhaps uninstall the Texinfo
>> package after installing msys-base (assuming mingw-get has an
>> uninstall option that can uninstall a single package)?  If that
>> doesn't work, I suggest to ask on the mingw-users mailing list, the
>> developer of mingw-get is reading that.
> Indeed, "mingw-get remove msys-texinfo" seems to have done that.
> If having to remove that package manually (as opposed to not installing it)
> is going to be a common situation, maybe INSTALL.MSYS should reflect that.

The Texinfo version that comes with MSYS works just fine, AFAICT.
There is only a minor issue with ^M characters that get inserted in
the info directory in certain situations.

So, I don't see a big need for having to uninstall that Texinfo and
manually install the other (the Windows-native) one.

Dani Moncayo

reply via email to

[Prev in Thread] Current Thread [Next in Thread]