From: brass goowy (brass_at_[hidden])
Date: 2008-04-09 16:40:26
Vicente Botet writes:
>> Configuring the above with a compiled library like boost serialization
>> is an interesting task as well, that I definitely think should be
>> addressed. could be that the flexibility decreases some in such a
>> scenario, or it could be configued in site-config.jam or whatever.
>Once the serialization library provide traces or log, if you want to use the
>serialization library with logs you should add a define at compile time
>e.g. -DBOOST_SERIALIZATION_LOG_ENABLE and link with the serialization logged
>variant e.g. -lboost_lserialization.
This is a good example of the need for compilers that output the code they
generate based on templates. If they did that, the library writer could
have an online service that spits out the final deliverable rather than
users having to maintain different versions of a library. It is a slow
and error prone process to rebuild a library/application as suggested here.
Alternatively, service providers would have logging versions of their code available
for users in the field, in effect eliminating the long and unproductive process of
a rebuild. Because the code is built by the service provider rather than less
experienced users, configuration confusion is mitigated. As the needs here are
pressing, we hope the problems with the status quo will be addressed sooner
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk