[
https://issues.apache.org/jira/browse/DISPATCH-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884813#comment-16884813
]
ASF GitHub Bot commented on DISPATCH-1282:
------------------------------------------
RoddieKieley commented on issue #459: DISPATCH-1282 - Support for building on
macOS
URL: https://github.com/apache/qpid-dispatch/pull/459#issuecomment-511258297
@jdanekrh I've been looking closely at the unittest2 issues I've been
having. It turns out that there are differences in behaviour and immediate
availability of unittest2 when installed via python -m easy_install, pip
install, or port install py-unittest2.
Of the three only the first works here as per the travis setup that installs
the egg to the main system /Library/Python/2.7 path. While this is probably
only really a pathing issue, it would be nice if this were less fragile.
Once the tests run I see that there are indeed issues from a default cmake
configuration as well as a segfault during the unit tests. More investigation
required.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Support for building on macOS
> -----------------------------
>
> Key: DISPATCH-1282
> URL: https://issues.apache.org/jira/browse/DISPATCH-1282
> Project: Qpid Dispatch
> Issue Type: New Feature
> Affects Versions: 1.5.0
> Reporter: Jiri Daněk
> Priority: Major
> Labels: macOS
>
> Currently, Dispatch compilation fails on "rt" library being unavailable.
> All Dispatch dependencies (Qpid Proton, libwebsockets, ...) can be built on
> macOS.
> I am attaching a patch which allows to compile dispatch on OSX and run it.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
