Hi all

Been tinkering with UberPOV on Mac for a while (thanks Yvo!) and I find myself
wanting to also use it on a recent install of Linux Mint. So I cloned it from
github and followed the unix build instructions, only to find that
boost/tr1/memory.hpp cannot be found. Some closer investigation reveals that my
version of boost is 1.65.1, but the TR1 stuff was removed in 1.65.0.

Has anyone else encountered this? Is there an easier way to solve this than
rolling back my boost version?

Bill

Post a reply to this message

On 5/29/19 6:42 PM, Bill Pragnell wrote:
> Hi all
> 
> Been tinkering with UberPOV on Mac for a while (thanks Yvo!) and I find myself
> wanting to also use it on a recent install of Linux Mint. So I cloned it from
> github and followed the unix build instructions, only to find that
> boost/tr1/memory.hpp cannot be found. Some closer investigation reveals that my
> version of boost is 1.65.1, but the TR1 stuff was removed in 1.65.0.
> 
> Has anyone else encountered this? Is there an easier way to solve this than
> rolling back my boost version?
> 
> Bill
> 

My recollection is that something promised with respect to how headers 
would be changed when the boost feature moved into C++ didn't happen as
expected.

There was discussion of the issue at:

https://github.com/POV-Ray/povray/pull/42

and

http://news.povray.org/povray.general/thread/%3C5a233b19%241%40news.povray.org%3E/

Christoph fixed the issue while looking at:

https://github.com/POV-Ray/povray/issues/317

and it looks like the fix took two commits:

https://github.com/POV-Ray/povray/commit/1dbca0bad858f5605cc8e3a2629eb0e0dbfbb052

and

https://github.com/POV-Ray/povray/commit/a847cb72563f9d9d072ff2f9ef5300b91c8b5839

Perhaps you can steal from some of that work. I'm not aware of anything 
'easy,' so to speak, with respect to a fix.

Bill P. (The other...)

Post a reply to this message

Aha, thanks for that. Those changes are not extensive, I'll just duplicate the
fix in my local repo. Probably 'easier' than mucking about with boost, from
where I'm sitting :)

What's the best way to get those changes into UberPOV permanently? Is it
possible to do some git magic to cherry pick those commits, or could I just
apply the fix on an UberPOV branch and push it myself?

Bill

(maybe I should start signing off as Bill P just to confuse everyone :D)

Post a reply to this message

On 5/30/19 4:58 AM, Bill Pragnell wrote:
> Aha, thanks for that. Those changes are not extensive, I'll just duplicate the
> fix in my local repo. Probably 'easier' than mucking about with boost, from
> where I'm sitting :)
> 
> What's the best way to get those changes into UberPOV permanently? Is it
> possible to do some git magic to cherry pick those commits, or could I just
> apply the fix on an UberPOV branch and push it myself?
> 
> Bill
> 
> (maybe I should start signing off as Bill P just to confuse everyone :D)
> 

Christoph is the only one who can update UberPOV and he's not worked 
there in a long time.

There is a git cherry picking technique. I used exactly once years ago - 
meaning I don't remember how to do it! Search for 'git cherry pick'.

The complication in grabbing things out of the main POV-Ray master 
branch and moving it to UberPOV is the code is in some places 
significantly different. I think this a reason why UberPOV didn't take 
hold as a general test bed for things. I moved one branch to UberPOV 
(never merged) and it collided with UberPOV changes. It meant a lot of 
work which I only ever really made sure compiled - I didn't test the 
features again as part of UberPOV. Also found myself with two branches 
of the same feature. One off POV-Ray master and another off UberPOV. Too 
much work.

If you want to run UberPOV specifically I'd recommend creating a branch 
and just letting it sit there. If it's your only UberPOV branch, compile 
and run that branch. If you end up with >1 let the branches, pull each 
all into an 'UberBillP' branch off the UberPOV master branch and compile.

The last is what I've been doing. Several times a year I build a version 
with the features I want off the current POV-Ray master. Down side is 
it's getting to be a lot of branches to rebase/merge when the master 
branch changes. I'm not a git expert. Perhaps there are better ways.

Bill P.

Post a reply to this message

William F Pokorny <ano### [at] anonymousorg> wrote:
> The complication in grabbing things out of the main POV-Ray master
> branch and moving it to UberPOV is the code is in some places
> significantly different.

Yes, once I sat down to it, it was evident that the code in those commits you
linked to mostly isn't in UberPOV. The changes required were much the same
though, plus a missing iostream equality operator. I fixed it in my local copy,
and I guess I'll just hang on to that for the time being.
Thanks for the help!

Bill P not P

Post a reply to this message

On 6/1/19 5:09 PM, Bill Pragnell wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
>> The complication in grabbing things out of the main POV-Ray master
>> branch and moving it to UberPOV is the code is in some places
>> significantly different.
> 
> Yes, once I sat down to it, it was evident that the code in those commits you
> linked to mostly isn't in UberPOV. The changes required were much the same
> though, plus a missing iostream equality operator. I fixed it in my local copy,
> and I guess I'll just hang on to that for the time being.
> Thanks for the help!
> 
> Bill P not P
> 
:-) Pleased to hear you worked it out.

Bill P.

Post a reply to this message