Christian Brabandt wrote:
> On Di, 23 Feb 2016, Bram Moolenaar wrote:
>
> > The output of :version should tell you if there is a fall-back for
> > $VIMRUNTIME. If it's not set, then check the Makefile, in Make_mvc.mak
> > it's done around line 1323. However, the default is empty.
> >
> > It
On Di, 23 Feb 2016, Bram Moolenaar wrote:
> The output of :version should tell you if there is a fall-back for
> $VIMRUNTIME. If it's not set, then check the Makefile, in Make_mvc.mak
> it's done around line 1323. However, the default is empty.
>
> It should work to find the runtime files
Christian Brabandt wrote:
> >> > > On Do, 18 Feb 2016, Bram Moolenaar wrote:
> >> > >
> >> > > > Christian Brabandt wrote:
> >> > > > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> >> > > > >
> >> > > > > > Thanks. I think we should also build a console version. Since
> >> > > > > > testing
>
Am 2016-02-22 22:04, schrieb Bram Moolenaar:
Christian Brabandt wrote:
> > On Do, 18 Feb 2016, Bram Moolenaar wrote:
> >
> > > Christian Brabandt wrote:
> > > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> > > >
> > > > > Thanks. I think we should also build a console version. Since
testing
Christian Brabandt wrote:
> > > On Do, 18 Feb 2016, Bram Moolenaar wrote:
> > >
> > > > Christian Brabandt wrote:
> > > > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> > > > >
> > > > > > Thanks. I think we should also build a console version. Since
> > > > > > testing
> > > > > > appears
Hi Bram!
On Fr, 19 Feb 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Do, 18 Feb 2016, Bram Moolenaar wrote:
> >
> > > Christian Brabandt wrote:
> > > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> > > >
> > > > > Thanks. I think we should also build a console version.
Christian Brabandt wrote:
> On Do, 18 Feb 2016, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> > >
> > > > Thanks. I think we should also build a console version. Since testing
> > > > appears to the take bulk of the time we can run
On Do, 18 Feb 2016, Christian Brabandt wrote:
> And since we are at it, the console version fails:
[...]
This was the test of Mingw vim.exe 7.4.1352
Best,
Christian
--
Der Kaiser belohnte ihn königlich.
-- Heinz Erhardt
--
--
You received this message from the "vim_dev"
On Do, 18 Feb 2016, Bram Moolenaar wrote:
> Christian Brabandt wrote:
> > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> >
> > > Thanks. I think we should also build a console version. Since testing
> > > appears to the take bulk of the time we can run the tests once with
> > > HUGE-console
Christian Brabandt wrote:
> On Mi, 17 Feb 2016, Bram Moolenaar wrote:
>
> > Thanks. I think we should also build a console version. Since testing
> > appears to the take bulk of the time we can run the tests once with
> > HUGE-console features. So perhaps we can build TINY-console with MSVC
On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> Thanks. I think we should also build a console version. Since testing
> appears to the take bulk of the time we can run the tests once with
> HUGE-console features. So perhaps we can build TINY-console with MSVC
> and HUGE-console with MingW and then
Christian Brabandt wrote:
> On Mi, 17 Feb 2016, Bram Moolenaar wrote:
>
> > Thanks. Not sure if it's all that useful to build all five feature
> > sets. huge + normal for GUI and console covers quite a bit already.
> >
> > It seems the reltime test is a bit flaky. Perhaps also caused by
On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> Thanks. Not sure if it's all that useful to build all five feature
> sets. huge + normal for GUI and console covers quite a bit already.
>
> It seems the reltime test is a bit flaky. Perhaps also caused by giving
> AppVeyor so much work.
Okay,
Christian Brabandt wrote:
> Hi Bram!
>
> On Mo, 15 Feb 2016, Bram Moolenaar wrote:
>
> > This should not be part of the daily build but the one that's triggered
> > by a submit. Then we get a warning email five minutes later.
>
> That's what I meant.
>
> >
> > The one we currently have
Hi,
2016/2/17 Wed 18:00:10 UTC+9 Ken Takata wrote:
> I don't think the following hunk should be applied:
>
> --- a/src/os_win32.c
> +++ b/src/os_win32.c
> @@ -5175,8 +5175,10 @@ mch_stop_job(job_T *job, char_u *how)
> return TerminateProcess(job->jv_proc_info.hProcess, 0) ? OK : FAIL;
> > However, since this builds MSVC and Mingw gvim and vim.exe for
> > FEATURES=tiny, small, normal, big and huge and runs the test it will
> > take a while to finish, probably around 50 Minutes.
> >
> > Feedback appreciated.
>
> I don't think the following hunk should be applied:
> MinGW is
Hi Christian,
2016/2/17 Wed 17:35:20 UTC+9 Christian Brabandt wrote:
> Hi Bram!
>
> On Mo, 15 Feb 2016, Bram Moolenaar wrote:
>
> > This should not be part of the daily build but the one that's triggered
> > by a submit. Then we get a warning email five minutes later.
>
> That's what I meant.
Hi Bram!
On Mo, 15 Feb 2016, Bram Moolenaar wrote:
> This should not be part of the daily build but the one that's triggered
> by a submit. Then we get a warning email five minutes later.
That's what I meant.
>
> The one we currently have only tests the GUI. We should at least have
> one
On 15/02/2016 12:09, Bram Moolenaar wrote:
Mike Williams wrote:
Come on guys, if you're fixing code dependent on pp defines, check with
them both defined and undefined that everything still builds and links.
It appears Appveyor only builds one specific setup. It would be useful
to run a few
Christian Brabandt wrote:
> On Mo, 15 Feb 2016, Bram Moolenaar wrote:
> >
> > Mike Williams wrote:
> >
> > > On 15/02/2016 08:10, Axel Bender wrote:
> > > > Compiling vim.exe (Windows 7 64-bit, MinGW 64-bit) fails with:
> > > >
> > > > gcc -c -Iproto -DWIN32 -DWINVER=0x0500
Hi Bram!
On Mo, 15 Feb 2016, Bram Moolenaar wrote:
>
> Mike Williams wrote:
>
> > On 15/02/2016 08:10, Axel Bender wrote:
> > > Compiling vim.exe (Windows 7 64-bit, MinGW 64-bit) fails with:
> > >
> > > gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
> > > -DHAVE_PATHDEF
Mike Williams wrote:
> On 15/02/2016 08:10, Axel Bender wrote:
> > Compiling vim.exe (Windows 7 64-bit, MinGW 64-bit) fails with:
> >
> > gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF
> > -DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT
> >
On 15/02/2016 08:10, Axel Bender wrote:
Compiling vim.exe (Windows 7 64-bit, MinGW 64-bit) fails with:
gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF
-DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT
-DFEAT_OLE -DFEAT_CSCOPE -DFEAT_MBYTE -DFEA
Compiling vim.exe (Windows 7 64-bit, MinGW 64-bit) fails with:
gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF
-DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT
-DFEAT_OLE -DFEAT_CSCOPE -DFEAT_MBYTE -DFEA
T_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV
24 matches
Mail list logo