Re: [jamboost] Writing tests for typeid wrapper

From: Jody Hagins (jody-boost-011304_at_[hidden])
Date: 2005-02-22 09:48:26

On Mon, 21 Feb 2005 23:45:43 -0600
Rene Rivera <grafik.list_at_[hidden]> wrote:

> One caveat to be aware of is that on certain platforms, i.e. Windows, 
> some targets (DLLs) generate more than one file and *all* files are 
> passed to the test. Which for the example above means it outputs 
> something akin to:
> 
> ====== BEGIN OUTPUT ======
> arg #0 = 
> 'C:\Boost\test\bin\boost\tools\build\v1\example\target_test_arg\simpl
> e.test\cw-8_3\debug\threading-multi\simple.exe' arg #1 = 
> 'C:\Boost\test\bin\boost\tools\build\v1\example\target_test_arg\simpl
> e.dll\cw-8_3\debug\threading-multi\simple.dll' arg #2 = 
> 'C:\Boost\test\bin\boost\tools\build\v1\example\target_test_arg\simpl
> e.dll\cw-8_3\debug\threading-multi\simple.lib' arg #3 = 
> 'C:\Boost\test\bin\boost\tools\build\v1\example\lib_use\libsimple.lib
> \cw-8_3\debug\threading-multi\libsimple.lib' arg #4 = 
> 'C:\CVSROOTs\Boost\boost\tools\build\v1\example\target_test_arg\simpl
> e_lib.cpp'
> 
> EXIT STATUS: 1
> ====== END OUTPUT ======
> 
> So your test program will have to sort out which of the two files is
> the shared library.

Thanks! I will check out the CVS HEAD and try this out (I assume that
is where the change resides).

Is there a boost way of knowing which path I want (e.g., based on the
platform)? If not, then I may be left to "trying" each file until one
successfully loads.