Hi Bram, 2016/1/11 Mon 6:22:52 UTC+9 Bram Moolenaar wrote: > Christian Brabandt wrote: > > > > > On So, 10 Jan 2016, Bram Moolenaar wrote: > > > > > > > > > > Ken Takata wrote: > > > > > > > > > > > Hi Bram and all, > > > > > > > > > > > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote: > > > > > > > Can we please gather the complete, step-by-step instructions? > > > > > > > Probably > > > > > > > the best place for this is src/INSTALLpc.txt. > > > > > > > > > > > > I wrote it. Please review. > > > > > > > > > > Great, thanks. Let me include this now. We can make further > > > > > improvements from there. > > > > > > > > > > > I also updated the appveyor script: > > > > > > https://github.com/k-takata/vim/tree/chrisbra-appveyor-build > > > > > > > > > > Where do we see the output of it? Does it produce the self-installing > > > > > executable similar to what I made: > > > > > ftp://ftp.vim.org/pub/vim/pc/gvim74-1024.exe > > > > > That follows the instructions in the toplevel Makefile. > > > > > > > > I think it is here: > > > > https://ci.appveyor.com/project/k-takata/vim/history e.g. last one > > > > seems > > > > to be: https://ci.appveyor.com/project/k-takata/vim/build/81 then click > > > > on an arch build and then on artifacts. I think the compiled builds are > > > > then uploaded back there: https://github.com/k-takata/vim/releases > > > > > > Thanks. It builds lots of stuff, taking a lot of time. But we would > > > only need to do this once a day, if there are changes. > > > > > > It does appear to use the distributed nsis/gvim.nsi file. > > > > It only takes about half an-hour. And I think, it is really nice, to > > have the compiled binaries available back at github.com/vim/vim/releases > > So we could have users install whatever patch level they want. > > > > > > > > > The instructions to build the binaries are here: > > > > https://github.com/k-takata/vim/blob/chrisbra-appveyor-build/appveyor.yml > > > > and especially > > > > https://github.com/k-takata/vim/blob/chrisbra-appveyor-build/src/appveyor.bat > > > > > > It contains quite a few version numbers. This will require regular > > > maintenance. > > > > Yes. The good thing is, it is build (and tested!) automatically, and we > > get notifications for failures, so we notice as soon as a patch (or > > upstream) breaks something. > > Yes, but who is going to do that? For the Vim code, if something breaks > it's most likely a patch I just submitted. However, for this build > script it depends on what other projects are doing, can happen any time.
I understand your concern. But I don't think we need to update the scripts frequently, maybe once or twice a year? > I rather have someone other than me maintain this. And run it > separately from the existing continuous builds. Then, how about creating a special repository for building Win32 installer? E.g. https://github.com/vim/vim-win32-installer The problem is how to sync with the main repository (vim/vim). It would be good if we could change the Travis CI setting of vim/vim and make it automatically push a new change to the special repository. (I don't know how to do it.) 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
