I've noticed that the mqueue unit tests all fail since at least boost
1.46.1. Some change in the boost serialization archive API is causing
std::vector<T> no longer being serialized with our archiver.
Did anyone notice / fix this ?
Peter
Orocos Real-Time ToolkitSmarter realtime. Safer threads
|
|
Mqueue transport no longer working ? (boost issue)
I've noticed that the mqueue unit tests all fail since at least boost Did anyone notice / fix this ? Peter |
Mqueue transport no longer working ? (boost issue)
On 05/08/2012 02:17 PM, Peter Soetens wrote:
> I've noticed that the mqueue unit tests all fail since at least boost
> 1.46.1. Some change in the boost serialization archive API is causing
> std::vector<T> no longer being serialized with our archiver.
>
> Did anyone notice / fix this ?
Not on my side since orogen/typegen does not use the specialized
archiver (and works fine with boost 1.48)
Mqueue transport no longer working ? (boost issue)
On Tue, May 8, 2012 at 3:20 PM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> On 05/08/2012 02:17 PM, Peter Soetens wrote:
>>
>> I've noticed that the mqueue unit tests all fail since at least boost
>> 1.46.1. Some change in the boost serialization archive API is causing
>> std::vector<T> no longer being serialized with our archiver.
>>
>> Did anyone notice / fix this ?
>
> Not on my side since orogen/typegen does not use the specialized archiver
> (and works fine with boost 1.48)
Oh that's right. I fixed the issue anyway on toolchain-2.5. There was
also another bug that std::vectors were serialized along the 'slow'
path, I had observed this once some time ago, but couldn't point to
the problem back then.
Anyway, 'old style' mqueue users should upgrade their 2.5 branch or
cherry-pick these patches.
Peter