Yet more fun from boost's API changes ...
Tested on Mac OS X Snow Leopard with boost v1.46.1, and Ubuntu 10.04 with boost v1.40
S
Attachment | Size |
---|---|
0001-Patches-for-boost-filesystem-v3.patch | 2.8 KB |
Orocos Real-Time ToolkitSmarter realtime. Safer threads
|
|
PATCH: utilmm for boost::filesystem v3
Yet more fun from boost's API changes ... Tested on Mac OS X Snow Leopard with boost v1.46.1, and Ubuntu 10.04 with boost v1.40
|
PATCH: utilmm for boost::filesystem v3
On 08/28/2011 10:11 PM, S Roderick wrote:
> Yet more fun from boost's API changes ...
>
> Tested on Mac OS X Snow Leopard with boost v1.46.1, and Ubuntu 10.04 with boost v1.40
Could you try the master branch ? I had a patch on rock's clone that was
supposed to fix compilation on MacOS
Sylvain
PATCH: utilmm for boost::filesystem v3
On Aug 29, 2011, at 08:31 , Sylvain Joyeux wrote:
> On 08/28/2011 10:11 PM, S Roderick wrote:
>> Yet more fun from boost's API changes ...
>>
>> Tested on Mac OS X Snow Leopard with boost v1.46.1, and Ubuntu 10.04 with boost v1.40
> Could you try the master branch ? I had a patch on rock's clone that was supposed to fix compilation on MacOS
Will do. I just noticed some of the commits you're referring to ... so master is the most advanced, or most stable, or ???, for Rock?
S
PATCH: utilmm for boost::filesystem v3
On 08/29/2011 02:36 PM, Stephen Roderick wrote:
>>> Yet more fun from boost's API changes ...
>>>
>>> Tested on Mac OS X Snow Leopard with boost v1.46.1, and Ubuntu 10.04 with boost v1.40
>> Could you try the master branch ? I had a patch on rock's clone that was supposed to fix compilation on MacOS
> Will do. I just noticed some of the commits you're referring to ... so master is the most advanced, or most stable, or ???, for Rock?
Not sure I understand the question
The issue there was that rock users are using rock's clone for utilmm.
Some of these people fixed compilation on MacOSX (since we have macos
users) and pushed it there.
And I did not update the orocos toolchain repository from rock's. Hence
the lingering problem on orocos toolchain
I usually regularly check and push to the orocos toolchain. Just
overlooked those.
Sylvain