|
|
Boost Interest : |
Subject: [Boost-cmake] Modularization, Core and Circular Dependencies
From: Michael Jackson (mike.jackson_at_[hidden])
Date: 2008-11-03 15:32:23
On Oct 31, 2008, at 2:16 PM, Doug Gregor wrote:
> On Fri, Oct 31, 2008 at 12:07 PM, Michael Jackson
> <mike.jackson_at_[hidden]> wrote:
>>
>> On Oct 30, 2008, at 11:14 PM, Doug Gregor wrote:
>>
>>> On Thu, Oct 30, 2008 at 2:26 PM, Michael Jackson
>>> <mike.jackson_at_[hidden]> wrote:
>>>>
>>>> What I am not sure of is what to do with the remaining headers in
>>>> the
>>>> "boost" directory. Are those going to be the "core" of Boost or ?
>>>
>>> Yeah, that's how I would do it.
>>
>> So are talking about modularizing what is left into "libs/core"
>> then? I just
>> want to be really clear and certain before I make that move.
>
> Sorry, I was very unclear. I would like the remaining libs (mpl,
> type_traits, config, and whatever else is in that tangle)
> unmodularized for now. There *are* circular dependencies at the
> library level and they aren't trivial to untangle. It's better for the
> CMake effort to leave those in the non-modularized core and let the
> library authors sort out the dependencies later.
>
> - Doug
Ok as I am working through the "testing" part of the CMake build
system it is becoming clear the circular dependencies. Do you want me
to "un-modularize" those for now? ie, turn OFF the modularization
those libraries?
Here are the candidates as I see it right now (This could change 5
minutes from now .. )
mpl
detail
utility
exception
integer
iterator
function
concept_check
concept
preprocessor
config
static_assert
type_traits
_________________________________________________________
Mike Jackson mike.jackson_at_[hidden]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio