Re: [Plib-devel] New CVS of PLIB pre-1.3.1

[Steve B. <sjb...@ai...>]

"Curtis L. Olson" wrote:

> Is there any way that you can engineer things on the plib end to
> generate some sort of helpful error when a current application that is
> expecting plib-1.2.x (and doesn't remember to call ulInit() for
> instance) suddenly is compiled against plib-1.3.x.

Well, apart from anything else, a PLIB 1.2 application is going to
fail to link against 1.3.1 (or 1.4 more importantly) because SSG
needs UL and a 1.2 application won't be linking to libplibul.a

>  My fear is that 6
> months down the line when plib-1.3.x transitions to the stable tree,
> I'll have completely forgotten this message and will end up wasting a
> lot of time.  :-)

Right now, ulInit() is an empty function - but I can certainly put some
'traps' into the code to check that it was called before any future
hypothetical function that might need it.
 
> Is there a good function in libplibul.a that we can test for?

  ulInit()

   :-P

> Autoconf has the AC_CHECK_LIB( lib, function) macro that will test for
> a library and add it to the link line if it exists.

Right - and I'm putting that into all my application's configure.in's
as we speak.
 
You'll also need:

#if WE_DETECTED_A_VALID_ulInit_IN_THE_CONFIGURE_SCRIPT

  ulInit () ;

#endif

...uck!  Messy!

-- 
Steve Baker   HomeEmail: <sjb...@ai...>
              WorkEmail: <sj...@li...>
              HomePage : http://web2.airmail.net/sjbaker1
              Projects : http://plib.sourceforge.net
                         http://tuxaqfh.sourceforge.net
                         http://tuxkart.sourceforge.net
                         http://prettypoly.sourceforge.net