On 12-9-2019 14:59, Dimitry Sibiryakov wrote:
12.09.2019 14:29, Mark Rotteveel wrote:
So maybe appveyor has it installed. Then I suppose you should install
it.
Looks like it. Or I will just always use VS2017 for my builds from now
on.
If core developers decided that VS 2017 is the only usable compiler
for Firebird 4 they must remove builds for older versions and clean up
workarounds for them from whole codebase.
You also need to install sed to be able to build Firebird on Windows, so
installing cmake if you want to build on VS2015 isn't a stretch. On the
other hand, I don't really see the point of maintaining both a VS2015
and a VS2017 build.
I was just used to building with VS2015, because a few months ago
building with VS2017 didn't work (or at least: not on my machine).
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
