On Jun 21, 2018, at 16:46, Langer, Stephen A. (Fed) wrote:
> Hi--
>
> I'm making some progress in writing a Portfile for my project, but I'm stuck
> on one point. The project's build script uses python distutils (which I'd be
> happy to get rid of but that's not likely to happen soon).
On Jun 21, 2018, at 09:20, Michael Dickens wrote:
> See < https://trac.macports.org/ticket/56294 >.
>
> Boost 1.67.0 has significant changes in the way it handles time computations
> that are not ABI or API backward compatible with any prior Boost.
>
> I think all of the ports I maintain are
Hi--
I'm making some progress in writing a Portfile for my project, but I'm stuck on
one point. The project's build script uses python distutils (which I'd be
happy to get rid of but that's not likely to happen soon). The build
commands, outside of MacPorts, are
python setup.py build --3D
Don’t you just love ‘standard’ libraries that break backward compatibility?
Ah the joys of FOSS …
Maybe I should have just stayed with the C++ STL (oh wait … that’s changing
too).
> On Jun 21, 2018, at 10:20 AM, Michael Dickens wrote:
>
> See < https://trac.macports.org/ticket/56294 >.
>
See < https://trac.macports.org/ticket/56294 >.
Boost 1.67.0 has significant changes in the way it handles time computations
that are not ABI or API backward compatible with any prior Boost.
I think all of the ports I maintain are multi-Boost compatible, and I've seen
updates to others I don't
Any hope of seeing boost 1.67?
If not and I set it up myself will maintainer give me a hand getting it ready
for ‘official’ port?
