Re: [simspark-devel] Timer Test Report

[Oliver O. <Oli...@ne...>]

Hi,

On 01/05/2007, at 8:02 PM, Joschka Boedecker wrote:

> * For submitting the code to the CVS, we need a test to check for  
> the boost_thread-mt library. In some distributions, we need to use  
> "-lboost_thread-mt", in others "-lboost_thread-gcc-mt" for linking.
> @Oliver: do you think you could do the Makefile magic for that? :-)

Finally I've looked into it. The configure script now checks for this  
lib (as boost_thread, boost_thread-mt, and boost_thread-gcc-mt). It's  
somehow interesting that just the boost guys can't come up with one  
standard way of calling the library.

The check creates a Makefile (Meta)variable @BOOST_THREADS_LIB@. If  
you put it in a Makefile.am somewhere, it will be replaced by the  
name of the boost thread library that was found (first) when the  
Makefile gets created.
I haven't done this, because I haven't checked where you want to use  
it. If you need it in, say oxygen, do something like this to the  
corresponding Makefile.am:

change:
liboxygen_debug_la_LIBADD = -lode ${spades_libs}
to
liboxygen_debug_la_LIBADD = -lode ${spades_libs} -l@BOOST_THREADS_LIB@

(you have to do that 2x in the Makefile.am, one time for the debug  
version of the lib, and one time for the normal version).

If you cvs up now, you need to booststrap the configure file again.  
If there are problems (or more different versions of the thread lib),  
let me know.
I have tested the script on one linux machine (@uni-koblenz.de), but  
I haven't checked what happens if there's no boost thread library.  
What should the check do in this case? Stop configuring?

cheers
Oliver

-- 
Oliver Obst          ES208   form follows function (Louis Sullivan).
Fon: +61 2 492 16175                          http://oliver.obst.eu/
Uni Newcastle  School of Electrical Engineering and Computer Science