 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Since OSX is a unix, I would have thought compiling UberPOV by following the
unix instructions would be possible. However, I have had some problems I can't
quite get my head around, so some insights or help would be appreciated.
When running the prebuild script, I get lots of warnings about a subdir-objects
option, some warnings about using an AM_PROG_AR macro in configure.ac, some
warnings about obsolete macros, and an error from sed saying Makefile.in can't
be found. I can post the full text if necessary.
I looked in the UberPOV root, and the prebuild appeared to have done something,
so I tried to run configure anyway. This bailed when checking the available
libraries with 'cannot link with the boost thread library'.
Has the prebuild failed, or are these warnings expected?
I have boost 1.54 installed (via macports, if it's important), and the
libboost-thread stuff is definitely present - configure reports this to be so,
but fails when checking if the library is usable. If the prebuild is not at
fault, what might be amiss?
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.12.2013 20:44, schrieb Bill Pragnell:
> Since OSX is a unix, I would have thought compiling UberPOV by following the
> unix instructions would be possible. However, I have had some problems I can't
> quite get my head around, so some insights or help would be appreciated.
>
> When running the prebuild script, I get lots of warnings about a subdir-objects
> option, some warnings about using an AM_PROG_AR macro in configure.ac, some
> warnings about obsolete macros, and an error from sed saying Makefile.in can't
> be found. I can post the full text if necessary.
>
> I looked in the UberPOV root, and the prebuild appeared to have done something,
> so I tried to run configure anyway. This bailed when checking the available
> libraries with 'cannot link with the boost thread library'.
>
> Has the prebuild failed, or are these warnings expected?
What you're experiencing are known problems with POV-Ray in general; the
issue with mssing Makefile.in is (presumably) related to a backward
compatibility-breaking change in the newest automake, while the boost
issue is due to a backward compatibility-breaking change in boost 1.50
and above. See the povray.unix newsgroup for how people are working
around the issue.
You ain't seen nothin' yet though; once you get through these, you'll
run into a few more problems, all of which are related to Mac OS X being
a BSD- rather than GNU-flavored Unix, and the dev team being rather
unfamiliar with the former.
The good news is that people on the 'net have already gone through the
task of getting POV-Ray to work on Mac OS X, and have reported on GitHub
not only the issues encountered, but also how they're currently working
around them. See POV-Ray's GitHub issue list for details (almost all
open issues are related to OS X):
https://github.com/POV-Ray/povray/issues?state=open
That said, the POV-Ray dev team have by now addressed all the OS X
specific issues in their own repository, and will release them on GitHub
as soon as they've got the synchronization with their own version
control system sorted out (they've been using Perforce for ages).
I expect that to happen any moment now, so I'm a bit reluctant to sneak
the fixes into UberPOV via the side door, and would rather prefer to
merge them from the POV-Ray master branch once they're there.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for the reply. I haven't tried to compile POV-Ray on Mac before - Yvo's
unofficial builds have worked perfectly for me, but of course I wanted to tinker
with UberPOV :)
clipka <ano### [at] anonymous org> wrote:
> I expect that to happen any moment now, so I'm a bit reluctant to sneak
> the fixes into UberPOV via the side door, and would rather prefer to
> merge them from the POV-Ray master branch once they're there.
So I guess I'm better off waiting for the fixes to make it back in officially?
I'm in no particular rush if this stuff is being worked on already, and I also
have a linux box I can use it on in the meantime.
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bill Pragnell <bil### [at] hotmailcom> wrote: I have already compiled
UberPOV for MacOS but I have to create an archive and update the home
page for it.
You can of course download the xcode project for the command line
version on my home page and move the uberpov sources into it.
http://megapov.inetart.net/povrayunofficial_mac/
You only have to take
care not to modify
libraries/jpeg/jconfig.h
source/backend/povray.h >> I think it is save to replace this one
vfe/syspovprotobase.h
becouse there are a few tweaks.
Don't replace the png, tiff,... libs. They are the
same for both 3.7 and UberPOV.` All in one project, no messing with make
etc...
I compiled both, gui and command line version of UberPOV f I have time I
Iwill upload UberPOV beta 3 for mac later today after work. If time
Ipermits.
Yvo > Thanks for the reply. I haven't tried to compile POV-Ray on Mac
before - Yvo's > unofficial builds have worked perfectly for me, but of
course I wanted to tinker > with UberPOV :) > > clipka
<ano### [at] anonymousorg> wrote: > > I expect that to happen any moment
now, so I'm a bit reluctant to sneak > > the fixes into UberPOV via the
side door, and would rather prefer to > > merge them from the POV-Ray
master branch once they're there. > > So I guess I'm better off waiting
for the fixes to make it back in officially? > I'm in no particular rush
if this stuff is being worked on already, and I also > have a linux box
I can use it on in the meantime. > > Bill
-- ----------------------------------- MegaPOV at:
http://megapov.inetart.net MacMegaPOV at:
http://users.skynet.be/smellenbergh E-mail: yvo(DOT)s(AT)gmx.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 03.12.2013 12:40, schrieb Yvo Smellenbergh:
> I compiled both, gui and command line version of UberPOV f I have time I
> Iwill upload UberPOV beta 3 for mac later today after work. If time
> Ipermits.
:-D
Thanks, once again, for your faithful catering to the Mac-affine wing of
the POV-Ray community!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 03.12.2013 12:40, schrieb Yvo Smellenbergh:
>
> > I compiled both, gui and command line version of UberPOV f I have time I
> > Iwill upload UberPOV beta 3 for mac later today after work. If time
> > Ipermits.
>
> :-D
>
> Thanks, once again, for your faithful catering to the Mac-affine wing of
> the POV-Ray community!
Seconded, that's amazing, thanks! I shall try it out tonight.
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 04.12.2013 11:39, schrieb Bill Pragnell:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 03.12.2013 12:40, schrieb Yvo Smellenbergh:
>>
>>> I compiled both, gui and command line version of UberPOV f I have time I
>>> Iwill upload UberPOV beta 3 for mac later today after work. If time
>>> Ipermits.
>>
>> :-D
>>
>> Thanks, once again, for your faithful catering to the Mac-affine wing of
>> the POV-Ray community!
>
> Seconded, that's amazing, thanks! I shall try it out tonight.
I'd also like to kindly ask you to try compiling from this version:
https://github.com/UberPOV/UberPOV/archive/feature/osx-support.zip
It's supposed to build fine(*) on OS X now, but I need a guinea pig to
actually try it ;-)
(* except for the boost thing. You'll still need to add
LIBS="-lboost_system -lboost_thread" to the ./configure command to get
around that one; but that's not a Mac-specific issue.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> I'd also like to kindly ask you to try compiling from this version:
>
> https://github.com/UberPOV/UberPOV/archive/feature/osx-support.zip
>
> It's supposed to build fine(*) on OS X now, but I need a guinea pig to
> actually try it ;-)
>
>
> (* except for the boost thing. You'll still need to add
> LIBS="-lboost_system -lboost_thread" to the ./configure command to get
> around that one; but that's not a Mac-specific issue.)
The prebuild script works fine now, but configure still bails at the boost check
even with your suggested LIBS switch, or with --with-boost and
--with-boost-thread set as per many other 3.7 compilation newsgroup threads (my
boost libs are installed in /opt/local/lib/, if that's relevant).
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 04.12.2013 20:04, schrieb Bill Pragnell:
> clipka <ano### [at] anonymousorg> wrote:
>> I'd also like to kindly ask you to try compiling from this version:
>>
>> https://github.com/UberPOV/UberPOV/archive/feature/osx-support.zip
>>
>> It's supposed to build fine(*) on OS X now, but I need a guinea pig to
>> actually try it ;-)
>>
>>
>> (* except for the boost thing. You'll still need to add
>> LIBS="-lboost_system -lboost_thread" to the ./configure command to get
>> around that one; but that's not a Mac-specific issue.)
>
> The prebuild script works fine now, but configure still bails at the boost check
> even with your suggested LIBS switch, or with --with-boost and
> --with-boost-thread set as per many other 3.7 compilation newsgroup threads (my
> boost libs are installed in /opt/local/lib/, if that's relevant).
Can you give any additional details (what exactly configure is
complaining about)?
You do have boost installed, do you?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Can you give any additional details (what exactly configure is
> complaining about)?
This seems to be the relevant chunk of config.log:
---------
configure:7606: checking whether the Boost::Thread library is available
configure:7638: g++ -c -pthread -D_THREAD_SAFE -I/opt/local/include
conftest.cpp >&5
configure:7638: $? = 0
configure:7653: result: yes
configure:7682: checking for exit in -lboost_thread-mt
configure:7707: g++ -o conftest -D_THREAD_SAFE -I/opt/local/include
-L/opt/local/lib conftest.cpp -lboost_thread-mt -D_THREAD_SAFE >&5
configure:7707: $? = 0
configure:7717: result: yes
configure:7849: checking whether the boost thread library is usable
configure:7869: g++ -o conftest -D_THREAD_SAFE -pthread -I/opt/local/include
-L/opt/local/lib conftest.cpp -lboost_thread-mt -D_THREAD_SAFE >&5
Undefined symbols:
"boost::system::generic_category()", referenced from:
__static_initialization_and_destruction_0(int, int)in ccjJtpIS.o
__static_initialization_and_destruction_0(int, int)in ccjJtpIS.o
"boost::system::system_category()", referenced from:
__static_initialization_and_destruction_0(int, int)in ccjJtpIS.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
---------
> You do have boost installed, do you?
Worth asking, but yes ;)
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
