 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have a fairly new laptop that I'm setting up and sorting out, and at some
point I became aware that there is really precious little clear, methodical,
detailed information on how to install povray on a linux system, that is right
here on the POV-Ray website.
So, in an effort to work out a fairly robust process for folks new to linux, and
unfamiliar with all of "the usual" ways of doing things that are just left as
"we assumed that you already know how to do all of this..." (no) I'm going to
use this thread to document installation of official POV-Ray, perhaps by several
methods, version 3.8 alpha, and hopefully povr and hgpovray38 as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sytem information:
bald@Alienware ~/Desktop $ inxi -Fx
System: Host: Alienware Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.6.7 (Gtk 3.18.9) Distro: Linux Mint 18.3 Sylvia
Machine: System: Alienware product: Alienware 17 R3 v: 1.2.3
Mobo: Alienware model: Alienware 17 R3 v: A00 Bios: Alienware v:
1.2.3 date: 11/11/2015
CPU: Quad core Intel Core i7-6700HQ (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20736
clock speeds: max: 3500 MHz 1: 3284 MHz 2: 3269 MHz 3: 3400 MHz 4:
3266 MHz 5: 3279 MHz 6: 3409 MHz
7: 3297 MHz 8: 3366 MHz
Graphics: Card-1: Intel HD Graphics 530 bus-ID: 00:02.0
Card-2: NVIDIA GM204M [GeForce GTX 970M] bus-ID: 01:00.0
Display Server: X.Org 1.18.4 driver: nvidia Resolution:
192### [at] 60 02hz
GLX Renderer: GeForce GTX 970M/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA
384.130 Direct Rendering: Yes
Audio: Card Intel 100 Series/C230 Series Family HD Audio Controller driver:
snd_hda_intel bus-ID: 00:1f.3
Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network: Card-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller
driver: alx port: d000 bus-ID: 3b:00.0
IF: enp59s0 state: up speed: 1000 Mbps duplex: full mac:
f8:ca:b8:5e:15:b1
Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
driver: ath10k_pci bus-ID: 3c:00.0
IF: wlp60s0 state: down mac: 9c:b6:d0:09:fd:b5
Card-3: Atheros usb-ID: 001-003
IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives: HDD Total Size: 1000.2GB (1.7% used) ID-1: /dev/sda model:
HGST_HTS721010A9 size: 1000.2GB
Partition: ID-1: / size: 503G used: 8.4G (2%) fs: ext4 dev: /dev/sda6
ID-2: swap-1 size: 8.49GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 33.0C mobo: N/A gpu: 0.0:34C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 250 Uptime: 1 min Memory: 728.0/7881.1MB Init: systemd
runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-05-10 8:58 PM (-4), Bald Eagle wrote:
> I have a fairly new laptop that I'm setting up and sorting out, and at some
> point I became aware that there is really precious little clear, methodical,
> detailed information on how to install povray on a linux system, that is right
> here on the POV-Ray website.
>
> So, in an effort to work out a fairly robust process for folks new to linux, and
> unfamiliar with all of "the usual" ways of doing things that are just left as
> "we assumed that you already know how to do all of this..." (no) I'm going to
> use this thread to document installation of official POV-Ray, perhaps by several
> methods, version 3.8 alpha, and hopefully povr and hgpovray38 as well.
This sounds like an excellent thread for povray.unix. Indeed, it seems
you already started one there last June. Unless you're inviting Windows
and Mac users to contribute their own tips?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoocom> wrote:
> This sounds like an excellent thread for povray.unix.
It does.
> Indeed, it seems you already started one there last June.
I sorta remember that. ;)
> Unless you're inviting Windows and Mac users to contribute their own tips?
Yes. I think the primary motivation is addressing the paucity of information
that is available on the official webpage with regard to installation,
especially for 3.8 alpha.
I think a lot of people would like to use it, and would benefit from the
additions and changes made since 3.7 stable.
For the unix-specific packages, I think that a lot of people - out in the world
- might want to install povray but don't know how, and getting 3.8 properly
working might be daunting enough to overall prevent them from doing so.
Which would be shame, as we should be promoting the creation of new users
aggressively.
And it would be so nice to just have a fairly straightforward and easy-to-follow
plan for getting official povray, hgpovray38, and povr all installed so I could
use whichever one I wanted. Without breaking something.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> I have a fairly new laptop that I'm setting up and sorting out, and at some
> point I became aware that there is really precious little clear, methodical,
> detailed information on how to install povray on a linux system, that is right
> here on the POV-Ray website.
>
> So, in an effort to work out a fairly robust process for folks new to linux, and
> unfamiliar with all of "the usual" ways of doing things that are just left as
> "we assumed that you already know how to do all of this..." (no) I'm going to
> use this thread to document installation of official POV-Ray, perhaps by several
> methods, version 3.8 alpha, and hopefully povr and hgpovray38 as well.
Hi Bill
I don't know how far you have got with this. And it has been a long time since I
compiled POV-Ray.
Right now I wanted to see if I could remember anything related to that. Here's
what I did on my x86_64 PC running Ubuntu 20.04.2 LTS in order to compile
v3.7.0.8:
sudo apt install libboost-dev libpng-dev libjpeg-dev libtiff-dev
cd ~
git clone https://github.com/POV-Ray/povray
cd povray
git checkout release/v3.7.0
cd unix
less README
less install.txt
./prebuild.sh
cd ..
./configure COMPILED_BY="My Name <email@address>"
make check
sudo make install
(I did not actually execute the last line.) configure mentioned that it can not
find an sdl library, so there is no preview window while POV-Ray is rendering.
Perhaps it helps to do this before starting the process above:
sudo apt install libsdl1.2-dev
Also note that I have been using this PC for some months now, so there may be
some necessary utilities or libraries that has been installed along with other
programs that I have installed before now.
It might be that the process of compiling v3.8 is quite similar to this.
I see now that you mention installation of official POV-Ray. The process above
will, of coarse, always make and install an unofficial version.
Are you aware of any official prebuilt binary for x86_64 Linux PCs ?
--
Tor Olav
http://subcube.com
https://github.com/t-o-k
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:web.609b0f032344a9a11f9dae3025979125@news.povray.org Bald Eagle
wrote:
>> Unless you're inviting Windows and Mac users to contribute their own
>> tips?
>
> Yes.
No tips here. I'd realy welcome windows compilation instructions for using
VS17 Developer command prompt.
Ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Op 12/05/2021 om 01:10 schreef Bald Eagle:
> Yes. I think the primary motivation is addressing the paucity of information
> that is available on the official webpage with regard to installation,
> especially for 3.8 alpha.
>
This installation info was given by Clipka in
https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.10064268
However, in Windows, I use a more 'intuitive' way which gives access
both to 3.7 and 3.8 easily (in separate renders of course ;-) ). That is
by putting the complete folder 'povray-3.8.0-alpha.10064268-av691-Win64'
into the 'bin' folder of POV-Ray. That way, you can access both
'pvengine64.exe' versions side by side if you want to do so.
Additionally, there is no conflict between the two that I know of. I
never came up against one as long as I have been using this setup. In
the past I had thus different folders in 'bin' corresponding to
different development stages of POV-Ray, including MegaPOV and/or UberPOV.
But maybe this is common knowledge? I don't know.
> I think a lot of people would like to use it, and would benefit from the
> additions and changes made since 3.7 stable.
>
Absolutely.
> For the unix-specific packages, I think that a lot of people - out in the world
> - might want to install povray but don't know how, and getting 3.8 properly
> working might be daunting enough to overall prevent them from doing so.
>
> Which would be shame, as we should be promoting the creation of new users
> aggressively.
>
> And it would be so nice to just have a fairly straightforward and easy-to-follow
> plan for getting official povray, hgpovray38, and povr all installed so I could
> use whichever one I wanted. Without breaking something.
>
...and, when possible, for Windows too of course. ;-)
Excellent initiative!
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tor Olav Kristensen" <tor### [at] TOBEREMOVEDgmailcom> wrote:
Thanks for those instructions. It's always good to get a few people to recount
their installation commands from scratch to see if there are some small
important details.
Those dependencies are a good case in point.
> It might be that the process of compiling v3.8 is quite similar to this.
Probably. I gave it a whirl with qtpovray, way back when, and what is in my
history is this:
sudo apt install git qt5-qmake qt5-default libboost-dev libboost-date-time-dev
libboost-thread-dev libz-dev libpng-dev libjpeg-dev libtiff-dev libopenexr-dev
git clone https://github.com/dickbalaska/qtpovray.git && git checkout qtpovray
&& qmake && make -j4
But then I think Dick Balaska whacked me upside the head and said "Listen, it's
as simple as:
sudo add-apt-repository ppa:qtpovray/qtpovray
sudo apt update
sudo apt upgrade
qtpovray
"
> I see now that you mention installation of official POV-Ray. The process above
> will, of coarse, always make and install an unofficial version.
>
> Are you aware of any official prebuilt binary for x86_64 Linux PCs ?
At the outset of _this_ installation thread, I went looking around, and found
that
sudo apt-get install povray
actually worked :O Which is lovely, because it can hardly get any easier than
that, excepting buying it pre-installed on the laptop.
So, I'm guessing that's an already compiled binary?
Thanks again for your review and commentary - always appreciated.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Tor Olav Kristensen" <tor### [at] TOBEREMOVEDgmailcom> wrote:
>
> Thanks for those instructions. It's always good to get a few people to recount
> their installation commands from scratch to see if there are some small
> important details.
>
> Those dependencies are a good case in point.
>
> > It might be that the process of compiling v3.8 is quite similar to this.
Right after my last post I did this.
git checkout release/v3.8.0
cd unix
./prebuild.sh
cd ..
./configure COMPILED_BY="My Name <email@address>"
make check
The result was a working POV-Ray version 3.8.0-alpha.unofficial
> Probably. I gave it a whirl with qtpovray, way back when, and what is in my
> history is this:
>
> sudo apt install git qt5-qmake qt5-default libboost-dev libboost-date-time-dev
> libboost-thread-dev libz-dev libpng-dev libjpeg-dev libtiff-dev libopenexr-dev
> git clone https://github.com/dickbalaska/qtpovray.git && git checkout qtpovray
> && qmake && make -j4
>
> But then I think Dick Balaska whacked me upside the head and said "Listen, it's
> as simple as:
>
> sudo add-apt-repository ppa:qtpovray/qtpovray
> sudo apt update
> sudo apt upgrade
> qtpovray
> "
Nice. That's useful.
> > I see now that you mention installation of official POV-Ray. The process above
> > will, of coarse, always make and install an unofficial version.
> >
> > Are you aware of any official prebuilt binary for x86_64 Linux PCs ?
>
> At the outset of _this_ installation thread, I went looking around, and found
> that
>
> sudo apt-get install povray
Yes, of course. I forgot about that. That's how I installed v3.7 on this Ubuntu
PC earlier. And since Ubuntu's repository version was already installed, I did
not want to mess up things by running the sudo make install command.
> actually worked :O Which is lovely, because it can hardly get any easier than
> that, excepting buying it pre-installed on the laptop.
>
> So, I'm guessing that's an already compiled binary?
Yes, it is. But it is probably not an official one.
> Thanks again for your review and commentary - always appreciated.
I'm glad that I can help.
--
Tor Olav
http://subcube.com
https://github.com/t-o-k
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> This installation info was given by Clipka in
> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.10064268
Yes, I recall that, as well as the discussion about renaming the .chm help file.
> However, in Windows, I use a more 'intuitive' way
Here, I think is where a screenshot or other graphic output of the directory
tree structure would be really nice for the documentation.
> But maybe this is common knowledge? I don't know.
I've learned to make as close to zero assumptions about "common knowledge" as
possible, especially when doing instructional or documentation work.
What was common knowledge in the 14th century as opposed to now?
The use of slide rules was "common knowledge" for 200+ years - and then *POOF*
we collectively forgot.
I've worked with PhD's in industry who didn't know that the GUI [B] button in MS
Word not only bolded text, but _un_bolded text. <facepalm>
"If I just take this 5-liter flask full of tetrahydrofuran and sodium-potassium
alloy, and put it under the faucet, that'll get rid of the sodium, right?" Yep.
Along with the rest of the room that your standing in...
And, in the linux world, people do that thing where: it's your first day working
at the local drug store, and so you must therefore know everything about every
product in the store, which one is "best", how all of the registers and other
things work, and must have in-depth medical knowledge to diagnose the rash on
little johnny's private parts. "Here, let me show you..." No, please.
So, although I am running linux and can do a handful of things very poorly, with
much search-engine use and finger-crossing, I really just don't know what I'm
doing, and it can't be assumed that "Well, of COURSE you 'just' do this git
thing, use THOSE flags do undo the tarball and then naturally perform a
make-check to make sure that these things reside in "the usual places"...
So I'm gonna try to write as much of it down as I can this time in one place and
make a PDF of it, and maybe most of it can wind up on the download page - which
can be the download and install page. ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
