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 the tests once with
> > > > > > HUGE-console features. So perhaps we can build TINY-console with
> > > > > > MSVC
> > > > > > and HUGE-console with MingW and then run the tests with the MingW
> > > > > > binary? That way we cover more rows & columns in the build & test
> > > > > > matrix.
> > > > >
> > > > > Well, a console version is build for MSVC, since that appears to
> > > > > build
> > > > > faster than MingW. Testing happens with the gvim.exe build from MSVC,
> > > > > because first of all, the test I tried with MingW did stall on test47
> > > > > and second of all, last time I checked with the nightly windows
> > > > > builds,
> > > > > the gui version test was a lot faster than the console test.
> > > >
> > > > Running the tests in the console is different from running them in the
> > > > GUI, I think we should run both.
> > >
> > > Okay, we can do this. Will take longer however.
> >
> > I'm glad you are taking the time to make this work. Pity it's not that
> > easy. I see the current version still fails in some ways it would not
> > fail when run locally.
>
> Yes, I saw some test failures for the console version. Attached patch
> appveyor_test_fixes.diff fixes those warnings (basically by making sure,
> that VIMRUNTIME is defined) and disables 2 tests, for which I couldn't
> find out, why they failed.
> Also, this patch fixes a warning about an uninitialized variable in
> f_tan()
I don't think using "set" works with nmake:
set VIMRUNTIME=..\..\runtime && $(VIMPROG) -u NONE -U NONE -S runtest.vim $*.vim
I don't understand why you need this, Vim should be able to find the
runtime files relative to the executable.
> > It appears to get stuck in "windres". Perhaps it's showing a dialog and
> > wants you to click OK. Hmm, the "Leaving directory" indicates that
> > windres finished, thus it must be something else.
> >
> > The tiny build should probably not build GvimExt. And the console
> > version should not build it either.
>
> Hm, I don't know how to disable this. However, I left out the tiny
> version and the current version only builds normal and huge versions as
> requested.
>
> Attached patch appveyor_test_matrix does that.
--
ARTHUR: A scratch? Your arm's off!
BLACK KNIGHT: No, it isn't.
ARTHUR: Well, what's that then?
BLACK KNIGHT: I've had worse.
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
