 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
First official (beta) release of UberPOV is now available at:
https://github.com/UberPOV/UberPOV/tree/v1.37.0.0-beta.1
Windows binaries are now available as well. Just copy the uberpov*.exe
beside your pvengine*.exe.
Happy POVing!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 20.11.2013 18:10, schrieb clipka:
> First official (beta) release of UberPOV is now available at:
>
> https://github.com/UberPOV/UberPOV/tree/v1.37.0.0-beta.1
>
> Windows binaries are now available as well. Just copy the uberpov*.exe
> beside your pvengine*.exe.
>
> Happy POVing!
Sorry, posted the wrong link; while the above does point in the general
direction, the actual distribution packages can be found here:
https://github.com/UberPOV/UberPOV/releases/tag/v1.37.0.0-beta.1
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/20/2013 12:10 PM, clipka wrote:
> First official (beta) release of UberPOV is now available at:
>
> https://github.com/UberPOV/UberPOV/tree/v1.37.0.0-beta.1
>
> Windows binaries are now available as well. Just copy the uberpov*.exe
> beside your pvengine*.exe.
>
> Happy POVing!
I had some problems with Makefile.in(s). first in ~uberpov/unix while
running prebuild.sh then during configure phase ... this time
~uberpov/vfe/Makefile.in and ~uberpov/source/Makefile.in are problems. I
ended up getting those files from my povray git build directory and got
a good configure ... or so I thought. make halts right away with the
following:
make: *** No rule to make target `disp_sdl.cpp', needed by `disp_sdl.o'.
Stop.
oh ... ~unix/prebuild clean doesn't seem to be working either
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 20.11.2013 23:40, schrieb James Holsenback:
> On 11/20/2013 12:10 PM, clipka wrote:
>> First official (beta) release of UberPOV is now available at:
>>
>> https://github.com/UberPOV/UberPOV/tree/v1.37.0.0-beta.1
>>
>> Windows binaries are now available as well. Just copy the uberpov*.exe
>> beside your pvengine*.exe.
>>
>> Happy POVing!
>
> I had some problems with Makefile.in(s). first in ~uberpov/unix while
> running prebuild.sh then during configure phase ... this time
> ~uberpov/vfe/Makefile.in and ~uberpov/source/Makefile.in are problems.
Can you specify "some problems"?
> I ended up getting those files from my povray git build directory and got
> a good configure ... or so I thought. make halts right away with the
> following:
>
> make: *** No rule to make target `disp_sdl.cpp', needed by `disp_sdl.o'.
> Stop.
The files generated by POV-Ray's ./prebuild.sh won't cut it, due to
various differences related to the project name. IIRC some of them were
inevitable to make autoconf happy with the different project name.
> oh ... ~unix/prebuild clean doesn't seem to be working either
From what I can tell, prebuild.sh calls the generated makefiles for
some part of the cleanup job, so I'm not too surprised there either.
As I'm not really a Linux jockey I'd be happy about any help I can get
for sorting out those problems you experience.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/20/2013 06:17 PM, clipka wrote:
> As I'm not really a Linux jockey I'd be happy about any help I can get
> for sorting out those problems you experience.
well ... i'm not into learning the in's and out's of make, and i guess
that put's me square in the middle of knowing just enough to be
dangerous, because things got broke quick. i think i'll hang back and
wait to see if converting to cmake gains any traction ... seems like
povray is becoming a windows-centric project
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 00:45, schrieb James Holsenback:
> On 11/20/2013 06:17 PM, clipka wrote:
>> As I'm not really a Linux jockey I'd be happy about any help I can get
>> for sorting out those problems you experience.
>
> well ... i'm not into learning the in's and out's of make, and i guess
> that put's me square in the middle of knowing just enough to be
> dangerous, because things got broke quick. i think i'll hang back and
> wait to see if converting to cmake gains any traction ... seems like
> povray is becoming a windows-centric project
I don't think so; it has in the past years, but with the AGPL, Git repo
and all I expect it to swing back a deal towards Linux and, hopefully,
other platforms as well.
(That said, CMake may turn out to become part of that process of course.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 20.11.2013 23:40, schrieb James Holsenback:
> On 11/20/2013 12:10 PM, clipka wrote:
>> First official (beta) release of UberPOV is now available at:
>>
>> https://github.com/UberPOV/UberPOV/tree/v1.37.0.0-beta.1
>>
>> Windows binaries are now available as well. Just copy the uberpov*.exe
>> beside your pvengine*.exe.
>>
>> Happy POVing!
>
> I had some problems with Makefile.in(s). first in ~uberpov/unix while
> running prebuild.sh then during configure phase ... this time
> ~uberpov/vfe/Makefile.in and ~uberpov/source/Makefile.in are problems.
Looks like autoconf hates you when two .cpp files in the project have
the same name, even if they're in different directories. In this case it
is "backend/colour/colour.cpp" and the newly added "base/colour.cpp".
I definitely need to do something about it, or the problem will also
surface in POV-Ray proper (same change there, except that it hasn't made
it into the Git repo yet).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 01:40, schrieb clipka:
> Am 20.11.2013 23:40, schrieb James Holsenback:
>> I had some problems with Makefile.in(s). first in ~uberpov/unix while
>> running prebuild.sh then during configure phase ... this time
>> ~uberpov/vfe/Makefile.in and ~uberpov/source/Makefile.in are problems.
Fix available now at:
https://github.com/UberPOV/UberPOV
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/20/2013 09:08 PM, clipka wrote:
> Am 21.11.2013 01:40, schrieb clipka:
>> Am 20.11.2013 23:40, schrieb James Holsenback:
>
>>> I had some problems with Makefile.in(s). first in ~uberpov/unix while
>>> running prebuild.sh then during configure phase ... this time
>>> ~uberpov/vfe/Makefile.in and ~uberpov/source/Makefile.in are problems.
>
> Fix available now at:
>
> https://github.com/UberPOV/UberPOV
>
OK thanks ... got a good build, however when when I did uberpov
--version a slight problem:
ash@linux-c2bm:~/ScratchPad/git/uberpov $ uberpov --version
uberpov: cannot open the system configuration file
/usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
uberpov: cannot open the user configuration file
/home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
uberpov: I/O restrictions are disabled
UberPOV 3.7.0.unofficial
Notice the space in uberpov.pov above ... the file lives properly in the
root of the build directory. It did /not/ get copied into
/usr/local/etc/uberpov/1.37 (uberpov.ini /did/). ~users/.uberpov on down
did /not/ get created ... copied uberpov.conf to the two places it
needed to be and uberpov --version now at least id's proper because it
found the users conf file ... guess there's an error in the source
somewher that is causing it to look for "uberpovray. conf"
uberpov --version
uberpov: cannot open the system configuration file
/usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
UberPOV 3.7.0.unofficial
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2013 06:11 AM, James Holsenback wrote:
> uberpov --version now at least id's proper
hmmm ... take it back!
> uberpov --version
> uberpov: cannot open the system configuration file
> /usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
> UberPOV 3.7.0.unofficial
shouldn't that be 1.3.7 ... VERSION file in root of build dir has:
1.37.0.0-alpha
so that means ~uberpov/unix/VERSION is correct ... could it be line 88
in ~uberpov/source/backend/povray.h ????
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 13:01, schrieb James Holsenback:
> On 11/21/2013 06:11 AM, James Holsenback wrote:
>> uberpov --version now at least id's proper
>
> hmmm ... take it back!
>
>> uberpov --version
>> uberpov: cannot open the system configuration file
>> /usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
>> UberPOV 3.7.0.unofficial
>
> shouldn't that be 1.3.7 ... VERSION file in root of build dir has:
>
> 1.37.0.0-alpha
>
> so that means ~uberpov/unix/VERSION is correct ... could it be line 88
> in ~uberpov/source/backend/povray.h ????
No, that line is fine. In some places the program does tell the user
what official version of POV-Ray it is based on.
Found the culprits though; Git master should be ok now.
Thanks for finding those buggers, I'd probably never have seen them myself.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2013 07:39 AM, clipka wrote:
> Am 21.11.2013 13:01, schrieb James Holsenback:
>> On 11/21/2013 06:11 AM, James Holsenback wrote:
>>> uberpov --version now at least id's proper
>>
>> hmmm ... take it back!
>>
>>> uberpov --version
>>> uberpov: cannot open the system configuration file
>>> /usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
>>> UberPOV 3.7.0.unofficial
>>
>> shouldn't that be 1.3.7 ... VERSION file in root of build dir has:
>>
>> 1.37.0.0-alpha
>>
>> so that means ~uberpov/unix/VERSION is correct ... could it be line 88
>> in ~uberpov/source/backend/povray.h ????
>
> No, that line is fine. In some places the program does tell the user
> what official version of POV-Ray it is based on.
>
> Found the culprits though; Git master should be ok now.
>
> Thanks for finding those buggers, I'd probably never have seen them myself.
>
yer welcome ... was it on purpose that I can't view files in uber on
perforce
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 20-11-2013 18:10, clipka wrote:
> Happy POVing!
This is GREAT!
I am now playing around with the sample scene files before trying out on
my own scenes, but it looks fantastic.
Keep up the good work!
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2013 07:39 AM, clipka wrote:
> Am 21.11.2013 13:01, schrieb James Holsenback:
> Found the culprits though; Git master should be ok now.
uberpov --version
uberpov: cannot open the user configuration file
/home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
UberPOV 1.37.0.0-alpha
OK ... id's proper now. uberpov.conf made it to
/usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 13:50, schrieb James Holsenback:
> yer welcome ... was it on purpose that I can't view files in uber on
> perforce
Of course. I wouldn't want /you/ sniffing around in there ;-)
Seriously, I have no idea how I'd even be able to change the permissions.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 14:30, schrieb James Holsenback:
> On 11/21/2013 07:39 AM, clipka wrote:
>> Am 21.11.2013 13:01, schrieb James Holsenback:
>> Found the culprits though; Git master should be ok now.
>
> uberpov --version
> uberpov: cannot open the user configuration file
> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
> UberPOV 1.37.0.0-alpha
>
>
> OK ... id's proper now. uberpov.conf made it to
> /usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory
Did you make install?
If not, then this is to be expected.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 14:51, schrieb clipka:
> Am 21.11.2013 14:30, schrieb James Holsenback:
>> On 11/21/2013 07:39 AM, clipka wrote:
>>> Am 21.11.2013 13:01, schrieb James Holsenback:
>>> Found the culprits though; Git master should be ok now.
>>
>> uberpov --version
>> uberpov: cannot open the user configuration file
>> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
>> UberPOV 1.37.0.0-alpha
>>
>>
>> OK ... id's proper now. uberpov.conf made it to
>> /usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory
>
> Did you make install?
>
> If not, then this is to be expected.
Uh... forget that statement. If you hadn't done make install, there
would be nothing in /usr/local/etc..., would there.
But it also means you installed as root; could there possibly be an
.uberpov directory now in the root's home directory?
What does POV-Ray proper do in that situation, anyway?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2013 14:30, schrieb James Holsenback:
> On 11/21/2013 07:39 AM, clipka wrote:
>> Am 21.11.2013 13:01, schrieb James Holsenback:
>> Found the culprits though; Git master should be ok now.
>
> uberpov --version
> uberpov: cannot open the user configuration file
> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
> UberPOV 1.37.0.0-alpha
As a side note, this message is just a warning; UberPOV should be able
to run just fine without a ~/.uberpov/1.37/uberpov.conf, except that it
prints this message. Same as POV-Ray does when it misses its
~/.povray/3.7/povray.conf file.
You might want to check though whether UberPOV accidently wrote an
uberpov.conf somewhere into ~/.povray, or even replaced POV-Ray's .conf
file. That would be seriously bad.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
