 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
After reading Bug #48 on github, I tried to build the 64 bit version
from git (commit #4983507) on Windows 10 so that I could compare it with
the official 3.7.0.0 release. Unfortunately, it refuses to build with
Visual Studio 2015 Community Edition.
I followed the compile instructions in /windows/readme.html to the
letter. In the same directory as readme.html, the file readme.txt states,
> The Visual Studio 2010 projects should also build fine in Visual Studio 2015
> after automatic conversion, as has been tested with the Visual Studio 2015
> Community edition.
That is NOT the case. While the conversion process did complete
successfully, actually trying to build POV-Ray failed. There were MANY
warnings, but the errors that stopped the build were as follows:
Severity Code Description Project File Line
Error C2440 'initializing': cannot convert from 'overloaded-function' to
'const pov::Sys1' povbackend
C:\src\povray\source\backend\vm\fnpovfpu.cpp 491
Error C2668 'acosh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_expressions.cpp 754
Error C2668 'asinh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_expressions.cpp 757
Error C2668 'atanh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_expressions.cpp 760
Error C2668 'asinh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_functions.cpp 1203
Error C2668 'acosh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_functions.cpp 1206
Error C2668 'atanh': ambiguous call to overloaded function povparser
C:\src\povray\source\parser\parser_functions.cpp 1209
Error LNK1181 cannot open input file
'C:\src\povray\windows\vs10\bin64\lib\povbackend64.lib' GUI
C:\src\povray\windows\vs10\LINK 1
Todd
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 15.11.2015 um 20:30 schrieb Todd Carnes:
> After reading Bug #48 on github, I tried to build the 64 bit version
> from git (commit #4983507) on Windows 10 so that I could compare it with
> the official 3.7.0.0 release. Unfortunately, it refuses to build with
> Visual Studio 2015 Community Edition.
I'll have a look at it; for the time being, please test with commit
#a371c26.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-11-15 11:57, clipka wrote:
> Am 15.11.2015 um 20:30 schrieb Todd Carnes:
>> After reading Bug #48 on github, I tried to build the 64 bit version
>> from git (commit #4983507) on Windows 10 so that I could compare it with
>> the official 3.7.0.0 release. Unfortunately, it refuses to build with
>> Visual Studio 2015 Community Edition.
>
> I'll have a look at it; for the time being, please test with commit
> #a371c26.
>
Ok. I will try that.
Todd
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-11-15 12:02, Todd Carnes wrote:
> On 2015-11-15 11:57, clipka wrote:
>> Am 15.11.2015 um 20:30 schrieb Todd Carnes:
>>> After reading Bug #48 on github, I tried to build the 64 bit version
>>> from git (commit #4983507) on Windows 10 so that I could compare it with
>>> the official 3.7.0.0 release. Unfortunately, it refuses to build with
>>> Visual Studio 2015 Community Edition.
>>
>> I'll have a look at it; for the time being, please test with commit
>> #a371c26.
>>
> Ok. I will try that.
>
> Todd
By the way, is it better to report bugs here or on Github?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 15.11.2015 um 21:10 schrieb Todd Carnes:
> On 2015-11-15 12:02, Todd Carnes wrote:
>> On 2015-11-15 11:57, clipka wrote:
>>> Am 15.11.2015 um 20:30 schrieb Todd Carnes:
>>>> After reading Bug #48 on github, I tried to build the 64 bit version
>>>> from git (commit #4983507) on Windows 10 so that I could compare it
>>>> with
>>>> the official 3.7.0.0 release. Unfortunately, it refuses to build with
>>>> Visual Studio 2015 Community Edition.
>>>
>>> I'll have a look at it; for the time being, please test with commit
>>> #a371c26.
>>>
>> Ok. I will try that.
>>
>> Todd
>
> By the way, is it better to report bugs here or on Github?
Definitely GitHub, as it comes with some essential mechanisms for
tracking, categorizing, following up, etc.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-11-15 11:57, clipka wrote:
> I'll have a look at it; for the time being, please test with commit
> #a371c26.
Commit# a371c26 compiled without issue.
Thank you.
Todd
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
