I've had a little play compiling the UNIX version for the
Mac, after finally getting my head around some library problems,
and finding out that none of the ./configure options for compiling 
without X actually work (configure says X disabled, Makefile says 
compile in povxlib.c) I found some interesting-ish results.


Based on biscuit.pov...

The command line version parses much faster 2 seconds cf  16 seconds

The offical version renders faster 9 seconds cf 15 seconds.

I'll try it on a bigger file soon, is benchmark.pov suitable for
benchmarking parsing or can someone suggest a better scene.

Dave

Post a reply to this message

Could you, or someone else, please detail the steps you used to compile
this for those of us who have never tried such things?

James

In article <3d7bbc9c$1@news.povray.org>, David Burnett
<var### [at] ntlworldcom> wrote:

> I've had a little play compiling the UNIX version for the
> Mac, after finally getting my head around some library problems,
> and finding out that none of the ./configure options for compiling 
> without X actually work (configure says X disabled, Makefile says 
> compile in povxlib.c) I found some interesting-ish results.
> 
> 
> Based on biscuit.pov...
> 
> The command line version parses much faster 2 seconds cf  16 seconds
> 
> The offical version renders faster 9 seconds cf 15 seconds.
> 
> I'll try it on a bigger file soon, is benchmark.pov suitable for
> benchmarking parsing or can someone suggest a better scene.
> 
> Dave

Post a reply to this message

On Mon, 11 Nov 2002 10:23:17 +0000, James Gray wrote:

> Could you, or someone else, please detail the steps you used to compile
> this for those of us who have never tried such things?
> 
> 
I'll have go, it was a while ago....

Number one is install the latest developer software from ADC.

The next thing you need are versions of libjpeg, libtiff and zlib, I
compiled these from source due to 10.2 being a new thing back then, but
you can get them from fink amongst others now. I had to do some fiddling
with the builds to get them to work mostly to do with compatability
versions, so I suggest getting the canned versions if you can.

Download the UNIX sources, run configure as usual. I used...


./configure --with-x=no -prefix=/Users/vargol

go to the src directory and edit the Makefile, remove the reference to
povxlib.o from the povray_OBJECTS section if its still in there, and
povxlib.c from povray_SOURCES. This is what the --with-x=no is supposed to
do, they might have fixed it since I built POV.

then

make
make install

if you don't use the prefix option you will need to sudo make install
instead.

If you've never built anything from the command line before just give us a
yell and I'll expand on the instructions.

Dave

Post a reply to this message

Okay, I ran into problems, so I'm taking you up on your offer for more
help.  Thanks in advance.

James

In article <3dd16472$1@news.povray.org>, David Burnett
<var### [at] ntlworldcom> wrote:

> Number one is install the latest developer software from ADC.

I had this already done.

> The next thing you need are versions of libjpeg, libtiff and zlib, I
> compiled these from source due to 10.2 being a new thing back then, but
> you can get them from fink amongst others now. I had to do some fiddling
> with the builds to get them to work mostly to do with compatability
> versions, so I suggest getting the canned versions if you can.

I installed fink.  Ran into a few minor issues there, but eventually got
it sorted out.  I installed libjpeg and libpng with it.

You listed libtiff instead of libpng, but the README didn't so I assumed
you were remembering it wrong, which could be my error, of course.  I also
didn't install zlib because I was led to believe Mac OS X 10.2 had it by
default, again I could be wrong.

> Download the UNIX sources, run configure as usual. I used...
> 
> 
> ./configure --with-x=no -prefix=/Users/vargol

I didn't use prefix but was prepared to sudo when the time came.

> go to the src directory and edit the Makefile, remove the reference to
> povxlib.o from the povray_OBJECTS section if its still in there, and
> povxlib.c from povray_SOURCES. This is what the --with-x=no is supposed to
> do, they might have fixed it since I built POV.

I did remove these two little items.

> then
> 
> make

This is where I lost it.  Make spit out some very strange errors:

...
cc1plus: invalid option `arch=i586'
cc1plus: invalid option `align-double'
cc1plus: invalid option `inline-all-stringops'
cc1plus: bad value (i586) for -mcpu= switch
make[1]: *** [atmosph.o] Error 1
make: *** [all-recursive] Error 1

It obviously guessed my platform wrong, I'm on a dual G4.  Any advice is
greatly appreciated!

James

Post a reply to this message

On Thu, 14 Nov 2002 16:28:47 +0000, James Gray wrote:

 
> This is where I lost it.  Make spit out some very strange errors:
> 
> ...
> cc1plus: invalid option `arch=i586'
> cc1plus: invalid option `align-double'
> cc1plus: invalid option `inline-all-stringops'
> cc1plus: bad value (i586) for -mcpu= switch
> make[1]: *** [atmosph.o] Error 1
> make: *** [all-recursive] Error 1

That's interesting, it didn't happen to me.

I think the best way to attack this is to edit the makefile.

I'm guessing here but you need to manually change the line
with the CXXFLAGS on it.

Mine ended up as 

CXXFLAGS = $(NOMULTICHAR) -O3 -maltivec -mtune=powerpc

although I think it started as 

CXXFLAGS = $(NOMULTICHAR) -O3

before I added the gcc 3.x powerpc tuning.

If that doesn't work let me know and I'll post my makefile which
should work.

Dave

Post a reply to this message

In article <3dd667b3$1@news.povray.org>, David Burnett
<var### [at] ntlworldcom> wrote:

> If that doesn't work let me know and I'll post my makefile which
> should work.


Hmm, well, it went a lot farther this time.  But eventually, it died, for
different reasons.  It said

jpeg_pov.cpp:142:21: jpeglib.h: No such file or directory
jpeg_pov.cpp:164: field `jerr' has incomplete type
jpeg_pov.cpp:165: 'jpeg_source_mgr' is used as a type, but is not defined as a 
   type.
jpeg_pov.cpp:166: 'jpeg_destination_mgr' is used as a type, but is not defined 
   as a type.
jpeg_pov.cpp:169: parse error before `[' token

...several more pages of erros and warnings about jpeg_pov here...

jpeg_pov.cpp:263: redefinition of `int METHODDEF'
jpeg_pov.cpp:220: `int METHODDEF' previously defined here
jpeg_pov.cpp:263: confused by earlier errors, bailing out
make[1]: *** [jpeg_pov.o] Error 1
make: *** [all-recursive] Error 1

I know, I know, I'm just full of problems.  Seriously, thanks again for
your help.

James

Post a reply to this message

On Sat, 16 Nov 2002 12:50:19 +0000, James Gray wrote:

First you'll be glad to know you're not alone with the
x86 options thing, there's a guy with the same complaint
in povray.programming

> jpeg_pov.cpp:142:21: jpeglib.h: No such file or directory

I'm afraid your going to look for jpeglib.h on your hard drive.
I appear to have a three copies, probably due to fink source 
based installs after building the library myself.

look in /sw/includes/ first, thats where fink would have installed 
a copy, also look in /usr/local/includes which is the 'right' place
as far as unices are concerned.

Now this is stretching my 'make' knowledge but I think the best
thing to do is add

-I /sw/includes

to the CCXFLAGS line in src/makefile (assuming that fink installed 
acopy there) I'm not sure this is the best place for it but it 
should work there, and I think -I is a compiler option.

Dave

Post a reply to this message

In article <3dd7ad2c$1@news.povray.org>, David Burnett
<var### [at] ntlworldcom> wrote:

> On Sat, 16 Nov 2002 12:50:19 +0000, James Gray wrote:
> 
> First you'll be glad to know you're not alone with the
> x86 options thing, there's a guy with the same complaint
> in povray.programming

Yeah, unfortunately it's looking to me like the command line install has a
long way to go.

> > jpeg_pov.cpp:142:21: jpeglib.h: No such file or directory
> 
> I'm afraid your going to look for jpeglib.h on your hard drive.
> I appear to have a three copies, probably due to fink source 
> based installs after building the library myself.
>
> look in /sw/includes/ first, thats where fink would have installed 
> a copy, also look in /usr/local/includes which is the 'right' place
> as far as unices are concerned.

It's in the fink location, as you suspected.

> Now this is stretching my 'make' knowledge but I think the best
> thing to do is add
> 
> -I /sw/includes

This, -I /sw/includes/jpeglib.h, and -include /sw/includes/jpeglib.h all
appear to have no effect.  I get the exact same errors, when it runs into
the jpeg file.

Other ideas?

James

Post a reply to this message

On Mon, 18 Nov 2002 11:02:16 +0000, James Gray wrote:

>> -I /sw/includes
> 
> This, -I /sw/includes/jpeglib.h, and -include /sw/includes/jpeglib.h all
> appear to have no effect.  I get the exact same errors, when it runs into
> the jpeg file.
> 
> Other ideas?

It's me, forgetting how gcc works, too much time in IDE's. TRy...

-I/sw/includes

NB No space after the -I and just the directory path with no trailing
foreslash.

Dave

Post a reply to this message

In article <3dd944dd$1@news.povray.org>, David Burnett
<var### [at] ntlworldcom> wrote:

> On Mon, 18 Nov 2002 11:02:16 +0000, James Gray wrote:
> 
> >> -I /sw/includes
> > 
> > This, -I /sw/includes/jpeglib.h, and -include /sw/includes/jpeglib.h all
> > appear to have no effect.  I get the exact same errors, when it runs into
> > the jpeg file.
> > 
> > Other ideas?
> 
> It's me, forgetting how gcc works, too much time in IDE's. TRy...
> 
> -I/sw/includes
> 
> NB No space after the -I and just the directory path with no trailing
> foreslash.

This didn't seem to change anything, unfortunately.

James

Post a reply to this message