On Feb 1, 2019, at 20:09, Zero King wrote:
> On Fri, Feb 01, 2019 at 06:11:16PM -0600, Ryan Schmidt wrote:
>
>> On Feb 1, 2019, at 15:30, Michael Dickens wrote:
>>
>>> OK yes we -offer- multiple versions, but only one version can be installed
>>> at a time right now.
>>
>> No, if you
On Fri, Feb 01, 2019 at 06:11:16PM -0600, Ryan Schmidt wrote:
On Feb 1, 2019, at 15:30, Michael Dickens wrote:
OK yes we -offer- multiple versions, but only one version can be installed at a
time right now.
No, if you install boost without the no_single variant, you will get both the
On Feb 1, 2019, at 15:30, Michael Dickens wrote:
> OK yes we -offer- multiple versions, but only one version can be installed at
> a time right now.
No, if you install boost without the no_single variant, you will get both the
single-threaded and the multithreaded versions. If you install
OK yes we -offer- multiple versions, but only one version can be installed at a
time right now. And, when using "--layout==tagged" I'd bet that the resulting
ABI name changes for each installed variant, which means that all ports that
depend on Boost would have to be rebuilt when switching
On Jan 17, 2019, at 14:17, Michael Dickens wrote:
> I've been trying to get Boost 1.69.0 working, without much luck yet because
> the default installed library names as installed by MacPorts are changed from
> "libboost_COMP-mt.dylib" to "libboost_COMP-mt-ARCH.dylib", where "COMP" is
> the
Hi Michael,
> On Jan 17, 2019, at 1:17 PM, Michael Dickens wrote:
>
> I've been trying to get Boost 1.69.0 working, without much luck yet because
> the default installed library names as installed by MacPorts are changed from
> "libboost_COMP-mt.dylib" to "libboost_COMP-mt-ARCH.dylib", where
I've been trying to get Boost 1.69.0 working, without much luck yet because the
default installed library names as installed by MacPorts are changed from
"libboost_COMP-mt.dylib" to "libboost_COMP-mt-ARCH.dylib", where "COMP" is the
component name (e.g., "system", "thread") and "ARCH" is the
