On Thu, 12 Sep 2019 15:13:51 +0200
Mark Rotteveel wrote:
> On the other hand, I don't really see the point of maintaining both a
> VS2015 and a VS2017 build.
I guess there are three practical reasons...
Firebird has to be compilable across lots of different platforms so
maintaining different ve
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 u
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 b
On 12-9-2019 14:12, Adriano dos Santos Fernandes wrote:
This suggests that cmake doesn't work in the VS2015 command prompt by
default. And with some googling I found that Microsoft announced
built-in cmake support for Visual Studio 2017.
So maybe appveyor has it installed. Then I suppose you sh
12.09.2019 11:39, Mark Rotteveel wrote:
PS It is not really clear to me what the 'official' compiler for Firebird on
Windows is BTW.
VC 2010 for FB3 and VC 2017 for FB4
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-deve
On 12/09/2019 08:36, Mark Rotteveel wrote:
> On 12-9-2019 12:33, Adriano dos Santos Fernandes wrote:
>> On 12/09/2019 05:39, Mark Rotteveel wrote:
>>> When building using the Visual Studio 2015 x64 Native Tools Command
>>> Prompt, I get the following error during the build:
>>>
>>>
>>> "D:\Developm
On 12-9-2019 12:33, Adriano dos Santos Fernandes wrote:
On 12/09/2019 05:39, Mark Rotteveel wrote:
When building using the Visual Studio 2015 x64 Native Tools Command
Prompt, I get the following error during the build:
"D:\Development\project\firebird\builds\win32\msvc14\FirebirdBoot.sln"
(gpr
12.09.2019 13:12, Dimitry Sibiryakov wrote:
You forgot to include %FB_ROOT_DIR%/extern to include search path.
Or remove "re2/" directory from #include directive.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 12/09/2019 07:46, Dimitry Sibiryakov wrote:
> I also see that setenvvar.bat doesn't call vcvarsall.bat anymore
> which result in path to MSBuild is not set and build failure. Was this
> change intended?
>
>
It's the developer responsibility to call the VS scripts to set the
environment, throu
12.09.2019 12:33, Adriano dos Santos Fernandes wrote:
Are you using the latest master?
There were an error, fixed in the latest commit.
Yes. You forgot to include %FB_ROOT_DIR%/extern to include search path.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourc
I also see that setenvvar.bat doesn't call vcvarsall.bat anymore which result in path
to MSBuild is not set and build failure. Was this change intended?
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 12/09/2019 05:39, Mark Rotteveel wrote:
> When building using the Visual Studio 2015 x64 Native Tools Command
> Prompt, I get the following error during the build:
>
>
> "D:\Development\project\firebird\builds\win32\msvc14\FirebirdBoot.sln"
> (gpre_boot target) (1) ->
>
> "D:\Development\project
When building using the Visual Studio 2015 x64 Native Tools Command
Prompt, I get the following error during the build:
"D:\Development\project\firebird\builds\win32\msvc14\FirebirdBoot.sln"
(gpre_boot target) (1) ->
"D:\Development\project\firebird\builds\win32\msvc14\gpre_boot.vcxproj"
(d
13 matches
Mail list logo
