For the people who do not want to bother with git, Hgpovray is now
available as sources


https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30

> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30

More works on the agenda :

http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38

Post a reply to this message

Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
> For the people who do not want to bother with git, Hgpovray is now
> available as sources
> 
> 
Latest version so far:

https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade

> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade


> More works on the agenda :
> 
> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
>

Post a reply to this message

hi,

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
> > For the people who do not want to bother with git, Hgpovray is now
> > available as sources
> Latest version so far:
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade

downloaded the .tar.gz version and run into trouble -- make error when
compilation gets to the maths/spline code.  log posted in p.binaries.misc.


regards, jr.

Post a reply to this message

Le 12/09/2018 à 23:50, jr a écrit :
> hi,
> 
> Le_Forgeron <jgr### [at] freefr> wrote:
>> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
>>> For the people who do not want to bother with git, Hgpovray is now
>>> available as sources
>> Latest version so far:
> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
> 
> downloaded the .tar.gz version and run into trouble -- make error when
> compilation gets to the maths/spline code.  log posted in p.binaries.misc.

What age is your compiler ?

I have compiled it with g++ 7, modern clang and icc (intel).

Post a reply to this message

hi,

Le Forgeron <jgr### [at] freefr> wrote:
> Le 12/09/2018 à 23:50, jr a écrit :
> > downloaded the .tar.gz version and run into trouble -- make error when
> > compilation gets to the maths/spline code.  log posted in p.binaries.misc.
>
> What age is your compiler ?

4.8.2.  :-)

however, is that not a "red herring"?  I would expect './configure' to fail if
the s/ware is .. not modern enough.

> I have compiled it with g++ 7, modern clang and icc (intel).



regards, jr.

Post a reply to this message

Am 13.09.2018 um 11:29 schrieb jr:
> hi,
> 
> Le Forgeron <jgr### [at] freefr> wrote:
>> Le 12/09/2018 à 23:50, jr a écrit :
>>> downloaded the .tar.gz version and run into trouble -- make error when
>>> compilation gets to the maths/spline code.  log posted in p.binaries.misc.
>>
>> What age is your compiler ?
> 
> 4.8.2.  :-)

For the records, GCC 4.8.2 is feature-complete with respect to C++11.

> however, is that not a "red herring"?  I would expect './configure' to fail if
> the s/ware is .. not modern enough.

The question isn't that offbeat; as a matter of fact, the only reliable
way to test whether any given compiler will compile a given program is
to actually try compiling that program.

Case in point: gcc 4.8.2 (or, more precisely, the standard header files
that came with it), despite claiming full C++11 compliance, actually
isn't, due to a couple of bugs in the implementation of std::vector<T>.

And that seems to be exactly what you are seeing; I couldn't find a bug
report matching the /exact/ symptoms, but the error messages point to a
a non-standard-compliant interface of `std::vector<T>::insert`, and
there are bug reports of multiple other non-compliances of
`std::vector<T>`, such as this one:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55817

Judging from when the other bugs were fixed, you'll probably need gcc
4.9 or later.

Post a reply to this message

hi,

clipka <ano### [at] anonymousorg> wrote:
> Am 13.09.2018 um 11:29 schrieb jr:
> > Le Forgeron <jgr### [at] freefr> wrote:
> >> Le 12/09/2018 à 23:50, jr a écrit :
> >>> downloaded the .tar.gz version and run into trouble -- make error when
> >>> compilation gets to the maths/spline code.  log posted in p.binaries.misc.
> >> What age is your compiler ?
> > 4.8.2.  :-)
>
> For the records, GCC 4.8.2 is feature-complete with respect to C++11.
> ...
> Case in point: gcc 4.8.2 (or, more precisely, the standard header files
> that came with it), despite claiming full C++11 compliance, actually
> isn't, due to a couple of bugs in the implementation of std::vector<T>.
>
> And that seems to be exactly what you are seeing; I couldn't find a bug
> report matching the /exact/ symptoms, but the error messages point to a
> a non-standard-compliant interface of `std::vector<T>::insert`, and
> there are bug reports of multiple other non-compliances of
> `std::vector<T>`, such as this one:
>
>     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55817
>
> Judging from when the other bugs were fixed, you'll probably need gcc
> 4.9 or later.

wow.  thank you very much for digging in to the details, appreciated.  update it
is then (well, near future :-))


regards, jr.

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
> > For the people who do not want to bother with git, Hgpovray is now
> > available as sources
> >
> >
> Latest version so far:
>
> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
>
> > https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
>
>
> > More works on the agenda :
> >
> > http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> >

Bonjour !

I just tried to build the latest HG-Pov I could find which seems to be that
Bigarade, right? Using MS VS2015,
Here is VS2015 build output:

1>------ Début de la génération : Projet : vfewin, Configuration : Debug x64
------
2>------ Début de la génération : Projet : rtrsupport, Configuration : Debug x64
------
3>------ Début de la génération : Projet : povbackend, Configuration : Debug x64
------
4>------ Début de la génération : Projet : povbase, Configuration : Debug x64
------
5>------ Début de la génération : Projet : povfrontend, Configuration : Debug
x64 ------
6>------ Génération ignorée : Projet : boost_date_time, Configuration : Debug
x64 ------
6>Projet non sélectionné dans le cadre d'une génération pour cette configuration
de solution
7>------ Début de la génération : Projet : povcore, Configuration : Debug x64
------
8>------ Début de la génération : Projet : povparser, Configuration : Debug x64
------
1>  vfesession.cpp
2>  vidcapimpl.cpp
3>  boundingtask.cpp
5>  povmain.cpp
4>  colour.cpp
7>  bounding.cpp
8>  parser.cpp
7>  texture.cpp
4>  metadata.cpp
3>..\..\source\backend\bounding\boundingtask.cpp(91): warning C4267: 'return' :
conversion de 'size_t' en 'unsigned int', perte possible de données
3>..\..\source\backend\bounding\boundingtask.cpp(162): warning C4267: '=' :
conversion de 'size_t' en 'unsigned int', perte possible de données
3>..\..\source\backend\bounding\boundingtask.cpp(163): warning C4267: '=' :
conversion de 'size_t' en 'unsigned int', perte possible de données
3>..\..\source\backend\bounding\boundingtask.cpp(178): warning C4267: '=' :
conversion de 'size_t' en 'unsigned int', perte possible de données
3>..\..\source\backend\bounding\boundingtask.cpp(179): warning C4267: '=' :
conversion de 'size_t' en 'unsigned int', perte possible de données
3>  povray.cpp
7>  scenedata.cpp
5>povmain.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
opÚration de lien utilisant cette bibliothÞque
5>  povfrontend.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povfrontend64d.lib
3>..\..\source\backend\povray.cpp(515): warning C4267: 'argument' : conversion
de 'size_t' en 'int', perte possible de données
3>  benchmark.cpp
3>  renderbackend.cpp
7>  tracethreaddata.cpp
8>..\..\source\parser\parser.cpp(9673): warning C4267: 'argument' : conversion
de 'size_t' en 'int', perte possible de données
8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12022): error C2146: erreur de syntaxe :
absence de ';' avant l'identificateur 'idx1'
4>  mathutil.cpp
8>..\..\source\parser\parser.cpp(12022): error C2065: 'idx1' : identificateur
non déclaré
4>  Génération de code en cours...
8>..\..\source\parser\parser.cpp(12023): error C2065: 'ssize_t' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12023): error C2146: erreur de syntaxe :
absence de ';' avant l'identificateur 'idx2'
8>..\..\source\parser\parser.cpp(12023): error C2065: 'idx2' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx1' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx2' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12026): error C2065: 'idx2' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12028): error C2065: 'idx2' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx1' : identificateur
non déclaré
8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx2' : identificateur
non déclaré
4>  jpeg.cpp
8>  parser_strings.cpp
7>  box.cpp
3>  scene.cpp
7>  Génération de code en cours...
4>..\..\source\base\image\jpeg.cpp(502): warning C4267: 'argument' : conversion
de 'size_t' en 'unsigned int', perte possible de données
8>..\..\source\parser\parser_strings.cpp(479): error C2131: l'expression n'a pas
été évaluée en constante
8>  ..\..\source\parser\parser_strings.cpp(479): note: échec en raison
d'arguments non constants ou d'une référence à un symbole non constant
8>  ..\..\source\parser\parser_strings.cpp(479): note: voir l'utilisation de
'this'
8>..\..\source\parser\parser_strings.cpp(708): warning C4267: '=' : conversion
de 'size_t' en 'int', perte possible de données
8>..\..\source\parser\parser_strings.cpp(1176): warning C4267: '=' : conversion
de 'size_t' en 'int', perte possible de données
8>  parser_tokenizer.cpp
3>  Génération de code en cours...
8>..\..\source\parser\parser_tokenizer.cpp(1514): warning C4267: '=' :
conversion de 'size_t' en 'int', perte possible de données
7>bounding.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
opÚration de lien utilisant cette bibliothÞque
4>  png.cpp
8>..\..\source\parser\parser_tokenizer.cpp(3915): warning C4267: '=' :
conversion de 'size_t' en 'int', perte possible de données
2>  vidcap.cpp
8>..\..\source\parser\parser_tokenizer.cpp(3935): warning C4267: '=' :
conversion de 'size_t' en 'int', perte possible de données
8>  Génération de code en cours...
3>  povbackend.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbackend64d.lib
7>  povcore.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povcore64d.lib
4>  Génération de code en cours...
4>timer.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
opÚration de lien utilisant cette bibliothÞque
4>mathutil.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
opÚration de lien utilisant cette bibliothÞque
4>  povbase.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbase64d.lib
2>  rtrsupport.cpp
1>  vfewin.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\vfe64d.lib
2>  Génération de code en cours...
2>vidcap.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
opÚration de lien utilisant cette bibliothÞque
2>  rtrsupport.vcxproj ->
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\rtrsupport64d.lib
9>------ Génération ignorée : Projet : tests, Configuration : Debug x64 ------
9>Projet non sélectionné dans le cadre d'une génération pour cette configuration
de solution
10>------ Début de la génération : Projet : GUI, Configuration : Debug x64
------
11>------ Génération ignorée : Projet : console, Configuration : Debug x64
------
11>Projet non sélectionné dans le cadre d'une génération pour cette
configuration de solution
10>  pvbitmap.cpp
10>  pvdialog.cpp
10>  pvdisplay.cpp
10>  pvedit.cpp
10>..\pvedit.cpp(301): warning C4267: '+=' : conversion de 'size_t' en 'int',
perte possible de données
10>  pvengine.cpp
10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(1544): warning
C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est déclarée
10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(3190): warning
C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est déclarée
10>..\pvengine.cpp(498): warning C4838: la conversion de 'int' en 'WORD'
requiert une conversion restrictive
10>..\pvengine.cpp(1721): warning C4477: 'sprintf' : la chaîne de format '%p'
nécessite un argument de type 'void *', mais l'argument variadique 2 est de type
'DWORD64'
10>..\pvengine.cpp(5152): warning C4996: 'GetVersionExA': a été déclaré
déconseillé
10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
voir la déclaration de 'GetVersionExA'
10>..\pvengine.cpp(5608): warning C4267: '=' : conversion de 'size_t' en
'unsigned int', perte possible de données
10>..\pvengine.cpp(5787): warning C4267: '=' : conversion de 'size_t' en
'unsigned int', perte possible de données
10>..\pvengine.cpp(5719): warning C4996: 'GetVersionExA': a été déclaré
déconseillé
10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
voir la déclaration de 'GetVersionExA'
10>  pvfiles.cpp
10>  pvfrontend.cpp
10>  pvguiext.cpp
10>  pvmem.cpp
10>  pvmenu.cpp
10>  pvmisc.cpp
10>..\pvmisc.cpp(223): warning C4838: la conversion de 'int' en 'unsigned int'
requiert une conversion restrictive
10>  pvtext.cpp
10>  pvupdate.cpp
10>..\pvupdate.cpp(166): warning C4996: 'GetVersionExA': a été déclaré
déconseillé
10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
voir la déclaration de 'GetVersionExA'
10>  Génération de code en cours...
10>LINK : fatal error LNK1104: impossible d'ouvrir le fichier
'C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povparser64d.lib'
========== Génération : 6 a réussi, 2 a échoué, 15 mis à jour, 3 a été ignoré
==========

Post a reply to this message

Le 09/05/2020 à 14:49, Mr a écrit :
> Le_Forgeron <jgr### [at] freefr> wrote:
>> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
>>> For the people who do not want to bother with git, Hgpovray is now
>>> available as sources
>>>
>>>
>> Latest version so far:
>>
>> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
>>
>>> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
>>
>>
>>> More works on the agenda :
>>>
>>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
>>>
> 
> Bonjour !
> 
> I just tried to build the latest HG-Pov I could find which seems to be that
> Bigarade, right? Using MS VS2015,
> Here is VS2015 build output:
> 
> 1>------ Début de la génération : Projet : vfewin, Configuration : Debug x64
> ------
> 2>------ Début de la génération : Projet : rtrsupport, Configuration : Debug
x64
> ------
> 3>------ Début de la génération : Projet : povbackend, Configuration : Debug
x64
> ------
> 4>------ Début de la génération : Projet : povbase, Configuration : Debug x64
> ------
> 5>------ Début de la génération : Projet : povfrontend, Configuration : Debug
> x64 ------
> 6>------ Génération ignorée : Projet : boost_date_time, Configuration : Debug
> x64 ------
> 6>Projet non sélectionné dans le cadre d'une génération pour cette configuration
> de solution
> 7>------ Début de la génération : Projet : povcore, Configuration : Debug x64
> ------
> 8>------ Début de la génération : Projet : povparser, Configuration : Debug
x64
> ------
> 1>  vfesession.cpp
> 2>  vidcapimpl.cpp
> 3>  boundingtask.cpp
> 5>  povmain.cpp
> 4>  colour.cpp
> 7>  bounding.cpp
> 8>  parser.cpp
> 7>  texture.cpp
> 4>  metadata.cpp
> 3>..\..\source\backend\bounding\boundingtask.cpp(91): warning C4267: 'return' :
> conversion de 'size_t' en 'unsigned int', perte possible de données
> 3>..\..\source\backend\bounding\boundingtask.cpp(162): warning C4267: '=' :
> conversion de 'size_t' en 'unsigned int', perte possible de données
> 3>..\..\source\backend\bounding\boundingtask.cpp(163): warning C4267: '=' :
> conversion de 'size_t' en 'unsigned int', perte possible de données
> 3>..\..\source\backend\bounding\boundingtask.cpp(178): warning C4267: '=' :
> conversion de 'size_t' en 'unsigned int', perte possible de données
> 3>..\..\source\backend\bounding\boundingtask.cpp(179): warning C4267: '=' :
> conversion de 'size_t' en 'unsigned int', perte possible de données
> 3>  povray.cpp
> 7>  scenedata.cpp
> 5>povmain.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> opÚration de lien utilisant cette bibliothÞque
> 5>  povfrontend.vcxproj ->
>
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povfrontend64d.lib
> 3>..\..\source\backend\povray.cpp(515): warning C4267: 'argument' : conversion
> de 'size_t' en 'int', perte possible de données
> 3>  benchmark.cpp
> 3>  renderbackend.cpp
> 7>  tracethreaddata.cpp
> 8>..\..\source\parser\parser.cpp(9673): warning C4267: 'argument' : conversion
> de 'size_t' en 'int', perte possible de données
> 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12022): error C2146: erreur de syntaxe :
> absence de ';' avant l'identificateur 'idx1'
> 4>  mathutil.cpp
> 8>..\..\source\parser\parser.cpp(12022): error C2065: 'idx1' : identificateur
> non déclaré
> 4>  Génération de code en cours...
> 8>..\..\source\parser\parser.cpp(12023): error C2065: 'ssize_t' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12023): error C2146: erreur de syntaxe :
> absence de ';' avant l'identificateur 'idx2'
> 8>..\..\source\parser\parser.cpp(12023): error C2065: 'idx2' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx1' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx2' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12026): error C2065: 'idx2' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12028): error C2065: 'idx2' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx1' : identificateur
> non déclaré
> 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx2' : identificateur
> non déclaré
> 4>  jpeg.cpp
> 8>  parser_strings.cpp
> 7>  box.cpp
> 3>  scene.cpp
> 7>  Génération de code en cours...
> 4>..\..\source\base\image\jpeg.cpp(502): warning C4267: 'argument' : conversion
> de 'size_t' en 'unsigned int', perte possible de données
> 8>..\..\source\parser\parser_strings.cpp(479): error C2131: l'expression n'a pas
> été évaluée en constante
> 8>  ..\..\source\parser\parser_strings.cpp(479): note: échec en raison
> d'arguments non constants ou d'une référence à un symbole non constant
> 8>  ..\..\source\parser\parser_strings.cpp(479): note: voir l'utilisation de
> 'this'
> 8>..\..\source\parser\parser_strings.cpp(708): warning C4267: '=' : conversion
> de 'size_t' en 'int', perte possible de données
> 8>..\..\source\parser\parser_strings.cpp(1176): warning C4267: '=' : conversion
> de 'size_t' en 'int', perte possible de données
> 8>  parser_tokenizer.cpp
> 3>  Génération de code en cours...
> 8>..\..\source\parser\parser_tokenizer.cpp(1514): warning C4267: '=' :
> conversion de 'size_t' en 'int', perte possible de données
> 7>bounding.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> opÚration de lien utilisant cette bibliothÞque
> 4>  png.cpp
> 8>..\..\source\parser\parser_tokenizer.cpp(3915): warning C4267: '=' :
> conversion de 'size_t' en 'int', perte possible de données
> 2>  vidcap.cpp
> 8>..\..\source\parser\parser_tokenizer.cpp(3935): warning C4267: '=' :
> conversion de 'size_t' en 'int', perte possible de données
> 8>  Génération de code en cours...
> 3>  povbackend.vcxproj ->
>
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbackend64d.lib
> 7>  povcore.vcxproj ->
> C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povcore64d.lib
> 4>  Génération de code en cours...
> 4>timer.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> opÚration de lien utilisant cette bibliothÞque
> 4>mathutil.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> opÚration de lien utilisant cette bibliothÞque
> 4>  povbase.vcxproj ->
> C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbase64d.lib
> 2>  rtrsupport.cpp
> 1>  vfewin.vcxproj ->
> C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\vfe64d.lib
> 2>  Génération de code en cours...
> 2>vidcap.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> opÚration de lien utilisant cette bibliothÞque
> 2>  rtrsupport.vcxproj ->
>
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\rtrsupport64d.lib
> 9>------ Génération ignorée : Projet : tests, Configuration : Debug x64 ------
> 9>Projet non sélectionné dans le cadre d'une génération pour cette configuration
> de solution
> 10>------ Début de la génération : Projet : GUI, Configuration : Debug x64
> ------
> 11>------ Génération ignorée : Projet : console, Configuration : Debug x64
> ------
> 11>Projet non sélectionné dans le cadre d'une génération pour cette
> configuration de solution
> 10>  pvbitmap.cpp
> 10>  pvdialog.cpp
> 10>  pvdisplay.cpp
> 10>  pvedit.cpp
> 10>..\pvedit.cpp(301): warning C4267: '+=' : conversion de 'size_t' en 'int',
> perte possible de données
> 10>  pvengine.cpp
> 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(1544): warning
> C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est déclarée
> 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(3190): warning
> C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est déclarée
> 10>..\pvengine.cpp(498): warning C4838: la conversion de 'int' en 'WORD'
> requiert une conversion restrictive
> 10>..\pvengine.cpp(1721): warning C4477: 'sprintf' : la chaîne de format '%p'
> nécessite un argument de type 'void *', mais l'argument variadique 2 est de type
> 'DWORD64'
> 10>..\pvengine.cpp(5152): warning C4996: 'GetVersionExA': a été déclaré
> déconseillé
> 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> voir la déclaration de 'GetVersionExA'
> 10>..\pvengine.cpp(5608): warning C4267: '=' : conversion de 'size_t' en
> 'unsigned int', perte possible de données
> 10>..\pvengine.cpp(5787): warning C4267: '=' : conversion de 'size_t' en
> 'unsigned int', perte possible de données
> 10>..\pvengine.cpp(5719): warning C4996: 'GetVersionExA': a été déclaré
> déconseillé
> 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> voir la déclaration de 'GetVersionExA'
> 10>  pvfiles.cpp
> 10>  pvfrontend.cpp
> 10>  pvguiext.cpp
> 10>  pvmem.cpp
> 10>  pvmenu.cpp
> 10>  pvmisc.cpp
> 10>..\pvmisc.cpp(223): warning C4838: la conversion de 'int' en 'unsigned int'
> requiert une conversion restrictive
> 10>  pvtext.cpp
> 10>  pvupdate.cpp
> 10>..\pvupdate.cpp(166): warning C4996: 'GetVersionExA': a été déclaré
> déconseillé
> 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> voir la déclaration de 'GetVersionExA'
> 10>  Génération de code en cours...
> 10>LINK : fatal error LNK1104: impossible d'ouvrir le fichier
>
'C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povparser64d.lib'
> ========== Génération : 6 a réussi, 2 a échoué, 15 mis à jour, 3 a été
ignoré
> ==========
> 
> 
> 
> 

you can fix the ssize_t error by defining it as a signed integer such as
int_least32_t

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 09/05/2020 à 14:49, Mr a écrit :
> > Le_Forgeron <jgr### [at] freefr> wrote:
> >> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
> >>> For the people who do not want to bother with git, Hgpovray is now
> >>> available as sources
> >>>
> >>>
> >> Latest version so far:
> >>
> >> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
> >>
> >>> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
> >>
> >>
> >>> More works on the agenda :
> >>>
> >>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> >>>
> >
> > Bonjour !
> >
> > I just tried to build the latest HG-Pov I could find which seems to be that
> > Bigarade, right? Using MS VS2015,
> > Here is VS2015 build output:
> >
> > 1>------ Début de la génération : Projet : vfewin, Configuration : Debug x64
> > ------
> > 2>------ Début de la génération : Projet : rtrsupport, Configuration : Debug
x64
> > ------
> > 3>------ Début de la génération : Projet : povbackend, Configuration : Debug
x64
> > ------
> > 4>------ Début de la génération : Projet : povbase, Configuration : Debug
x64
> > ------
> > 5>------ Début de la génération : Projet : povfrontend, Configuration :
Debug
> > x64 ------
> > 6>------ Génération ignorée : Projet : boost_date_time, Configuration :
Debug
> > x64 ------
> > 6>Projet non sélectionné dans le cadre d'une génération pour cette
configuration
> > de solution
> > 7>------ Début de la génération : Projet : povcore, Configuration : Debug
x64
> > ------
> > 8>------ Début de la génération : Projet : povparser, Configuration : Debug
x64
> > ------
> > 1>  vfesession.cpp
> > 2>  vidcapimpl.cpp
> > 3>  boundingtask.cpp
> > 5>  povmain.cpp
> > 4>  colour.cpp
> > 7>  bounding.cpp
> > 8>  parser.cpp
> > 7>  texture.cpp
> > 4>  metadata.cpp
> > 3>..\..\source\backend\bounding\boundingtask.cpp(91): warning C4267: 'return' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(162): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(163): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(178): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(179): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>  povray.cpp
> > 7>  scenedata.cpp
> > 5>povmain.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 5>  povfrontend.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povfrontend64d.lib
> > 3>..\..\source\backend\povray.cpp(515): warning C4267: 'argument' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 3>  benchmark.cpp
> > 3>  renderbackend.cpp
> > 7>  tracethreaddata.cpp
> > 8>..\..\source\parser\parser.cpp(9673): warning C4267: 'argument' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12022): error C2146: erreur de syntaxe :
> > absence de ';' avant l'identificateur 'idx1'
> > 4>  mathutil.cpp
> > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'idx1' : identificateur
> > non déclaré
> > 4>  Génération de code en cours...
> > 8>..\..\source\parser\parser.cpp(12023): error C2065: 'ssize_t' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12023): error C2146: erreur de syntaxe :
> > absence de ';' avant l'identificateur 'idx2'
> > 8>..\..\source\parser\parser.cpp(12023): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx1' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12026): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12028): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx1' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx2' : identificateur
> > non déclaré
> > 4>  jpeg.cpp
> > 8>  parser_strings.cpp
> > 7>  box.cpp
> > 3>  scene.cpp
> > 7>  Génération de code en cours...
> > 4>..\..\source\base\image\jpeg.cpp(502): warning C4267: 'argument' : conversion
> > de 'size_t' en 'unsigned int', perte possible de données
> > 8>..\..\source\parser\parser_strings.cpp(479): error C2131: l'expression n'a pas
> > été évaluée en constante
> > 8>  ..\..\source\parser\parser_strings.cpp(479): note: échec en raison
> > d'arguments non constants ou d'une référence à un symbole non constant
> > 8>  ..\..\source\parser\parser_strings.cpp(479): note: voir l'utilisation de
> > 'this'
> > 8>..\..\source\parser\parser_strings.cpp(708): warning C4267: '=' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>..\..\source\parser\parser_strings.cpp(1176): warning C4267: '=' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>  parser_tokenizer.cpp
> > 3>  Génération de code en cours...
> > 8>..\..\source\parser\parser_tokenizer.cpp(1514): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 7>bounding.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>  png.cpp
> > 8>..\..\source\parser\parser_tokenizer.cpp(3915): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 2>  vidcap.cpp
> > 8>..\..\source\parser\parser_tokenizer.cpp(3935): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 8>  Génération de code en cours...
> > 3>  povbackend.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbackend64d.lib
> > 7>  povcore.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povcore64d.lib
> > 4>  Génération de code en cours...
> > 4>timer.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>mathutil.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>  povbase.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbase64d.lib
> > 2>  rtrsupport.cpp
> > 1>  vfewin.vcxproj ->
> > C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\vfe64d.lib
> > 2>  Génération de code en cours...
> > 2>vidcap.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 2>  rtrsupport.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\rtrsupport64d.lib
> > 9>------ Génération ignorée : Projet : tests, Configuration : Debug x64
------
> > 9>Projet non sélectionné dans le cadre d'une génération pour cette
configuration
> > de solution
> > 10>------ Début de la génération : Projet : GUI, Configuration : Debug x64
> > ------
> > 11>------ Génération ignorée : Projet : console, Configuration : Debug x64
> > ------
> > 11>Projet non sélectionné dans le cadre d'une génération pour cette
> > configuration de solution
> > 10>  pvbitmap.cpp
> > 10>  pvdialog.cpp
> > 10>  pvdisplay.cpp
> > 10>  pvedit.cpp
> > 10>..\pvedit.cpp(301): warning C4267: '+=' : conversion de 'size_t' en 'int',
> > perte possible de données
> > 10>  pvengine.cpp
> > 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(1544): warning
> > C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est
déclarée
> > 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(3190): warning
> > C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est
déclarée
> > 10>..\pvengine.cpp(498): warning C4838: la conversion de 'int' en 'WORD'
> > requiert une conversion restrictive
> > 10>..\pvengine.cpp(1721): warning C4477: 'sprintf' : la chaîne de format '%p'
> > nécessite un argument de type 'void *', mais l'argument variadique 2 est de type
> > 'DWORD64'
> > 10>..\pvengine.cpp(5152): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>..\pvengine.cpp(5608): warning C4267: '=' : conversion de 'size_t' en
> > 'unsigned int', perte possible de données
> > 10>..\pvengine.cpp(5787): warning C4267: '=' : conversion de 'size_t' en
> > 'unsigned int', perte possible de données
> > 10>..\pvengine.cpp(5719): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>  pvfiles.cpp
> > 10>  pvfrontend.cpp
> > 10>  pvguiext.cpp
> > 10>  pvmem.cpp
> > 10>  pvmenu.cpp
> > 10>  pvmisc.cpp
> > 10>..\pvmisc.cpp(223): warning C4838: la conversion de 'int' en 'unsigned int'
> > requiert une conversion restrictive
> > 10>  pvtext.cpp
> > 10>  pvupdate.cpp
> > 10>..\pvupdate.cpp(166): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>  Génération de code en cours...
> > 10>LINK : fatal error LNK1104: impossible d'ouvrir le fichier
> >
'C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povparser64d.lib'
> > ========== Génération : 6 a réussi, 2 a échoué, 15 mis à jour, 3 a été
ignoré
> > ==========
> >
> >
> >
> >
>
> you can fix the ssize_t error by defining it as a signed integer such as
> int_least32_t

Does that mean I need to learn C to test the branch? :-)

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 09/05/2020 à 14:49, Mr a écrit :
> > Le_Forgeron <jgr### [at] freefr> wrote:
> >> Le 18/08/2018 à 13:58, Le_Forgeron a écrit :
> >>> For the people who do not want to bother with git, Hgpovray is now
> >>> available as sources
> >>>
> >>>
> >> Latest version so far:
> >>
> >> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
> >>
> >>> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226.Bigarade
> >>
> >>
> >>> More works on the agenda :
> >>>
> >>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> >>>
> >
> > Bonjour !
> >
> > I just tried to build the latest HG-Pov I could find which seems to be that
> > Bigarade, right? Using MS VS2015,
> > Here is VS2015 build output:
> >
> > 1>------ Début de la génération : Projet : vfewin, Configuration : Debug x64
> > ------
> > 2>------ Début de la génération : Projet : rtrsupport, Configuration : Debug
x64
> > ------
> > 3>------ Début de la génération : Projet : povbackend, Configuration : Debug
x64
> > ------
> > 4>------ Début de la génération : Projet : povbase, Configuration : Debug
x64
> > ------
> > 5>------ Début de la génération : Projet : povfrontend, Configuration :
Debug
> > x64 ------
> > 6>------ Génération ignorée : Projet : boost_date_time, Configuration :
Debug
> > x64 ------
> > 6>Projet non sélectionné dans le cadre d'une génération pour cette
configuration
> > de solution
> > 7>------ Début de la génération : Projet : povcore, Configuration : Debug
x64
> > ------
> > 8>------ Début de la génération : Projet : povparser, Configuration : Debug
x64
> > ------
> > 1>  vfesession.cpp
> > 2>  vidcapimpl.cpp
> > 3>  boundingtask.cpp
> > 5>  povmain.cpp
> > 4>  colour.cpp
> > 7>  bounding.cpp
> > 8>  parser.cpp
> > 7>  texture.cpp
> > 4>  metadata.cpp
> > 3>..\..\source\backend\bounding\boundingtask.cpp(91): warning C4267: 'return' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(162): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(163): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(178): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>..\..\source\backend\bounding\boundingtask.cpp(179): warning C4267: '=' :
> > conversion de 'size_t' en 'unsigned int', perte possible de données
> > 3>  povray.cpp
> > 7>  scenedata.cpp
> > 5>povmain.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 5>  povfrontend.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povfrontend64d.lib
> > 3>..\..\source\backend\povray.cpp(515): warning C4267: 'argument' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 3>  benchmark.cpp
> > 3>  renderbackend.cpp
> > 7>  tracethreaddata.cpp
> > 8>..\..\source\parser\parser.cpp(9673): warning C4267: 'argument' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12022): error C2146: erreur de syntaxe :
> > absence de ';' avant l'identificateur 'idx1'
> > 4>  mathutil.cpp
> > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'idx1' : identificateur
> > non déclaré
> > 4>  Génération de code en cours...
> > 8>..\..\source\parser\parser.cpp(12023): error C2065: 'ssize_t' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12023): error C2146: erreur de syntaxe :
> > absence de ';' avant l'identificateur 'idx2'
> > 8>..\..\source\parser\parser.cpp(12023): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx1' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12024): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12026): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12028): error C2065: 'idx2' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx1' : identificateur
> > non déclaré
> > 8>..\..\source\parser\parser.cpp(12031): error C2065: 'idx2' : identificateur
> > non déclaré
> > 4>  jpeg.cpp
> > 8>  parser_strings.cpp
> > 7>  box.cpp
> > 3>  scene.cpp
> > 7>  Génération de code en cours...
> > 4>..\..\source\base\image\jpeg.cpp(502): warning C4267: 'argument' : conversion
> > de 'size_t' en 'unsigned int', perte possible de données
> > 8>..\..\source\parser\parser_strings.cpp(479): error C2131: l'expression n'a pas
> > été évaluée en constante
> > 8>  ..\..\source\parser\parser_strings.cpp(479): note: échec en raison
> > d'arguments non constants ou d'une référence à un symbole non constant
> > 8>  ..\..\source\parser\parser_strings.cpp(479): note: voir l'utilisation de
> > 'this'
> > 8>..\..\source\parser\parser_strings.cpp(708): warning C4267: '=' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>..\..\source\parser\parser_strings.cpp(1176): warning C4267: '=' : conversion
> > de 'size_t' en 'int', perte possible de données
> > 8>  parser_tokenizer.cpp
> > 3>  Génération de code en cours...
> > 8>..\..\source\parser\parser_tokenizer.cpp(1514): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 7>bounding.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>  png.cpp
> > 8>..\..\source\parser\parser_tokenizer.cpp(3915): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 2>  vidcap.cpp
> > 8>..\..\source\parser\parser_tokenizer.cpp(3935): warning C4267: '=' :
> > conversion de 'size_t' en 'int', perte possible de données
> > 8>  Génération de code en cours...
> > 3>  povbackend.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbackend64d.lib
> > 7>  povcore.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povcore64d.lib
> > 4>  Génération de code en cours...
> > 4>timer.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>mathutil.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 4>  povbase.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povbase64d.lib
> > 2>  rtrsupport.cpp
> > 1>  vfewin.vcxproj ->
> > C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\vfe64d.lib
> > 2>  Génération de code en cours...
> > 2>vidcap.obj : warning LNK4221: Ce fichier objet ne dÚfinit pas de symboles
> > publics jusqu'ici non dÚfinis. Par consÚquent, il ne sera utilisÚ par aucune
> > opÚration de lien utilisant cette bibliothÞque
> > 2>  rtrsupport.vcxproj ->
> >
C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\rtrsupport64d.lib
> > 9>------ Génération ignorée : Projet : tests, Configuration : Debug x64
------
> > 9>Projet non sélectionné dans le cadre d'une génération pour cette
configuration
> > de solution
> > 10>------ Début de la génération : Projet : GUI, Configuration : Debug x64
> > ------
> > 11>------ Génération ignorée : Projet : console, Configuration : Debug x64
> > ------
> > 11>Projet non sélectionné dans le cadre d'une génération pour cette
> > configuration de solution
> > 10>  pvbitmap.cpp
> > 10>  pvdialog.cpp
> > 10>  pvdisplay.cpp
> > 10>  pvedit.cpp
> > 10>..\pvedit.cpp(301): warning C4267: '+=' : conversion de 'size_t' en 'int',
> > perte possible de données
> > 10>  pvengine.cpp
> > 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(1544): warning
> > C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est
déclarée
> > 10>C:\Program Files (x86)\Windows Kits\8.1\Include\um\dbghelp.h(3190): warning
> > C4091: 'typedef ' : ignoré à gauche de '' quand aucune variable n'est
déclarée
> > 10>..\pvengine.cpp(498): warning C4838: la conversion de 'int' en 'WORD'
> > requiert une conversion restrictive
> > 10>..\pvengine.cpp(1721): warning C4477: 'sprintf' : la chaîne de format '%p'
> > nécessite un argument de type 'void *', mais l'argument variadique 2 est de type
> > 'DWORD64'
> > 10>..\pvengine.cpp(5152): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>..\pvengine.cpp(5608): warning C4267: '=' : conversion de 'size_t' en
> > 'unsigned int', perte possible de données
> > 10>..\pvengine.cpp(5787): warning C4267: '=' : conversion de 'size_t' en
> > 'unsigned int', perte possible de données
> > 10>..\pvengine.cpp(5719): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>  pvfiles.cpp
> > 10>  pvfrontend.cpp
> > 10>  pvguiext.cpp
> > 10>  pvmem.cpp
> > 10>  pvmenu.cpp
> > 10>  pvmisc.cpp
> > 10>..\pvmisc.cpp(223): warning C4838: la conversion de 'int' en 'unsigned int'
> > requiert une conversion restrictive
> > 10>  pvtext.cpp
> > 10>  pvupdate.cpp
> > 10>..\pvupdate.cpp(166): warning C4996: 'GetVersionExA': a été déclaré
> > déconseillé
> > 10>  C:\Program Files (x86)\Windows Kits\8.1\Include\um\sysinfoapi.h(433): note:
> > voir la déclaration de 'GetVersionExA'
> > 10>  Génération de code en cours...
> > 10>LINK : fatal error LNK1104: impossible d'ouvrir le fichier
> >
'C:\HG-POV\povray-3.8.0.alpha-Hg.226.Bigarade\windows\vs2015\bin64\lib\povparser64d.lib'
> > ========== Génération : 6 a réussi, 2 a échoué, 15 mis à jour, 3 a été
ignoré
> > ==========
> >
> >
> >
> >
>
> you can fix the ssize_t error by defining it as a signed integer such as
> int_least32_t

I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
and 12023 I made a few attempts at replacing "ssize_t"

ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);


First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
but every time only got an  error "conversion de 'size_t' en 'int', perte
possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
processor machine.

Any further advice?

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> ...
> > > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' :
> ...
> > you can fix the ssize_t error by defining it as a signed integer such as
> > int_least32_t
>
> I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
> and 12023 I made a few attempts at replacing "ssize_t"
>
> ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
> ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);
>
> First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
> but every time only got an  error "conversion de 'size_t' en 'int', perte
> possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
> processor machine.
>
> Any further advice?

taking that error (from clean source, I assume) means that, for some reason, no
header is included which provides 'ssize_t'.  after a quick look on my system, I
think including 'unistd.h' would do.  alternatively, you could, at the top of
whichever .cpp file, add a definition (ideally with a '#ifndef' guard) like:
  #define ssize_t int

POSIX guarantees a max of 32767, I think.

hth.



regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > ...
> > > > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' :
> > ...
> > > you can fix the ssize_t error by defining it as a signed integer such as
> > > int_least32_t
> >
> > I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
> > and 12023 I made a few attempts at replacing "ssize_t"
> >
> > ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
> > ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);
> >
> > First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
> > but every time only got an  error "conversion de 'size_t' en 'int', perte
> > possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
> > processor machine.
> >
> > Any further advice?
>
> taking that error (from clean source, I assume) means that, for some reason, no
> header is included which provides 'ssize_t'.  after a quick look on my system, I
> think including 'unistd.h' would do.  alternatively, you could, at the top of
> whichever .cpp file, add a definition (ideally with a '#ifndef' guard) like:
>   #define ssize_t int
>
> POSIX guarantees a max of 32767, I think.
>
> hth.
>
>
>
> regards, jr.

I made a search for "unistd.h" and could not find it neither in HG-POV nor in
POV-Ray 3.8 sources. what path should I include from? I tried without path and
it is not found.

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > ...
> > > > > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' :
> > > ...
> > > > you can fix the ssize_t error by defining it as a signed integer such as
> > > > int_least32_t
> > >
> > > I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
> > > and 12023 I made a few attempts at replacing "ssize_t"
> > >
> > > ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
> > > ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);
> > >
> > > First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
> > > but every time only got an  error "conversion de 'size_t' en 'int', perte
> > > possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
> > > processor machine.
> > >
> > > Any further advice?
> >
> > taking that error (from clean source, I assume) means that, for some reason, no
> > header is included which provides 'ssize_t'.  after a quick look on my system, I
> > think including 'unistd.h' would do.  alternatively, you could, at the top of
> > whichever .cpp file, add a definition (ideally with a '#ifndef' guard) like:
> >   #define ssize_t int
> >
> > POSIX guarantees a max of 32767, I think.

should have written: guarantees at least a maximum of 32767.

> >
> I made a search for "unistd.h" and could not find it neither in HG-POV nor in
> POV-Ray 3.8 sources. what path should I include from? I tried without path and
> it is not found.


it's not part of an application, it's a system header (well, it is here, on a
Slackware GNU/Linux box).  turns out on my box just including 'stdio.h' is
enough.

jr@crow:1:tmp$ locate unistd.h | grep /usr/include
/usr/include/unistd.h
/usr/include/sys/unistd.h
/usr/include/asm-x86/unistd.h
/usr/include/bits/unistd.h
/usr/include/linux/unistd.h
/usr/include/asm-generic/unistd.h
jr@crow:2:tmp$ cat mr.c
#include <stdio.h>

int main(void) {
  ssize_t a, b, c;
  a = -1, b = 0, c = 1;
  printf("ssize_t vals: %zd  %zd  %zd\n", a, b, c);
  return 0;
}

jr@crow:3:tmp$ c99 mr.c
jr@crow:4:tmp$ ./a.out
ssize_t vals: -1  0  1
jr@crow:5:tmp$


(the 'c99' is a shell alias for the compiler)


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> ...
> jr@crow:2:tmp$ cat mr.c
> #include <stdio.h>
> int main(void) {
>   ssize_t a, b, c;
>   a = -1, b = 0, c = 1;
>   printf("ssize_t vals: %zd  %zd  %zd\n", a, b, c);
>   return 0;
> }
> ...

and, although I don't "speak" C++, I was able to confirm that it should work if
you include 'stdio.h'.

jr@crow:6:tmp$ c### [at] mrcpp
#include <iostream>
#include <stdio.h>

int main(void) {
  ssize_t a, b, c;
  a = -1, b = 0, c = 1;
  std::cout << "ssize_t vals:" << a << "  " << b << "  " << c << "\n";
  return 0;
}

jr@crow:7:tmp$ c++ mr.cpp
jr@crow:8:tmp$ ./a.out
ssize_t vals:-1  0  1
jr@crow:9:tmp$


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > ...
> > > > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' :
> > ...
> > > you can fix the ssize_t error by defining it as a signed integer such as
> > > int_least32_t
> >
> > I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
> > and 12023 I made a few attempts at replacing "ssize_t"
> >
> > ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
> > ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);
> >
> > First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
> > but every time only got an  error "conversion de 'size_t' en 'int', perte
> > possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
> > processor machine.
> >
> > Any further advice?
>
> taking that error (from clean source, I assume) means that, for some reason, no
> header is included which provides 'ssize_t'.  after a quick look on my system, I
> think including 'unistd.h' would do.  alternatively, you could, at the top of
> whichever .cpp file, add a definition (ideally with a '#ifndef' guard) like:
>   #define ssize_t int
>
> POSIX guarantees a max of 32767, I think.
>
> hth.
>
>
>
> regards, jr.

Thanks
I tried all manners of include suggested to no success... However, this seemed
to do it for me, added after line 47 of parser.cpp below #include <algorithm> :


#if defined(_MSC_VER)
#include <BaseTsd.h>
typedef SSIZE_T ssize_t;
#endif


Now I have another error, Which I boldly assume unrelated:
line 479  expression not evaluated to constant:
char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
as well as "Impossible d'utiliser 'this' dans une expression constante" (for the
same line)

web search brings me here:
https://docs.microsoft.com/fr-fr/cpp/error-messages/compiler-errors-1/compiler-error-c2131?view=vs-2019

I interpret it as an incentive to initialize some variable or iterator index
beforehand? I am standing still in the dark waiting for your lights !

Post a reply to this message

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:

> Now I have another error, Which I boldly assume unrelated:
> line 479  expression not evaluated to constant:
> char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
> as well as "Impossible d'utiliser 'this' dans une expression constante" (for the
> same line)
>
> web search brings me here:
>
https://docs.microsoft.com/fr-fr/cpp/error-messages/compiler-errors-1/compiler-error-c2131?view=vs-2019
>
> I interpret it as an incentive to initialize some variable or iterator index
> beforehand? I am standing still in the dark waiting for your lights !

I forgot to mention that this line 479 was now in parser_strings.cpp

Post a reply to this message

hi,
"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > ...
> > > > > 8>..\..\source\parser\parser.cpp(12022): error C2065: 'ssize_t' :
> > > ...
> > > > you can fix the ssize_t error by defining it as a signed integer such as
> > > > int_least32_t
> > >
> > > I don't know if that was any sensible thing to do but, in parser.cpp, line 12022
> > > and 12023 I made a few attempts at replacing "ssize_t"
> > >
> > > ssize_t idx1 = std::min(Local_Vector[0], Local_Vector[1]);
> > > ssize_t idx2 = std::max(Local_Vector[0], Local_Vector[1]);
> > >
> > > First by "int_least32_t" and then by "unsigned int" and finally "int_least64_t",
> > > but every time only got an  error "conversion de 'size_t' en 'int', perte
> > > possible de données" and no build. Using MSVS 2015 on Windows 7, with I7
> > > processor machine.
> > >
> > > Any further advice?
> >
> > taking that error (from clean source, I assume) means that, for some reason, no
> > header is included which provides 'ssize_t'.  after a quick look on my system, I
> > think including 'unistd.h' would do.  alternatively, you could, at the top of
> > whichever .cpp file, add a definition (ideally with a '#ifndef' guard) like:
> >   #define ssize_t int
> >
> > POSIX guarantees a max of 32767, I think.
>
> Thanks
> I tried all manners of include suggested to no success... However, this seemed
> to do it for me, added after line 47 of parser.cpp below #include <algorithm> :
>
> #if defined(_MSC_VER)
> #include <BaseTsd.h>
> typedef SSIZE_T ssize_t;
> #endif

I had not realised you're on Redmond's finest.

I wonder whether using either the Linux "sub-system" supplied with Windows 10,
aiui, or an installation of 'cygwin', would not make all these errors/problems
go away.

<https://www.cygwin.com/>

> Now I have another error, Which I boldly assume unrelated:
> line 479  expression not evaluated to constant:
> char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];

one hack-ish workaround could be to separate out the operations, ie in C I might
do something like:

size_t const n = strlen(Get_Token_String(...));
char tmp_compound[4 + n] = {'\0'};

> as well as "Impossible d'utiliser 'this' dans une expression constante" (for the
> same line)
>
> web search brings me here:
>
https://docs.microsoft.com/fr-fr/cpp/error-messages/compiler-errors-1/compiler-error-c2131?view=vs-2019
>
> I interpret it as an incentive to initialize some variable or iterator index
> beforehand? I am standing still in the dark waiting for your lights !

some "lights", more like a 15W bulb.  :-)  good luck.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:

> one hack-ish workaround could be to separate out the operations, ie in C I might
> do something like:
>
> size_t const n = strlen(Get_Token_String(...));
> char tmp_compound[4 + n] = {'\0'};

So instead of this:
char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];

....and after adding the same include in parser_strings.cpp, I used:

const ssize_t n = strlen(Get_Token_String(CYLINDER_TOKEN));
char tmp_compound[4 + n];

And still error messages from the same line not eval to const also tried with
const int n = strlen(Get_Token_String(CYLINDER_TOKEN));

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > one hack-ish workaround could be to separate out the operations, ie in C I might
> > do something like:
> >
> > size_t const n = strlen(Get_Token_String(...));
> > char tmp_compound[4 + n] = {'\0'};
>
> So instead of this:
> char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
>
> ....and after adding the same include in parser_strings.cpp, I used:
>
> const ssize_t n = strlen(Get_Token_String(CYLINDER_TOKEN));
> char tmp_compound[4 + n];
>
> And still error messages from the same line not eval to const also tried with
> const int n = strlen(Get_Token_String(CYLINDER_TOKEN));

two points.  the 'strlen()' function returns a 'size_t', that is, an unsigned
value, while both 'int' and 'ssize_t' hold signed values; however, if that was
the problem you would have seen "warning: conversion to..." messages, not
errors.

second, I just downloaded 'Hg.226.Bigarade' and built it; one single warning
message aside, the program builds cleanly (on a Slackware GNU/Linux box).  so,
sorry, cannot help any further, but my advice is: either create a virtual
machine running a Linux, or install 'cygwin'[*], or explore whether the Windows
10/Ubuntu thing works for you.

(I read the following quote in someone's signature block years back
(paraphrased): "computers are like air-conditioning, they stop working when you
open Windows."  ;-))

[*] there are other s/wares too, like 'MinGW'.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > one hack-ish workaround could be to separate out the operations, ie in C I might
> > > do something like:
> > >
> > > size_t const n = strlen(Get_Token_String(...));
> > > char tmp_compound[4 + n] = {'\0'};
> >
> > So instead of this:
> > char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
> >
> > ....and after adding the same include in parser_strings.cpp, I used:
> >
> > const ssize_t n = strlen(Get_Token_String(CYLINDER_TOKEN));
> > char tmp_compound[4 + n];
> >
> > And still error messages from the same line not eval to const also tried with
> > const int n = strlen(Get_Token_String(CYLINDER_TOKEN));
>
> two points.  the 'strlen()' function returns a 'size_t', that is, an unsigned
> value, while both 'int' and 'ssize_t' hold signed values; however, if that was
> the problem you would have seen "warning: conversion to..." messages, not
> errors.
>
> second, I just downloaded 'Hg.226.Bigarade' and built it; one single warning
> message aside, the program builds cleanly (on a Slackware GNU/Linux box).  so,
> sorry, cannot help any further, but my advice is: either create a virtual
> machine running a Linux, or install 'cygwin'[*], or explore whether the Windows
> 10/Ubuntu thing works for you.
>
> (I read the following quote in someone's signature block years back
> (paraphrased): "computers are like air-conditioning, they stop working when you
> open Windows."  ;-))
>
> [*] there are other s/wares too, like 'MinGW'.
>
>
> regards, jr

Sorry since my purpose is blender exporter use.  I can't afford to not be cross
platform

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> ...  I can't afford to not be cross platform

you know that POV-Ray builds, you know that Hg is derived from the same sources.
 it would be a lot of work, but if you worked through the differences in the
sources, perhaps aided by single-stepping (with debugger) through POV-Ray
execution, you could (likely) find out exactly what
'Get_Token_String(CYLINDER_TOKEN)' returns, and what else matters at that point
in the code.  sorry to be of little/no help.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > ...  I can't afford to not be cross platform
>
> you know that POV-Ray builds, you know that Hg is derived from the same sources.
>  it would be a lot of work, but if you worked through the differences in the
> sources, perhaps aided by single-stepping (with debugger) through POV-Ray
> execution, you could (likely) find out exactly what
> 'Get_Token_String(CYLINDER_TOKEN)' returns, and what else matters at that point
> in the code.  sorry to be of little/no help.
>
>
> regards, jr.

I had tried but could not find 'Get_Token_String(CYLINDER_TOKEN)' used in the
same context in POV-Ray trunk source, I may have searched wrong.
Just trying to help would already be a lot! besides I do have the impression
that you did unlock a few a step forwards. thanks !

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > ...  I can't afford to not be cross platform
> >
> > you know that POV-Ray builds, you know that Hg is derived from the same sources.
> >  it would be a lot of work, but if you worked through the differences in the
> > sources, perhaps aided by single-stepping (with debugger) through POV-Ray
> > execution, you could (likely) find out exactly what
> > 'Get_Token_String(CYLINDER_TOKEN)' returns, and what else matters at that point
> > in the code.  sorry to be of little/no help.
>
> I had tried but could not find 'Get_Token_String(CYLINDER_TOKEN)' used in the
> same context in POV-Ray trunk source, I may have searched wrong.
> Just trying to help would already be a lot! besides I do have the impression
> that you did unlock a few a step forwards. thanks !

thanks for the .. vote of confidence.  (flattery will get you anywhere..  :-))

I've created two 'tags' files with the symbols/names used in the sources.
searching them for 'Get_Token' gives me:

jr@swift:1:tmp$ xzgrep -n Get_Token hg_tags.xz
46500:Get_Token
povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 317;" f
class:pov_parser::Parser
46501:Get_Token_String
povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 1701;" f
class:pov_parser::Parser
jr@swift:2:tmp$ xzgrep -n Get_Token pov_tags.xz
45379:Get_Token povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp
210;" f class:pov_parser::Parser
45380:Get_Token_String
povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp 877;" f
class:pov_parser::Parser
jr@swift:3:tmp$

you can download the listings from here:

<https://drive.google.com/file/d/10RaLHKnogRE6ikkiaybHMP4d8ezyZfH9/view?usp=sharing>
<https://drive.google.com/file/d/10ThvgvOXlnSnHJrlAVdiV1UF1fcRpAIZ/view?usp=sharing>

they're about 20M each, so I have used 'xz' to compress, you can use 'WinRAR' to
uncompress if you don't have an 'unxz' installed.


regards, jr.

(reply via email if you feel this discussion is a bit off-topic)

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > > ...  I can't afford to not be cross platform
> > >
> > > you know that POV-Ray builds, you know that Hg is derived from the same sources.
> > >  it would be a lot of work, but if you worked through the differences in the
> > > sources, perhaps aided by single-stepping (with debugger) through POV-Ray
> > > execution, you could (likely) find out exactly what
> > > 'Get_Token_String(CYLINDER_TOKEN)' returns, and what else matters at that point
> > > in the code.  sorry to be of little/no help.
> >
> > I had tried but could not find 'Get_Token_String(CYLINDER_TOKEN)' used in the
> > same context in POV-Ray trunk source, I may have searched wrong.
> > Just trying to help would already be a lot! besides I do have the impression
> > that you did unlock a few a step forwards. thanks !
>
> thanks for the .. vote of confidence.  (flattery will get you anywhere..  :-))
>
> I've created two 'tags' files with the symbols/names used in the sources.
> searching them for 'Get_Token' gives me:
>
> jr@swift:1:tmp$ xzgrep -n Get_Token hg_tags.xz
> 46500:Get_Token
> povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 317;" f
> class:pov_parser::Parser
> 46501:Get_Token_String
> povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 1701;" f
> class:pov_parser::Parser
> jr@swift:2:tmp$ xzgrep -n Get_Token pov_tags.xz
> 45379:Get_Token povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp
> 210;" f class:pov_parser::Parser
> 45380:Get_Token_String
> povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp 877;" f
> class:pov_parser::Parser
> jr@swift:3:tmp$
>
> you can download the listings from here:
>
> <https://drive.google.com/file/d/10RaLHKnogRE6ikkiaybHMP4d8ezyZfH9/view?usp=sharing>
> <https://drive.google.com/file/d/10ThvgvOXlnSnHJrlAVdiV1UF1fcRpAIZ/view?usp=sharing>
>
> they're about 20M each, so I have used 'xz' to compress, you can use 'WinRAR' to
> uncompress if you don't have an 'unxz' installed.
>
>
> regards, jr.
>
> (reply via email if you feel this discussion is a bit off-topic)


The solution from this page seems to bring me a step further:
https://stackoverflow.com/questions/33423502/expression-did-not-evaluate-to-a-constant-c

so...
char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
becomes
char* tmp_compound = new char[4+strlen(Get_Token_String(CYLINDER_TOKEN))];

Now I'm left with new lnk errors of "unresolved external symbols"(?) in
povcore64d.lib(tracepixel.obj)

Post a reply to this message

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > hi,
> >
> > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > "jr" <cre### [at] gmailcom> wrote:
> > > > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > > > ...  I can't afford to not be cross platform
> > > >
> > > > you know that POV-Ray builds, you know that Hg is derived from the same
sources.
> > > >  it would be a lot of work, but if you worked through the differences in the
> > > > sources, perhaps aided by single-stepping (with debugger) through POV-Ray
> > > > execution, you could (likely) find out exactly what
> > > > 'Get_Token_String(CYLINDER_TOKEN)' returns, and what else matters at that
point
> > > > in the code.  sorry to be of little/no help.
> > >
> > > I had tried but could not find 'Get_Token_String(CYLINDER_TOKEN)' used in the
> > > same context in POV-Ray trunk source, I may have searched wrong.
> > > Just trying to help would already be a lot! besides I do have the impression
> > > that you did unlock a few a step forwards. thanks !
> >
> > thanks for the .. vote of confidence.  (flattery will get you anywhere..  :-))
> >
> > I've created two 'tags' files with the symbols/names used in the sources.
> > searching them for 'Get_Token' gives me:
> >
> > jr@swift:1:tmp$ xzgrep -n Get_Token hg_tags.xz
> > 46500:Get_Token
> > povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 317;" f
> > class:pov_parser::Parser
> > 46501:Get_Token_String
> > povray-3.8.0.alpha-Hg.226.Bigarade/source/parser/parser_tokenizer.cpp 1701;" f
> > class:pov_parser::Parser
> > jr@swift:2:tmp$ xzgrep -n Get_Token pov_tags.xz
> > 45379:Get_Token povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp
> > 210;" f class:pov_parser::Parser
> > 45380:Get_Token_String
> > povray-3.8.0-alpha.10064268/source/parser/parser_tokenizer.cpp 877;" f
> > class:pov_parser::Parser
> > jr@swift:3:tmp$
> >
> > you can download the listings from here:
> >
> >
<https://drive.google.com/file/d/10RaLHKnogRE6ikkiaybHMP4d8ezyZfH9/view?usp=sharing>
> >
<https://drive.google.com/file/d/10ThvgvOXlnSnHJrlAVdiV1UF1fcRpAIZ/view?usp=sharing>
> >
> > they're about 20M each, so I have used 'xz' to compress, you can use 'WinRAR' to
> > uncompress if you don't have an 'unxz' installed.
> >
> >
> > regards, jr.
> >
> > (reply via email if you feel this discussion is a bit off-topic)
>
>
> The solution from this page seems to bring me a step further:
>
https://stackoverflow.com/questions/33423502/expression-did-not-evaluate-to-a-constant-c
>
> so...
> char tmp_compound[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
> becomes
> char* tmp_compound = new char[4+strlen(Get_Token_String(CYLINDER_TOKEN))];
>

Hi, I went on trying:
....Then removing deprecated binary_function following this page helped me clear
the next issue:
https://stackoverflow.com/questions/22386882/why-have-unary-function-binary-function-been-removed-from-c11
So in compare_pointees.hpp line 36 may become:

struct equal_pointees_t {
  bool operator() ( OptionalPointee const& x, OptionalPointee const& y ) const
    { return equal_pointees(x,y) ; }
  typedef OptionalPointee first_argument_type;
  typedef OptionalPointee second_argument_type;
  typedef bool result_type;
} ;


And line 61:

struct less_pointees_t {
  bool operator() ( OptionalPointee const& x, OptionalPointee const& y ) const
    { return less_pointees(x,y) ; }
  typedef OptionalPointee first_argument_type;
  typedef OptionalPointee second_argument_type;
  typedef bool result_type;
} ;

However in function _template.hpp, line 662 should also change:
    , public std::function<T0,R>
and line 666:
    , public std::function<T0,T1,R>
but to what?


(using CLANG-cl compiler in MSVS2019 from its internal installer, and ISO C++ 17
language version

Post a reply to this message

hi,

"Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > > "jr" <cre### [at] gmailcom> wrote:
> > > > > "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
> > > > > > ...  I can't afford to not be cross platform
> > > > > ...
> Hi, I went on trying:
> ...
> However in function _template.hpp, line 662 should also change:
>     , public std::function<T0,R>
> and line 666:
>     , public std::function<T0,T1,R>
> but to what?

uh, sorry, no idea, this is way into C++ territory.  hopefully JG, or someone
else with the required language skills, can help.


regards, jr.

Post a reply to this message

On 10/3/20 7:20 PM, Mr wrote:
> "Mr" <mauriceraybaud [at] hotmail dot fr>> wrote:
...
> (using CLANG-cl compiler in MSVS2019 from its internal installer, and ISO C++ 17
> language version
> 

The code to which you are pointing is not familiar to me.

Have you tried compiling with the compiler flag '-std=c++11' ?

For windows compiles, the libraries necessary are in the libraries 
directory. In the official POV-Ray code base these have not been updated 
in a long time. Further, the POV-Ray base code is only ensured to work 
with c++11.

In what state you might find the libraries directory in hgpovray38 I do 
not know. Jerome was a Ubuntu user last I knew.

On unix/linux based systems the libraries are install-able based upon a 
release of whatever version of unix/linux/osx one runs. Therefore these 
libraries will work (are supposed to work) with the default c/c++ 
compiler version shipped. Compiles in the unix/linux/osx environments do 
not use the libraries directory.

The g++ default for Ubuntu 18.04.1 and 20.04.1 to which I just upgraded 
is c++14. I also set -std=c++11 occasionally to test I have not 
introduced something code wise which will not compile at that standard. 
In doing that for povr, I'm pretty sure POV-Ray itself still OK at c++11.

I've also played with compiles using -std=c++17, but these don't compile 
on 18.04 systems because the Ubuntu 18.04 'libraries' are not compatible 
with c++17(1). A hint the even older libraries directory versions likely 
are not.

(1) I've not yet tried a -stdc++17 compile on Ubuntu 20.04.1 - in part 
because I've been busy these past few days cleaning up new warnings in 
the povr code base I now see in the Ubuntu 20.04.1 environment!

My upfront guess is the windows libraries directory is out of date for 
the environment in which you are compiling. Give -std=c++11 a try. If 
you're lucky, let us know.

Bill P.

Post a reply to this message

William F Pokorny <ano### [at] anonymousorg> wrote:

> My upfront guess is the windows libraries directory is out of date for
> the environment in which you are compiling. Give -std=c++11 a try. If
> you're lucky, let us know.
>
> Bill P.

Indeed, instead of what was in my last message, I just replaced the content of
boost immediate sub-directories with what was in the similarly named directories
of a fresh boost download... That got rid of this error! (I wonder if my two
previous modifications (posix ssize_t specific import and typedef, and cam
tokenizer pointer are still needed. I will assume they were and go on after
switching back to iso c++14 language version) I am left with another error line
506 in pvengine.cpp,
at the end of SCROLLKEYS key2scroll []:

constant expression evaluates to -1 which cannot be narrowed to type 'WORD' (aka
'unsigned short') [-Wc++11-narrowing] GUI
C:\HG-povray\povray-hgpovray38\windows\pvengine.cpp 506

I also have the exact same error for what appears (to my Python-only eye) to be
a negative index, line 223 in pvmisc.cpp


I don't know by what to replace them ?

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> For the people who do not want to bother with git, Hgpovray is now
> available as sources
>
>
> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>
> >
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>
> More works on the agenda :
>
> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38

Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
background behind submarine instead of blue with current 3.8 plain pov master.

Post a reply to this message

Le 23/10/2020 à 16:10, Mr a écrit :
> Le_Forgeron <jgr### [at] freefr> wrote:
>> For the people who do not want to bother with git, Hgpovray is now
>> available as sources
>>
>>
>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>
>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>
>> More works on the agenda :
>>
>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> 
> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
> background behind submarine instead of blue with current 3.8 plain pov master.
> 
> 

Can you identify the version of hgpovray38 ?

Post a reply to this message

Le 24/10/2020 à 17:59, Le_Forgeron a écrit :
> Le 23/10/2020 à 16:10, Mr a écrit :
>> Le_Forgeron <jgr### [at] freefr> wrote:
>>> For the people who do not want to bother with git, Hgpovray is now
>>> available as sources
>>>
>>>
>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>>
>>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>>
>>> More works on the agenda :
>>>
>>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
>>
>> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
>> background behind submarine instead of blue with current 3.8 plain pov master.
>>
>>
> 
> Can you identify the version of hgpovray38 ?
> 
Oups, my bad. 226 Thermidor is 2 years old.

I will check with the latest head.

Post a reply to this message

Le 24/10/2020 à 18:11, Le_Forgeron a écrit :
> Le 24/10/2020 à 17:59, Le_Forgeron a écrit :
>> Le 23/10/2020 à 16:10, Mr a écrit :
>>> Le_Forgeron <jgr### [at] freefr> wrote:
>>>> For the people who do not want to bother with git, Hgpovray is now
>>>> available as sources
>>>>
>>>>
>>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>>>
>>>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
>>>>
>>>> More works on the agenda :
>>>>
>>>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
>>>
>>> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
>>> background behind submarine instead of blue with current 3.8 plain pov master.
>>>
>>>
>>
>> Can you identify the version of hgpovray38 ?
>>
> Oups, my bad. 226 Thermidor is 2 years old.
> 
> I will check with the latest head.
> 

Ok, happens also with latest head. I will have to search when it
started, not fun as I did not play with media.

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 24/10/2020 à 18:11, Le_Forgeron a écrit :
> > Le 24/10/2020 à 17:59, Le_Forgeron a écrit :
> >> Le 23/10/2020 à 16:10, Mr a écrit :
> >>> Le_Forgeron <jgr### [at] freefr> wrote:
> >>>> For the people who do not want to bother with git, Hgpovray is now
> >>>> available as sources
> >>>>
> >>>>
> >>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> >>>>
> >>>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> >>>>
> >>>> More works on the agenda :
> >>>>
> >>>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> >>>
> >>> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
> >>> background behind submarine instead of blue with current 3.8 plain pov master.
> >>>
> >>>
> >>
> >> Can you identify the version of hgpovray38 ?
> >>
> > Oups, my bad. 226 Thermidor is 2 years old.
> >
> > I will check with the latest head.
> >
>
> Ok, happens also with latest head. I will have to search when it
> started, not fun as I did not play with media.
maybe color models are to be suspected as so many  relatively recent changes
happened ?
(rgb > srgb rgbf rgbt RAL...)

Post a reply to this message

"Mr" <nomail@nomail> wrote:

> > Ok, happens also with latest head. I will have to search when it
> > started, not fun as I did not play with media.

> maybe color models are to be suspected as so many  relatively recent changes
> happened ?
> (rgb > srgb rgbf rgbt RAL...)

Works ok in (qtpovray)3.8, using #version 3.6 and #version 3.8

Line 786 has a negative light source, so maybe scroll down to that section and
start commenting out some lights and see what happens.

after that is // submarine and media

light in lines Line 73 & 74 has media_interaction off

Other than that - no idea.

Post a reply to this message

Le 25/10/2020 à 02:35, Bald Eagle a écrit :
> 
> "Mr" <nomail@nomail> wrote:
> 
>>> Ok, happens also with latest head. I will have to search when it
>>> started, not fun as I did not play with media.
> 
>> maybe color models are to be suspected as so many  relatively recent changes
>> happened ?
>> (rgb > srgb rgbf rgbt RAL...)
> 
> Works ok in (qtpovray)3.8, using #version 3.6 and #version 3.8
> 
> Line 786 has a negative light source, so maybe scroll down to that section and
> start commenting out some lights and see what happens.
> 

Negative light are honored, not the problem.

> after that is // submarine and media
> 
> light in lines Line 73 & 74 has media_interaction off
> 
> Other than that - no idea.
> 
> 

Commenting the media in the last union, get the same bad result as
hgpovray38 with povray master 3.8;

Post a reply to this message

Le 25/10/2020 à 10:33, Le_Forgeron a écrit :
> Le 25/10/2020 à 02:35, Bald Eagle a écrit :
>>
>> "Mr" <nomail@nomail> wrote:
>>
>>>> Ok, happens also with latest head. I will have to search when it
>>>> started, not fun as I did not play with media.
>>
>>> maybe color models are to be suspected as so many  relatively recent changes
>>> happened ?
>>> (rgb > srgb rgbf rgbt RAL...)
>>
>> Works ok in (qtpovray)3.8, using #version 3.6 and #version 3.8
>>
>> Line 786 has a negative light source, so maybe scroll down to that section and
>> start commenting out some lights and see what happens.
>>
> 
> Negative light are honored, not the problem.
> 
>> after that is // submarine and media
>>
>> light in lines Line 73 & 74 has media_interaction off
>>
>> Other than that - no idea.
>>
>>
> 
> Commenting the media in the last union, get the same bad result as
> hgpovray38 with povray master 3.8;
> 

Ok, I can fix it... but I do not understand yet why it happened and how
it works.

diff --git a/source/core/render/tracepixel.cpp
b/source/core/render/tracepixel.cpp
index 6d661b07..50d420a1 100644
--- a/source/core/render/tracepixel.cpp
+++ b/source/core/render/tracepixel.cpp
@@ -235,7 +235,7 @@ void TracePixelCameraData::SetupCamera(const Camera&
cam)
     bool normalise = false;
     camera = cam;
     useFocalBlur = false;
-    //precomputeContainingInteriors = true;
+    precomputeContainingInteriors = true;
     cameraDirection = camera.Direction;
     cameraRight = camera.Right;
     cameraUp =  camera.Up;

Post a reply to this message

On 10/25/20 5:57 AM, Le_Forgeron wrote:
> Le 25/10/2020 à 10:33, Le_Forgeron a écrit :
>> Le 25/10/2020 à 02:35, Bald Eagle a écrit :
...
>>
>> Commenting the media in the last union, get the same bad result as
>> hgpovray38 with povray master 3.8;
>>

I'd not have looked if not for the claim of the same bad results in 
povray master 3.8, but I branched off the last commit to master and I do 
not see that line in tracepixel.cpp commented. (I've not run the test case)

If any help, I went on to look at the state of tracepixel.cpp for every 
commit since the move the github. I see twelve up to v3.8 master head 
and none have the precompute... line commented.

> 
> Ok, I can fix it... but I do not understand yet why it happened and how
> it works.
> 
> diff --git a/source/core/render/tracepixel.cpp
> b/source/core/render/tracepixel.cpp
> index 6d661b07..50d420a1 100644
> --- a/source/core/render/tracepixel.cpp
> +++ b/source/core/render/tracepixel.cpp
> @@ -235,7 +235,7 @@ void TracePixelCameraData::SetupCamera(const Camera&
> cam)
>       bool normalise = false;
>       camera = cam;
>       useFocalBlur = false;
> -    //precomputeContainingInteriors = true;
> +    precomputeContainingInteriors = true;
>       cameraDirection = camera.Direction;
>       cameraRight = camera.Right;
>       cameraUp =  camera.Up;
>

Post a reply to this message

Latest package:

https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave

> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Latest package:
>
> https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave
>
> > https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave

Thanks ! It does render with blue background now.
Next issue is when I try to render the grenadine scene, I get a "Parse Error:
Cannot open include file lemon.inc." (disregarding any +L option).
That however could also happen with standard povray 3.8.

Post a reply to this message

"Mr" <nomail@nomail> wrote:
> Le_Forgeron <jgr### [at] freefr> wrote:
> > Latest package:
> >
> > https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave
> >
> > >
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.229.Betterave
>
> Thanks ! It does render with blue background now.
> Next issue is when I try to render the grenadine scene, I get a "Parse Error:
> Cannot open include file lemon.inc." (disregarding any +L option).
> That however could also happen with standard povray 3.8.

Sorry, ignore the grenadine (non)issue, I was making a typo.

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 24/10/2020 à 17:59, Le_Forgeron a écrit :
> > Le 23/10/2020 à 16:10, Mr a écrit :
> >> Le_Forgeron <jgr### [at] freefr> wrote:
> >>> For the people who do not want to bother with git, Hgpovray is now
> >>> available as sources
> >>>
> >>>
> >>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> >>>
> >>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> >>>
> >>> More works on the agenda :
> >>>
> >>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> >>
> >> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
> >> background behind submarine instead of blue with current 3.8 plain pov master.
> >>
> >>
> >
> > Can you identify the version of hgpovray38 ?
> >
> Oups, my bad. 226 Thermidor is 2 years old.
>
> I will check with the latest head.

Hi, I tried building on windows again with "betterave", and after reimplementing
all the changes previously mentioned in this thread I manage to push again many
of the errors away, but fail to see what to do about the wrong type line 485 of
windows/pvengine.cpp :
https://github.com/LeForgeron/povray/blob/Hgpovray/windows/pvengine.cpp#L485

At the end of a struct array typed WORD, having -1 values maybe to specify end
of array that looks like list of all keys that allow to scroll.

It seems that some difference relied upon *outside* this file allows vanilla pov
to build with that same technique.


Is there maybe some library that I could change to more recent version? (I
already pushed many errors by replacing boost folder... But maybe I want too far
with that one in a too recent version?

Post a reply to this message

"Mr" <nomail@nomail> wrote:
> Le_Forgeron <jgr### [at] freefr> wrote:
> > Le 24/10/2020 à 17:59, Le_Forgeron a écrit :
> > > Le 23/10/2020 à 16:10, Mr a écrit :
> > >> Le_Forgeron <jgr### [at] freefr> wrote:
> > >>> For the people who do not want to bother with git, Hgpovray is now
> > >>> available as sources
> > >>>
> > >>>
> > >>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> > >>>
> > >>>>
https://github.com/LeForgeron/povray/releases/tag/v3.8.0.alpha%2BHg.226-Thermidor-30
> > >>>
> > >>> More works on the agenda :
> > >>>
> > >>> http://wiki.povray.org/content/User:Le_Forgeron/HgPovray38
> > >>
> > >> Hello, ...With the set of default scenes, the advanced/abyss.pov shows a black
> > >> background behind submarine instead of blue with current 3.8 plain pov master.
> > >>
> > >>
> > >
> > > Can you identify the version of hgpovray38 ?
> > >
> > Oups, my bad. 226 Thermidor is 2 years old.
> >
> > I will check with the latest head.
>
> Hi, I tried building on windows again with "betterave", and after reimplementing
> all the changes previously mentioned in this thread I manage to push again many
> of the errors away, but fail to see what to do about the wrong type line 485 of
> windows/pvengine.cpp :
> https://github.com/LeForgeron/povray/blob/Hgpovray/windows/pvengine.cpp#L485
>
> At the end of a struct array typed WORD, having -1 values maybe to specify end
> of array that looks like list of all keys that allow to scroll.
>
> It seems that some difference relied upon *outside* this file allows vanilla pov
> to build with that same technique.
>
>
> Is there maybe some library that I could change to more recent version? (I
> already pushed many errors by replacing boost folder... But maybe I want too far
> with that one in a too recent version?

Adding :
-Wno-c++11-narrowing

into additional compiler options seems to have solved that... next issues coming
soon :-)

Post a reply to this message

"Mr" <nomail@nomail> wrote:
> >
> > Is there maybe some library that I could change to more recent version? (I
> > already pushed many errors by replacing boost folder... But maybe I want too far
> > with that one in a too recent version?
>
> Adding :
> -Wno-c++11-narrowing
>
> into additional compiler options seems to have solved that... next issues coming
> soon :-)


It now tells me as error for
libraries\boost\boost\type_index\detail\compile_time_type_info.hpp ,  line 279
(" boost::typeindex::detail::failed_to_get_function_name();") :
no matching function for call to 'failed_to_get_function_name'



....and as info for \libraries\boost\boost\type_index\ctti_type_index.hpp , line
117 :
in instantiation of member function 'boost::detail::ctti<void>::n' requested
here

also info for libraries\boost\boost\type_index\detail\compile_time_type_info.hpp
, line 87 :
candidate template ignored: couldn't infer template argument 'T'

If I click to show definition of 'T', below are lines :
"TypeIndex library could not detect your compiler.Please make the
BOOST_TYPE_INDEX_FUNCTION_SIGNATURE macro use correct compiler macro for getting
the whole function name. Define BOOST_TYPE_INDEX_CTTI_USER_DEFINED_PARSING to
correct value after that."

I am using Visual Studio 2019 building Release x64 target, with LLVM as a
compiler, ISO standard Language version C++14, --disable-io-restrictions
-Wno-c++11-narrowing, and with all other changes mentioned before in this
discussion. any clue what else to change to keep/(start?) moving forward?

Post a reply to this message

Hi, I made yet another attempt at building on Windows with other parameters and
received different warnings mentioning :

unknown type name '__m64'

Is there any chance to replace / enhance definition of this in the source code
with something more cross platform  ?

Post a reply to this message

Le 28/02/2021 à 23:15, Mr a écrit :
> Hi, I made yet another attempt at building on Windows with other parameters and
> received different warnings mentioning :
> 
> unknown type name '__m64'
> 
> Is there any chance to replace / enhance definition of this in the source code
> with something more cross platform  ?
> 
> 
> 

Can you elaborate a bit more (location of the error ?) ?

What is puzzling is that something like __m64 starts with double
underscore and that is something which should be reserved to compiler
implementation.

Any capture of the full message ?

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 28/02/2021 à 23:15, Mr a écrit :
> > Hi, I made yet another attempt at building on Windows with other parameters and
> > received different warnings mentioning :
> >
> > unknown type name '__m64'
> >
> > Is there any chance to replace / enhance definition of this in the source code
> > with something more cross platform  ?
> >
> >
> >
>
> Can you elaborate a bit more (location of the error ?) ?
>
> What is puzzling is that something like __m64 starts with double
> underscore and that is something which should be reserved to compiler
> implementation.
>
> Any capture of the full message

 Indeed includes belonged to LLVM /CLANG 10 for VC... The thing is I know too
little, especially about expected options and get lost in trial and errors.

A few clues or reminders of what "should" normally  be the best options could
help me to get there quicker. (Using a Windows 10 with an I7 CPU) current
settings: when loading a file I let it update toolset from v140 to version142

Configuration: Debug, Platform: x64
Windows SDK version 10 ... Better with the default of 8.1?
Floating point mode Precise... Better with strict or fast?

MFC: Use Standard Windows Libraries... Better with use MFC from a static
library? or from a shared dll?
Desactivate language extensions : Yes (/Za)... ok?
iso norm for C version?  trying with MSVC inherited... Better with C 11 or C 17?
iso norm for C++ version?  trying with default std C++14 (nothing older)...
Better with 17 or "latest"?

Character set currently undefined  in project file, better with unicode or MBCS?

No Common Language Runtime

Compile as C++(/TP) ... Better with compile as C Code (/TC)?
With that, I get all the errors mentionned in this discussion, so I stopped
assuming that the code should not be touched and am about to start again to the
suggested changes. I was only searching for a working build setup witout it
first : so I now switched the toolset from Visual Studio 2019 (v142) to LLVM
(clang-cl).. better with LLVM? any clues?

Post a reply to this message

Hi, I made a new attempt at building on Windows after changing one machine and a
fresh msvs install, (all configurations for vanilla pov built fine)  and noticed
one different warning about 'GetVersionExA' declared deprecated, from
pvupdate.cpp line 164, (microsoft error code C4996):

So I copied it here in case it might help solving windows build issues I met
before.

Post a reply to this message