Hi Bram,

2016/1/1 Fri 23:19:41 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
> 
> > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > 1. About diff.exe
> > > > 
> > > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and 
> > > > libiconv.
> > > > Doesn't it conflict with 64-bit builds?  diff.exe bundled with the 
> > > > official
> > > > Vim 7.4 installer doesn't depend on gettext and libiconv, so I think 
> > > > using
> > > > diff.exe from gvim74.exe is safer.
> > > > 
> > > > Additionally, diff.exe is installed under the GvimExt directory, but it
> > > > should be installed to the same directory as gvim.exe.
> > > > 
> > > > https://github.com/k-takata/vim/commit/3624185df8c304669a6ad4a50d58dea6147cc0ac
> > > 
> > > It's important that the diff program can handle different line endings.
> > > There are many that won't work nicely.  The diff.exe included in the
> > > installer is an older version of GNU diffutils.
> > 
> > Sorry, I don't understand well...
> > Does the diff.exe included in the installer can handle different line 
> > endings?
> > Is the diff.exe enough for our purpose? Or do we need more up-to-date GNU
> > diffutils?
> 
> The diff.exe I have included works well.  I don't expect useful
> improvements from later versions.  When building it with another
> compiler or libraries it's possible to make it behave worse.

OK, it seems better to keep using the diff.exe included in the gvim74.exe.

Now I succeeded in creating installers on AppVeyor.
Here are the scripts:
https://github.com/k-takata/vim/tree/chrisbra-appveyor-build
and the results:
https://ci.appveyor.com/project/k-takata/vim/build/65
(You can download the installers from the ARTIFACTS button.)

Differences from the gvim74.exe are:
1. Four types of packages
  32-bit zip, installer
  64-bit zip, installer
2. Compiler version
  Windows SDK 7.1 (VC10)
3. Updated if_xx
  ActivePerl 5.22
  ActiveTcl 8.6
  LuaBinaries 5.3
  Python 2.7
  Python 3.4
  RubyInstaller 2.2
4. Updated libintl and libiconv
  https://mlocati.github.io/gettext-iconv-windows/
  Now libintl depends on libiconv.
  Additionally, 64-bit version depends on libwinpthread.

There are still some problems:
1. 64-bit installer's default directory
  64-bit installer will to install into "C:\Program Files (x86)\Vim", but
  it should be "C:\Program Files\Vim".
2. Build time
  It takes about 30 minutes that building 64- and 32-bit gvim.exe/vim.exe and
  test them all on AppVeyor.  I think it's enough to test only 64-bit gvim.exe
  when building a non-tagged commit (as we currently do).
3. gvimext.dll in zip package
  Which version of gvimext.dll should be included in the zip package?
  64- or 32-bit?  Both?

Regards,
Ken Takata

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui