[boost] [log] custom architecture and address-model

Hi, it seems that Boost.Log defines, and checks, it's own log-address-model and log-architecture and log-instruction-set properties. Naturally, if I'm trying to make regular address-model and architecture properties always set, these are getting in the way. Do we really need per-library properties? If a user wants to build Boost.Log with a particular architecture, I would think he can do: ./b2 --with-log <whatever> If so, is everybody fine if I eliminate these custom features eventually? -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com