Actions
Feature #2085
closedBoost Signals updated to Boost Signals2
Description
It has come to my attention while compiling against boost 1.54 that boost signals, currently used by WT, is being depreciated and phased out, and that the new signals2 is the way to go.
Is there any plans for changing Wt to rely on signals2 instead of signals? It may be possible to support both with some interesting header magic, if this is desired, though I don't see any reason why not to bump boost's required level up to 1.40
http://www.boost.org/doc/libs/1_54_0/doc/html/signals2/api_changes.html#signals2.porting
Updated by Wim Dumon over 11 years ago
- Status changed from New to InProgress
- Assignee set to Wim Dumon
In recent git versions, there is already a switch in WConfig.h.in that lets you select between signals and signals2. This will become a cmake configuration option.
BR,
Wim.
Updated by Koen Deforche about 11 years ago
- Status changed from InProgress to Resolved
- Target version set to 3.3.1
Updated by Koen Deforche about 11 years ago
- Status changed from Resolved to Closed
Actions