 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fixed in POV-Ray v3.8.0 (currently under development). If you dare, try
the binaries available at:
https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.9387404
(Make sure to name them differently than the original v3.7 binaries. It
should also be possible to extract them to a different directory and run
them from there.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Fixed in POV-Ray v3.8.0 (currently under development). If you dare, try
> the binaries available at:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.9387404
>
> (Make sure to name them differently than the original v3.7 binaries. It
> should also be possible to extract them to a different directory and run
> them from there.)
Hi,
Yes, I will try to install povray 3.8.0, why not...
I gathered informations with an old file I kept, named 'config.log' that
contains among others, differents variables/values a user can change before
compile time especially when inputing './configure' at the prompt/terminal.
Until someone will tell me I'm wrong , I think that the variables used to name
the final binary are 'PACKAGE' or/and 'PACKAGE_TARNAME' (they both contain
'povray' )but I'm not sure.
If you can give me some advice about that, I'll be glad. :-D
------------------------
I discovered POVRay in 1997 in a magazine that came with a CD-Rom (that was the
2 second version under MS-DOS: v2.x) All I had as a CPU was an Intel 486 SX2
(yes, without a mathematic coprocessor :-( ). For a scene equivalent to the one
above with the conic_sweep, the render took about 6 hours, I quickly gave up
making scenes (I didn't use editor with the Scene description language, but a
software with iron wire interface with 4 windows named 'POVSB' (under windows
3.1) or something like this. I began learning the SDL later in 2007 until now.
Nostalgia... :-D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 06/11/2017 19:02, Warren wrote:
> I discovered POVRay in 1997 in a magazine that came with a CD-Rom (that was the
> 2 second version under MS-DOS: v2.x) All I had as a CPU was an Intel 486 SX2
> (yes, without a mathematic coprocessor:-( ). For a scene equivalent to the one
> above with the conic_sweep, the render took about 6 hours, I quickly gave up
> making scenes (I didn't use editor with the Scene description language, but a
> software with iron wire interface with 4 windows named 'POVSB' (under windows
> 3.1) or something like this. I began learning the SDL later in 2007 until now.
> Nostalgia...:-D
It took you long enough to drop in. ;-)
Welcome.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 06.11.2017 um 20:02 schrieb Warren:
> clipka <ano### [at] anonymousorg> wrote:
>> Fixed in POV-Ray v3.8.0 (currently under development). If you dare, try
>> the binaries available at:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.9387404
>>
>> (Make sure to name them differently than the original v3.7 binaries. It
>> should also be possible to extract them to a different directory and run
>> them from there.)
>
> Hi,
>
> Yes, I will try to install povray 3.8.0, why not...
> I gathered informations with an old file I kept, named 'config.log' that
> contains among others, differents variables/values a user can change before
> compile time especially when inputing './configure' at the prompt/terminal.
>
> Until someone will tell me I'm wrong , I think that the variables used to name
> the final binary are 'PACKAGE' or/and 'PACKAGE_TARNAME' (they both contain
> 'povray' )but I'm not sure.
> If you can give me some advice about that, I'll be glad. :-D
Oh wait... you're running Linux? Well, then it's a lot simpler: Just
download the tarball and proceed as usual (prebuild, configure, make,
install), this'll give you a POV-Ray installation living in an entirely
separate set of directories (with `3.8` in the name, as opposed to
`3.7`). Unless you're configuring to install in a custom directory anyway.
For Windows it's a bit more complicated since users don't usually build
their own binaries there. So for the users' convenience we provide
pre-built Windows binaries, but for our own convenience we don't provide
complete installer packages. So the binaries need to "piggyback" on an
existing installation.
>
> ------------------------
> I discovered POVRay in 1997 in a magazine that came with a CD-Rom (that was the
> 2 second version under MS-DOS: v2.x) All I had as a CPU was an Intel 486 SX2
> (yes, without a mathematic coprocessor :-( ). For a scene equivalent to the one
> above with the conic_sweep, the render took about 6 hours, I quickly gave up
> making scenes (I didn't use editor with the Scene description language, but a
> software with iron wire interface with 4 windows named 'POVSB' (under windows
> 3.1) or something like this. I began learning the SDL later in 2007 until now.
> Nostalgia... :-D
I see your 1997 CD-ROM and raise you a ca. 1995 copy obtained via FidoNet.
(I'm cheating a bit though: I never did a lot with POV-Ray back then,
and only re-discovered it in 2008.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 06.11.2017 um 20:02 schrieb Warren:
> > clipka <ano### [at] anonymousorg> wrote:
>
> I see your 1997 CD-ROM and raise you a ca. 1995 copy obtained via FidoNet.
>
> (I'm cheating a bit though: I never did a lot with POV-Ray back then,
> and only re-discovered it in 2008.)
After a quick research for the 'ca' term, I see that it means 'approximately'
(circa) and that's true, the magazine and the CD-Rom in question was sold in
december 1995 it was named "Sciences et Vie Micro - Villagina 3". The 24 bits
Targa files rendered with POVRay definitely caught my fancy by comparison with
the 256 colors of the Windows 3.1 standard desktop.
I notice your message about 3.8.0 POVRay setup under Linux. Thank you ;-D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warren" <nomail@nomail> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 06.11.2017 um 20:02 schrieb Warren:
> > > clipka <ano### [at] anonymousorg> wrote:
>
> > [About Linux and povray setup ]
I did some research on my computer about the povray 3.7 binary and remembering
your message I get a result (in the Terminal) that doesn't match what you said
:-( ...
Here's the Terminal and the output of some command (I use Ubuntu 16.xx as Linux
only)
antoine@antoine-pcmapex:/usr/local/bin$ ls -lArth
total 9,6M
-rwxr-xr-x 1 root root 3,2M juin 25 2016 povray
-rwxr-xr-x 1 root root 2,7M avril 29 2017 geomorph
antoine@antoine-pcmapex:/usr/local/bin$ which povray
/usr/local/bin/povray
antoine@antoine-pcmapex:/usr/local/bin$ which ls
/bin/ls
antoine@antoine-pcmapex:/usr/local/bin$ cd ..
antoine@antoine-pcmapex:/usr/local$ ls
bin Brother etc games include lib man sbin share src
antoine@antoine-pcmapex:/usr/local$ cd share
antoine@antoine-pcmapex:/usr/local/share$ ls
Aria ca-certificates doc emacs fonts geomorph locale man povray-3.7
SFML sgml timidity xml
antoine@antoine-pcmapex:/usr/local/share$ cd povray-3.7/
antoine@antoine-pcmapex:/usr/local/share/povray-3.7$ ls
icons include ini scenes scripts
antoine@antoine-pcmapex:/usr/local/share/povray-3.7$
--------------------end
As you can see there's a povray (3.7) binary in '/usr/local/bin/' and that
doesn't look to be a link file (the weight is about 3.2 Mo). I do have a
'povray-3.7/' directory in '/usr/local/share/' but there's no any binary file in
it.
The following input command in a Terminal show:
------------------------------------------------------------
antoine@antoine-pcmapex:/usr/local/bin$ ./povray --version
POV-Ray 3.7.0.unofficial
This is an unofficial version compiled by:
Antoine FAURE
The POV-Ray Team is not responsible for supporting this version.
Copyright 1991-2013 Persistence of Vision Raytracer Pty. Ltd.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Built-in features:
I/O restrictions: enabled
X Window display: enabled (using SDL)
Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
Unsupported image formats: openexr
Compilation settings:
Build architecture: x86_64-unknown-linux-gnu
Built/Optimized for: x86_64-unknown-linux-gnu (using -march=native)
Compiler vendor: gnu
Compiler version: g++-5 5.3.1
Compiler flags: -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -s -O3 -ffast-math -march=native -pthread
----------------------------------------------------end
This is the binary I have compiled some time ago (Antoine FAURE)
I don't seem to have the custom directory for the different versions of POVRay
you're talking about...
And doing some search with : 'sudo find / -name "povray" -type f' only displayed
the '/usr/local/bin' file
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
On 07/11/2017 17:25, Warren wrote:
>>> [About Linux and povray setup ]
> Here's the Terminal and the output of some command (I use Ubuntu 16.xx as Linux
> only)
>
> antoine@antoine-pcmapex:/usr/local/bin$ ls -lArth
> total 9,6M
> -rwxr-xr-x 1 root root 3,2M juin 25 2016 povray
-----<snip>-----
that all looked alright at first glance. the executable is always (I
think) simply povray, so on my machine I renamed the executable after
install to povray37 (alongside povray36).
> I don't seem to have the custom directory for the different versions of POVRay
> you're talking about...
> And doing some search with : 'sudo find / -name "povray" -type f' only displayed
> the '/usr/local/bin' file
IIUC, that's a misunderstanding. everything except the program is in
versioned (sub)directories. hth.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 07.11.2017 um 18:25 schrieb Warren:
> "Warren" <nomail@nomail> wrote:
>> clipka <ano### [at] anonymousorg> wrote:
>>> Am 06.11.2017 um 20:02 schrieb Warren:
>>>> clipka <ano### [at] anonymousorg> wrote:
>>
>>> [About Linux and povray setup ]
>
> I did some research on my computer about the povray 3.7 binary and remembering
> your message I get a result (in the Terminal) that doesn't match what you said
> :-( ...
Goes to show how well I know the Linux version... not. (*sigh!*)
Guess you'll need to use the `--prefix=PREFIX` configure option then.
See `./unix/install.txt` (or `./INSTALL` after the prebuild step).
Post a reply to this message
|
|
| |
| |
|
|
From: William F Pokorny
Subject: Re: orthographic camera and conic_sweep object
Date: 8 Nov 2017 10:50:52
Message: <5a0327dc$1@news.povray.org>
|
|
|
| |
| |
|
|
On 11/07/2017 07:04 PM, clipka wrote:
> Am 07.11.2017 um 18:25 schrieb Warren:
>> "Warren" <nomail@nomail> wrote:
>>> clipka <ano### [at] anonymousorg> wrote:
>>>> Am 06.11.2017 um 20:02 schrieb Warren:
>>>>> clipka <ano### [at] anonymousorg> wrote:
>>>
>>>> [About Linux and povray setup ]
>>
>> I did some research on my computer about the povray 3.7 binary and remembering
>> your message I get a result (in the Terminal) that doesn't match what you said
>> :-( ...
>
> Goes to show how well I know the Linux version... not. (*sigh!*)
>
> Guess you'll need to use the `--prefix=PREFIX` configure option then.
> See `./unix/install.txt` (or `./INSTALL` after the prebuild step).
>
Perhaps the following newsgroup post from this summer also of help:
http://news.povray.org/povray.beta-test/message/%3C5950ff4b%40news.povray.org%3E/#%3C5950ff4b%40news.povray.org%3E
Keep in mind it was written when the current 3.8.0 was called 3.7.1.
---
If you are not dependent on changes in the shipped include/ini files
between versions, you can do compiles for whatever version you have
downloaded/grabbed/modified via github/git and on success, copy the
final binary in <sourceInstall>/unix/povray to your $HOME/bin directory
as povray38, povrayIdea57 or whatever(1) and use that command over
'povray' when you run. $HOME/bin needs to be in your $PATH environment
variable.
Day to day I mostly use this latter method over the more complete
--prefix method. The disadvantage is the $HOME/bin/<povrayVersion>
method will use for includes/ini and home directory defaults whatever
the previous, matching 3.7 or 3.8 machine/user install. Whether the
executable looks for 3.7 or 3.8 defaults depends upon the version of the
code branch being compiled.
Aside: The 'elsewhere' part of './unix/install.txt' "3.1.3 Building
in-place or elsewhere" was not working the last I tried such a compile
earlier this year & expect it's still not.
Bill P.
(1) - Yep, I'm lying in the first 3.8 use case. One needs to have
installed the 3.8 version on your machine - at some point - no matter
what is left as your 'povray' system default/last install. Otherwise the
$HOME/bin/<povrayVersion> program won't find the default 3.8 directories
and files.
Or
To avoid overwriting the 3.7 executable in /usr/local/bin/povray during
a 'make install' of a 3.8 distribution, the environment variable POVINI
can be set to point to a specific ini file with Library_Path=...
settings to directories such that 3.8 executable - say
'$HOME/bin/povray38' - will run with the old 3.7 install getting only a
warning about no system 3.8 conf file. It will, so long as you at some
point create local the $HOME/.povray/3.8 directory and files matching
what you have already for $HOME/.povray/3.7.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 08.11.2017 um 16:50 schrieb William F Pokorny:
> Perhaps the following newsgroup post from this summer also of help:
>
>
http://news.povray.org/povray.beta-test/message/%3C5950ff4b%40news.povray.org%3E/#%3C5950ff4b%40news.povray.org%3E
>
>
> Keep in mind it was written when the current 3.8.0 was called 3.7.1.
Yes; and that might make it difficult to apply the approach: The v3.8
binary would try to read user-specific files from `~/.povray/3.8` which
would have been installed in `~/.povray/3.7`.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
