Re: [Boost-users] [serialization] boost::serialization adds huge amounts of exports to resultant Windows PE file

Subject: Re: [Boost-users] [serialization] boost::serialization adds huge amounts of exports to resultant Windows PE file
From: Robert Ramey (ramey_at_[hidden])
Date: 2010-10-02 13:15:58

Chris Yuen wrote:
> Rober Ramey wrote:
>> If you want to be really helpful you could do the following:
>
>> On your own machine run library_test.sh for the serialization library
>> for each of the three compilers in release mode and send me the
>> results. For those compilers which pass, we'll tweak the
>> force_include file accomodate this new information.
>
> I would love to help, but any pointers on how to run it? I tried
> library_test.bat and library_test.sh and failed:
>
>    > cd
>    D:\Lib\boost\libs\serialization\test
>
>    > ..\..\..\tools\regression\src\library_test.bat
>    'process_jam_log' is not recognized as an internal or external
>    command, operable program or batch file.
>    'library_status' is not recognized as an internal or external
>    command, operable program or batch file.
>
>
>    $ uname
>    CYGWIN_NT-6.1-WOW64
>
>    $ pwd
>    /cygdrive/d/Lib/boost/libs/serialization/test
>
>    $ ../../../tools/regression/src/library_test.sh toolset=msvc
>    ../../../tools/regression/src/library_test.sh: line 17:
> process_jam_log: command not found
>    ../../../tools/regression/src/library_test.sh: line 18:
> library_status: command not found
>
> Best regards,
> Chris Yuen

The two programs process_jam_log and library_status have to be built and 
moved to
some directory in the path.  These can be built with bjam by moving
to tools/regression/src/process_jam_log and running bjam - similarly
for library_status.

Robert Ramey