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