Re: Collision/Compiling Problems
John Rohlf (jrohlf++at++tubes)
Fri, 6 May 94 11:57:07 PDT
>
> I am having some problems getting collision detection to work
> in a simulation that I am writing using Performer 1.2. Considering that
> the faq and release notes warned that the pfuCollide functions are
> jumpy I set out writing my own. After implementing simple terrain
> following (just like pfuCollideGrnd returning zpr) I decided to test
> out the pfu version. Here's the problem:
>
> When I compile my code that calls pfNodeTravMask, pfSegsIsectNode and
> pfQueryHit everything goes nicely and I have great performance.
>
> When I try to use the pfuCollideGrnd function as a replacement
> with all of the same links (including a link to libpfutil.a) and all of
> the same includes (including #include "/usr/src/Performer/include/pfutil.h")
> I get the following:
>
>
> cc pfobj2.o vrnav.o pftri.o vr.o -o vr -xansi -D__STDC__ -I. -I..
> -I/usr/src/Performer/include -I/usr/include/Performer /usr/lib/libpf.a
> /usr/src/Performer/lib/libpfutil.a /usr/lib/libpr.a -lmpc -limage -lfm
> -lgl_s -lX11 -lm -lfpe -lC
>
> /usr/bin/ld:
> Undefined:
> pfNodeTravMask
> pfMQueryHit
> pfSegsIsectNode
> pfQueryHit
> *** Error code 1
>
> Stop.
>
>
> So almost identical versions of code are having problems finding functions
> that should be easily found. This isn't the first time I have had a
> problem with mysteriously undefined functions (just the most frustrating).
> Obviously I have overlooked some small something, or we have installed
> Performer incorrectly.
>
> Any insight is greatly appreciated.
>
You need to put libpfutil before libpf since libpfutil references
libpf functions.
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:50:16 PDT