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:\Development\project\firebird\builds\win32\msvc14\FirebirdBoot.sln"
>>> (gpre_boot target) (1) ->
>>>
>>> "D:\Development\project\firebird\builds\win32\msvc14\gpre_boot.vcxproj"
>>> (default target) (2) ->
>>>
>>> "D:\Development\project\firebird\builds\win32\msvc14\common.vcxproj"
>>> (default target) (3) ->
>>>         (Lib target) ->
>>>           LINK : fatal error LNK1181: cannot open input file
>>> '../../../extern/re2/builds/x64\Release\re2.lib'
>>> [D:\Development\project\firebird\builds\win32\msvc14\common.vcxproj]
>>>
>>> Using the x64 Native Tools Command Prompt for VS 2017 works. What
>>> could be the problem with the VS 2015 build?
>>>
>>
>> Are you using the latest master?
>>
>> There were an error, fixed in the latest commit.
>>
>> AppVeyor build is working:
>> https://ci.appveyor.com/project/FirebirdSQL/firebird/builds/27256941
>
> I have synced my fork today, so I am using the HEAD of master on
> FirebirdSQL/firebird.
>
> Interestingly enough, re-running it after the successful build using
> the VS2017 command prompt, it now works. However, looking at the
> timestamp of the files in extern\re2\builds, it didn't rebuild re2,
> but used the output of my previous VS2017 build. This would indicate
> that the VS2015 build does not compile re2.
>
> Logging the output of make_boot.bat (using make_boot > make_boot.log
> 2>&1) gives me:
>
> Building re2...
> 'cmake' is not recognized as an internal or external command,
> operable program or batch file.
> 'cmake' is not recognized as an internal or external command,
> operable program or batch file.
> 'cmake' is not recognized as an internal or external command,
> operable program or batch file.
> Extracting pre-built zlib
>
> 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 should install it.

> As an aside, this also suggests that clean_all.bat isn't cleaning all
> as it should, and this hides possible build issues.

Does the others extern libraries are cleaned?

Is re2 not cleaned at all or only when cmake is not present?


Adriano



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to