 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi folks,
has anybody compiled the Superpatch for POVRay in an Unix
enviroment. Can anybody give me advice how to do this?
I will appreciate any help
Thanks
chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 May 1999 11:12:00 -0500, Christian Wietholt wrote:
>Hi folks,
>
>has anybody compiled the Superpatch for POVRay in an Unix
>enviroment. Can anybody give me advice how to do this?
>
>I will appreciate any help
It took me a while, but I succeeded in getting the superpatch
to build with the Unix sources and the Cygwin toolkit under
Windows NT. You should be able to use my makefiles and other
modifications to build it with the standard GNU tools under
your favorite Unix. I can't maintain my website from here,
so you'll have to go over to povray.binaries.programming to
get the patch. Just unzip it in your source directory (it
should replace frame.h, parse.h, and unix/makefile) and make
it as you usually would.
For obvious reasons, I haven't tested this with the X or SVGA
versions. If anyone has any problems with those, let me know.
This does not include the shared library support, as far as I
know. I need to consult the original isosurface materials to
figure out how that's supposed to work, and those are at home.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron,
Thank yoy very much for helping me. I really apreciate that.
At this time I am trying to compile your sources, but I found
some errors. Two of them I could fix, but about the third I am
not sure what to do exactly, I do not much about the sources,
perhaps you can help with this problem.
Bug report :
First:
In the makefile there is a little error. I think the two
lines beginning with C:\.... are there accidently.
......
radiositDEP = $(SRCDIR)/radiosit.c \
C:\Cygnus\B19\H-i386-cygwin32\lib\gcc-lib\i386-cygwin32\egcs-2.91.57\..\..\..\..\i386-cygwin32\include\string.h
\
C:\Cygnus\B19\H-i386-cygwin32\lib\gcc-lib\i386-cygwin32\egcs-2.91.57\..\..\..\..\i386-cygwin32\include\_ansi.h
\
$(SRCDIR)/frame.h config.h $(SRCDIR)/lighting.h $(SRCDIR)/point.h
$(SRCDIR)/vlbuffer.h $(SRCDIR)/bbox.h $(SRCDIR)/vector.h \
$(SRCDIR)/povray.h $(SRCDIR)/atmosph.h $(SRCDIR)/camera.h
$(SRCDIR)/media.h
.....
Second:
file f_func.c line 207
//*(calc_stack_top)= pow(
ABS(*(calc_stack_top)),*(calc_stack_top+1));
An ansi C Compiler does not understand the // - comment and it is
confusing
because of the * after the // to. I changed it that way :
/* *(calc_stack_top)= pow(
ABS(*(calc_stack_top)),*(calc_stack_top+1)); */
otherwise I had some errors
Third:
Here I don't know exactly what to do.
"../f_param.c", line 78: error(1164): argument of type "OBJECT *" is
incompatible with parameter of type "PARAMETRIC *"
if (! Intersect_Par_Box (Ray, Object, &Depth1, &Depth2, &Side1,
&Side2))
^
I put here a cast in like :
if (! Intersect_Par_Box (Ray, (PARAMETRIC*)Object, &Depth1,
&Depth2, &Side1, &Side2))
"../f_param.c", line 501: error(1143): declaration is incompatible with
"PRECOMP_PAR_DATA *Precompute_Parametric_Values(PARAMETRIC *,
char,
int)" (declared at line 158 of "../isosrf.h")
PRECOMP_PAR_DATA *Precompute_Parametric_Values (Par, flags, depth)
^
This problem I think I fixed by changing the line from
PRECOMP_PAR_DATA *Precompute_Parametric_Values (Par, flags, depth)
PARAMETRIC *Par;
char flags;
int depth;
to
PRECOMP_PAR_DATA *Precompute_Parametric_Values (PARAMETRIC * Par, char
flags, int depth)
Now it finished compilation but I am not sure if the cast will do the
job
during runtime. What do you think about that?
I am looking forward to hearing from you.
chris
> On Fri, 21 May 1999 11:12:00 -0500, Christian Wietholt wrote:
> >Hi folks,
> >
> >has anybody compiled the Superpatch for POVRay in an Unix
> >enviroment. Can anybody give me advice how to do this?
> >
> >I will appreciate any help
>
> It took me a while, but I succeeded in getting the superpatch
> to build with the Unix sources and the Cygwin toolkit under
> Windows NT. You should be able to use my makefiles and other
> modifications to build it with the standard GNU tools under
> your favorite Unix. I can't maintain my website from here,
> so you'll have to go over to povray.binaries.programming to
> get the patch. Just unzip it in your source directory (it
> should replace frame.h, parse.h, and unix/makefile) and make
> it as you usually would.
>
> For obvious reasons, I haven't tested this with the X or SVGA
> versions. If anyone has any problems with those, let me know.
>
> This does not include the shared library support, as far as I
> know. I need to consult the original isosurface materials to
> figure out how that's supposed to work, and those are at home.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 May 1999 16:15:12 -0500, Christian Wietholt wrote:
>In the makefile there is a little error. I think the two
>lines beginning with C:\.... are there accidently.
Yes, they are. cpp -MMD is supposed to ignore system headers, but
apparently it missed some (I'm using egcs 1.1). The dependencies
were generated automatically and massaged by a Perl script, so
while they're accurate, it's easy for bugs like that to sneak in.
>Second:
>
>file f_func.c line 207
>
> //*(calc_stack_top)= pow(
>ABS(*(calc_stack_top)),*(calc_stack_top+1));
You are correct. I had to fix that one, too, but I forgot to add
it to my zip file.
>Third:
>
>Here I don't know exactly what to do.
>
>"../f_param.c", line 78: error(1164): argument of type "OBJECT *" is
> incompatible with parameter of type "PARAMETRIC *"
...
>I put here a cast in like :
>
> if (! Intersect_Par_Box (Ray, (PARAMETRIC*)Object, &Depth1,
>&Depth2, &Side1, &Side2))
I'm sure this is okay. I'm surprised my egcs didn't complain about it.
OBJECT is the generic superclass to PARAMETRIC. You got to that line
through the POV equivalent of a virtual function pointer, so you know
Object is in fact a PARAMETRIC. The cast should be completely safe.
>PRECOMP_PAR_DATA *Precompute_Parametric_Values (Par, flags, depth)
>PARAMETRIC *Par;
>char flags;
>int depth;
>
>to
>
>PRECOMP_PAR_DATA *Precompute_Parametric_Values (PARAMETRIC * Par, char
>flags, int depth)
This should be fine, too. I need to go eradicate the last vestiges of
K&R from all this code someday; does anyone know a warning that I can
enable to point out K&R-style function headers?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron,
I just tested povray and x-povray both with shapes.pov and
with skyvase.pov. Both versions are working normaly. But
I could not test the new functions yet, I hope they will work
too.
> On Fri, 21 May 1999 16:15:12 -0500, Christian Wietholt wrote:
>
> >In the makefile there is a little error. I think the two
> >lines beginning with C:\.... are there accidently.
>
> Yes, they are. cpp -MMD is supposed to ignore system headers, but
> apparently it missed some (I'm using egcs 1.1). The dependencies
> were generated automatically and massaged by a Perl script, so
> while they're accurate, it's easy for bugs like that to sneak in.
I am not using the egcs. I am using the original SGI C-Compiler, and
I had similar experiences that the SGI Compiler is very sensitiv.
> >Third:
> >
> >Here I don't know exactly what to do.
> >
> >"../f_param.c", line 78: error(1164): argument of type "OBJECT *" is
> > incompatible with parameter of type "PARAMETRIC *"
> ...
> >I put here a cast in like :
> >
> > if (! Intersect_Par_Box (Ray, (PARAMETRIC*)Object, &Depth1,
> >&Depth2, &Side1, &Side2))
>
> I'm sure this is okay. I'm surprised my egcs didn't complain about it.
> OBJECT is the generic superclass to PARAMETRIC. You got to that line
> through the POV equivalent of a virtual function pointer, so you know
> Object is in fact a PARAMETRIC. The cast should be completely safe.
Good to know that my suggestion was correct, so I don't have to recompile
everything again.
> >PRECOMP_PAR_DATA *Precompute_Parametric_Values (Par, flags, depth)
> >PARAMETRIC *Par;
> >char flags;
> >int depth;
> >
> >to
> >
> >PRECOMP_PAR_DATA *Precompute_Parametric_Values (PARAMETRIC * Par, char
> >flags, int depth)
>
> This should be fine, too. I need to go eradicate the last vestiges of
> K&R from all this code someday; does anyone know a warning that I can
> enable to point out K&R-style function headers?
Sorry, but I don't know anything about such warnings. Strange is that was
the only error of this kind although there are many more function declared
like this. But now it is working and I think we don't have to worry about
it.
Again I wish to thank you very much for your support. I hope I can render
my volumetric data soon.
Take care
chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 May 1999 16:46:57 -0500, Christian Wietholt wrote:
>Ron,
>
>I just tested povray and x-povray both with shapes.pov and
>with skyvase.pov. Both versions are working normaly. But
>I could not test the new functions yet, I hope they will work
>too.
You can get some demo files that Gilles Tran just posted in
povray.binaries.scene-files to test the isosurface functionality.
It should work okay; I tested my cygwin build with his iso_egg.pov
script and it looked just like the output from my MSVC build.
>Again I wish to thank you very much for your support. I hope I can render
>my volumetric data soon.
The fun might be just beginning. You still have to figure out how
to build i_dat3d.so on Unix, or how to take the code from it and
shoehorn it into isofunc.c. I'll look around and see what I can
find in the original (3.0) isosurface source on this problem.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron,
I am just testing the superpatch with the demo files from Gilles
Tran and it seems to be working fine. That are great news.
Not so great is your last section. You mean we are not ready with
it. I suppose that the dat3d library is exactly what I need for my
volumetric data.
I think I can't be very helpful with porting the i_dat3d.so to Unix.
I have no idea what povray or the isosurface patch exactly does.
I am a beginner with povray. But I will take a look on that 3d
thing.
Thanks again
chris
> On Fri, 21 May 1999 16:46:57 -0500, Christian Wietholt wrote:
> >Ron,
> >
> >I just tested povray and x-povray both with shapes.pov and
> >with skyvase.pov. Both versions are working normaly. But
> >I could not test the new functions yet, I hope they will work
> >too.
>
> You can get some demo files that Gilles Tran just posted in
> povray.binaries.scene-files to test the isosurface functionality.
> It should work okay; I tested my cygwin build with his iso_egg.pov
> script and it looked just like the output from my MSVC build.
>
> >Again I wish to thank you very much for your support. I hope I can render
> >my volumetric data soon.
>
> The fun might be just beginning. You still have to figure out how
> to build i_dat3d.so on Unix, or how to take the code from it and
> shoehorn it into isofunc.c. I'll look around and see what I can
> find in the original (3.0) isosurface source on this problem.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi
> Windows NT. You should be able to use my makefiles and other
> modifications to build it with the standard GNU tools under
> your favorite Unix. I can't maintain my website from here,
> so you'll have to go over to povray.binaries.programming to
Hmmm...I can't find a group with that name on news.povray.org. Do you
use another server ?
CU
Dodger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 23 May 1999 01:12:43 +0200, Bjoern Jaeger
<joe### [at] uni-paderborn de> wrote:
>
>Hi
>
>> Windows NT. You should be able to use my makefiles and other
>> modifications to build it with the standard GNU tools under
>> your favorite Unix. I can't maintain my website from here,
>> so you'll have to go over to povray.binaries.programming to
>Hmmm...I can't find a group with that name on news.povray.org. Do you
>use another server ?
Nope, there are no other servers carrying povray.*. It's definitely
on news.povray.org. You might have to do whatever your newsreader
does to retrieve new groups.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 23 May 1999 01:12:43 +0200, Bjoern Jaeger
<joe### [at] uni-paderbornde> wrote:
>Hmmm...I can't find a group with that name on news.povray.org. Do you
>use another server ?
The name of the group is actually 'povray.programming'.
--
Alan
--------------------------------------------------------------------
http://www.povray.org - Home of the Persistence of Vision Ray Tracer
news.povray.org - where POV-Ray enthusiasts from around the world
- get together to exchange ideas and experiences
--------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
