Request port of Stanford "rayshade"

[murrayeisenberg@…]

This is to request a port of the Rayshade application for creating ray-traced images. Source and other information is available at ​http://www-graphics.stanford.edu/~cek/rayshade/rayshade.html. The program is written in C, yacc, and lex. Although an OS X port is available from that site, it dates to 1992 and does not work on current or recent versions of OS X.

[cooljeanius (Eric Gallager)]

1992? OS X wasn't even introduced yet at that point then...

[murrayeisenberg@…]

Replying to egall@…:

1992? OS X wasn't even introduced yet at that point then...

Sorry, yes of course you're correct. I mean just Mac OS.

[cooljeanius (Eric Gallager)]

Trying it out now... this interactive configure script is reminding me a lot of perl's...

[cooljeanius (Eric Gallager)]

Cc Me!

[cooljeanius (Eric Gallager)]

idk, after trying to build it, I think this might be just too old...

[ryandesign (Ryan Carsten Schmidt)]

Replying to murrayeisenberg@…:

Although an OS X port is available from that site, it dates to 1992 and does not work on current or recent versions of OS X.

A prerequisite for creating a MacPorts port for a program is that the program compiles on OS X. Work with the developers of rayshade to get it to compile on OS X. Once it does, we can create a port for it.

[cooljeanius (Eric Gallager)]

Replying to ryandesign@…:

Work with the developers of rayshade to get it to compile on OS X. Once it does, we can create a port for it.

I doubt the original developers of it even exist any more, given that they haven't worked on it in 21 years...

[ryandesign (Ryan Carsten Schmidt)]

Precisely.

Anyway, here's the start of a Portfile.

I patched the Configure script to remove incorrect warnings and errors and to look in ${prefix} first so that our newer version of bison gets used. Actually I think bison is also used at runtime.

During configuration, it tries to use nm to figure out what's in the C library. It uses printf as its litmus test, and printf doesn't seem to be in OS X's C library—or nm isn't the right way to make that determination. If we can fix this it might help it find some other functions.

The configuration asks some questions I didn't know the answers to, like in which ways the compiler supports the void type or how many bits of randomness the random() function produces. (The ​random() manpage says all bits are random, but it returns a long; doesn't the size of a long vary based on the build architecture?) I left those answers at the defaults.

After configuration, it runs make depend, which generates a lot of warnings and one error, I believe because it uses cpp which doesn't understand some things in the system headers. Using $CC -E wouldn't encounter those errors but is not an option because rayshade needs to feed things to the C preprocessor via stdin and it seems that only cpp understands that.

Then the build fails with various errors like:

hf.c:470:1: error: static declaration of 'CreateHfTriangle' follows non-static declaration

hf.c:670:1: error: static declaration of 'GetQueuedTri' follows non-static declaration

extended.c:58:1: error: static declaration of 'ExtendedIntens' follows non-static declaration

fog.c:31:2: error: function declared in block scope cannot have 'static' storage class

texture.c:165:3: error: non-void function 'TextToUV' should return a value [-Wreturn-type]

And then finally:

/usr/include/strings.h:76:7: error: expected parameter declarator

/usr/include/strings.h:76:7: error: expected ')'