 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have tried to compile the latest version 3.8.0.9861167 alpha and as in
the official version that I compiled I still have the problem that it
does not show the image while it is generated. While compiling it shows
the following message,
Built-in features:
I/O restrictions: enabled
X Window display: disabled
Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
Unsupported image formats: openexr
Compilation settings:
Build architecture: x86_64-pc-linux-gnu
Built/Optimized for: x86_64-pc-linux-gnu (using -march=native)
Compiler vendor: gnu
Compiler version: g++ 7
Compiler flags: -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math
-march=native -pthread
Libraries: -ltiff -ljpeg -lpng -lz -lrt -lm -lboost_thread
-pthread -lboost_system
Note that in the Built-in features the X Windows display is disabled.
I have followed the detailed instructions in
https://github.com/POV-Ray/povray/blob/master/unix/README.md
and I think that the dependencies listed do not include the necessary X
server or XCygwin or X11 or XDisplay or whatever it is called.
Can someone tell me what is needed to complete the installation?
Thank you very much
B. Gimeno
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
BGimeno <bru### [at] gmail com> wrote:
> I have tried to compile the latest version 3.8.0.9861167 alpha and as in
> the official version that I compiled I still have the problem that it
> does not show the image while it is generated. While compiling it shows
> the following message,
>
> Built-in features:
> I/O restrictions: enabled
> X Window display: disabled
> Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
> Unsupported image formats: openexr
>
> Note that in the Built-in features the X Windows display is disabled.
>
on my machine it reads "X Window display: enabled (using SDL)",
so it looks like that library (libSDL*.so) is not found/used when building.
hth.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.10.2018 um 16:38 schrieb jr:
>> Note that in the Built-in features the X Windows display is disabled.
>
> on my machine it reads "X Window display: enabled (using SDL)",
> so it looks like that library (libSDL*.so) is not found/used when building.
> hth.
From what I see in the Unix build scripts, it seems that POV-Ray can't
(or doesn't want to) use SDL without X.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
El 01/10/18 a las 17:04, clipka escribió:
> Am 01.10.2018 um 16:38 schrieb jr:
>
>>> Note that in the Built-in features the X Windows display is disabled.
>>
>> on my machine it reads "X Window display: enabled (using SDL)",
>> so it looks like that library (libSDL*.so) is not found/used when building.
>> hth.
>
> From what I see in the Unix build scripts, it seems that POV-Ray can't
> (or doesn't want to) use SDL without X.
>
So
"sudo apt-get install libsdl2-dev"
in my case solved this question.
If this resolved the issue in my case maybe it should be included in the
list of dependencies.
Thank you very much
Regards
B. Gimeno
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.10.2018 um 17:51 schrieb BGimeno:
> El 01/10/18 a las 17:04, clipka escribió:
>> Am 01.10.2018 um 16:38 schrieb jr:
>>
>>>> Note that in the Built-in features the X Windows display is disabled.
>>>
>>> on my machine it reads "X Window display: enabled (using SDL)",
>>> so it looks like that library (libSDL*.so) is not found/used when
>>> building.
>>> hth.
>>
>> From what I see in the Unix build scripts, it seems that POV-Ray can't
>> (or doesn't want to) use SDL without X.
>>
>
> So
> "sudo apt-get install libsdl2-dev"
> in my case solved this question.
> If this resolved the issue in my case maybe it should be included in the
> list of dependencies.
Did you have `libsdl-dev` installed before?
Because that one is explicitly mentioned in `unix/README.md` as /the/
extra prerequisite to enable the render preview display.
To the best of my knowledge, if `libsdl-dev` is installed, you shouldn't
need `libsdl2-dev`, because that's just a newer generation of the library.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
clipka <ano### [at] anonymousorg> wrote:
> Am 01.10.2018 um 16:38 schrieb jr:
> >> Note that in the Built-in features the X Windows display is disabled.
> > on my machine it reads "X Window display: enabled (using SDL)",
> > so it looks like that library (libSDL*.so) is not found/used when building.
> From what I see in the Unix build scripts, it seems that POV-Ray can't
> (or doesn't want to) use SDL without X.
one way of looking at it. :-)
I think POV-Ray does not "do" X at all, the last version (I have access to)
which does is 3.6.1. from 3.7.x it uses the SDL instead. a real pity because
if POV-Ray output to an actual X window, knocking up front-ends a la 'qtpovray'
would be doable in a(ny) number of (scripting) languages, with a single
supporting command line switch (cf 'xterm -into $id').
(also, why SDL in the first place? all the joystick and audio etc facilities,
unused. yet, no preview without)
BGimeno:
> "sudo apt-get install libsdl2-dev"
> in my case solved this question.
not all Linux distributions go to lengths to disenfranchise their users. ;-)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.10.2018 um 18:36 schrieb jr:
> I think POV-Ray does not "do" X at all, the last version (I have access to)
> which does is 3.6.1. from 3.7.x it uses the SDL instead. a real pity because
> if POV-Ray output to an actual X window, knocking up front-ends a la 'qtpovray'
> would be doable in a(ny) number of (scripting) languages, with a single
> supporting command line switch (cf 'xterm -into $id').
>
> (also, why SDL in the first place? all the joystick and audio etc facilities,
> unused. yet, no preview without)
I'm pretty sure it was primarily a matter of maintainability. And with
SDL being able to drive Xlib, my naive assumption as a Windows jockey is
that it /should/ still work.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
clipka <ano### [at] anonymousorg> wrote:
> Am 01.10.2018 um 18:36 schrieb jr:
> > I think POV-Ray does not "do" X at all, the last version (I have access to)
> > which does is 3.6.1. from 3.7.x it uses the SDL instead. a real pity because
> > if POV-Ray output to an actual X window, knocking up front-ends a la 'qtpovray'
> > would be doable in a(ny) number of (scripting) languages, with a single
> > supporting command line switch (cf 'xterm -into $id').
> > (also, why SDL in the first place? all the joystick and audio etc facilities,
> > unused. yet, no preview without)
>
> I'm pretty sure it was primarily a matter of maintainability. And with
> SDL being able to drive Xlib, my naive assumption as a Windows jockey is
> that it /should/ still work.
I did have a look at the API (some time ago, not long after installing 3.7), as
I recall there is no way of telling SDL to use a given window (id).
using Xlib (or lower) directly would have the added benefit of the built-in
network transparency.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 01/10/2018 à 20:29, jr a écrit :
> hi,
>
> clipka <ano### [at] anonymousorg> wrote:
>> Am 01.10.2018 um 18:36 schrieb jr:
>>> I think POV-Ray does not "do" X at all, the last version (I have access to)
>>> which does is 3.6.1. from 3.7.x it uses the SDL instead. a real pity because
>>> if POV-Ray output to an actual X window, knocking up front-ends a la 'qtpovray'
>>> would be doable in a(ny) number of (scripting) languages, with a single
>>> supporting command line switch (cf 'xterm -into $id').
>>> (also, why SDL in the first place? all the joystick and audio etc facilities,
>>> unused. yet, no preview without)
>>
>> I'm pretty sure it was primarily a matter of maintainability. And with
>> SDL being able to drive Xlib, my naive assumption as a Windows jockey is
>> that it /should/ still work.
>
> I did have a look at the API (some time ago, not long after installing 3.7), as
> I recall there is no way of telling SDL to use a given window (id).
>
what about SDL_CreateWindowFrom() ? (just googling libsdl)
The main issue with SDL so far in povray is the lack of title for the
render window.
I need to investigate SDL_SetWindowTitle()
https://wiki.libsdl.org/SDL_SetWindowTitle
> using Xlib (or lower) directly would have the added benefit of the built-in
> network transparency.
Oh, the dependancy on Xlib is even worse, and Xlib programming is painful.
Also, there is the Wayland menace (no more network, but windows does not
either, so who care... me !)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 02/10/2018 à 13:11, Le Forgeron a écrit :
> Le 01/10/2018 à 20:29, jr a écrit :
>> hi,
>>
>> clipka <ano### [at] anonymousorg> wrote:
>>> Am 01.10.2018 um 18:36 schrieb jr:
>>>> I think POV-Ray does not "do" X at all, the last version (I have
>>>> access to)
>>>> which does is 3.6.1. from 3.7.x it uses the SDL instead. a real
>>>> pity because
>>>> if POV-Ray output to an actual X window, knocking up front-ends a la
>>>> 'qtpovray'
>>>> would be doable in a(ny) number of (scripting) languages, with a
>>>> single
>>>> supporting command line switch (cf 'xterm -into $id').
>>>> (also, why SDL in the first place? all the joystick and audio etc
>>>> facilities,
>>>> unused. yet, no preview without)
>>>
>>> I'm pretty sure it was primarily a matter of maintainability. And with
>>> SDL being able to drive Xlib, my naive assumption as a Windows jockey is
>>> that it /should/ still work.
>>
>> I did have a look at the API (some time ago, not long after installing
>> 3.7), as
>> I recall there is no way of telling SDL to use a given window (id).
>>
>
> what about SDL_CreateWindowFrom() ? (just googling libsdl)
>
> The main issue with SDL so far in povray is the lack of title for the
> render window.
>
> I need to investigate SDL_SetWindowTitle()
>
> https://wiki.libsdl.org/SDL_SetWindowTitle
>
>
Ok, SDL2 has a migration guide and it will not be a five minutes patch
for Povray.
https://wiki.libsdl.org/MigrationGuide?highlight=%28SDL_WM_SetCaption%29
Most calls made in Povray have been updated to new functions, so there
might be a bit of change in logic too, and a need for detecting libsdl2
along with libsdl1.2 (none, either or both might be present)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
