Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ZMQ portability #1

Closed
zmughal opened this issue Jun 24, 2014 · 6 comments
Closed

ZMQ portability #1

zmughal opened this issue Jun 24, 2014 · 6 comments
Labels
bug category:build in progress
Milestone
Devel::IPerl v0.009

Comments

@zmughal
Copy link
Member

zmughal commented Jun 24, 2014

@zmughal zmughal added the bug label Jun 28, 2014
@zmughal zmughal mentioned this issue May 12, 2015
Closed
@zmughal
Copy link
Member Author

zmughal commented May 23, 2015

Next step: perhaps create an Alien::Base-based Alien::LibZMQ3, Alien::ZMQ4.

@zmughal
Copy link
Member Author

zmughal commented May 26, 2015

TODO: test https://github.com/zmughal/p5-Alien-ZMQ4 on Windows

@zmughal zmughal modified the milestone: Devel::IPerl v0.007 Aug 2, 2015
@asimonov
Copy link

asimonov commented Sep 7, 2016

Zaki, i am trying to install iperl on windows and need to check what configuration you used. Cannot find your email anywhere. What is the best way to contact?

@zmughal
Copy link
Member Author

zmughal commented Sep 7, 2016

Hi, you can reach me at zmughal@cpan.org.

Just to answer your question, I currently do not have a Windows build working. I am planning to get to this at some point, but have been really busy lately. I will try to set aside time for this in the coming weeks and will let you know my progress.

In the meantime, I would recommend using Docker or a virtual machine with Linux to install IPerl. Someone has made a Dockerfile here.

Another approach is to install JupyterHub on a Linux machine. This will act as a server that will let you create Jupyter/IPerl notebooks from any machine that can reach it.

I hope that helps!

zmughal added a commit that referenced this issue Dec 16, 2017
@zmughal
Use Net::Async::ZMQ instead of IO::Async::Handle
4ca54ea 
This moves the specific handling of the ZMQ file descriptors into
Net::Async::ZMQ where it can handle things in a more cross-platform
manner.

This is related to
<#1>,
<#41>.
zmughal added a commit that referenced this issue Dec 17, 2017
@zmughal
Use Net::Async::ZMQ instead of IO::Async::Handle
5384fe9 
This moves the specific handling of the ZMQ file descriptors into
Net::Async::ZMQ where it can handle things in a more cross-platform
manner.

This is related to
<#1>,
<#41>.
zmughal added a commit that referenced this issue Dec 17, 2017
@zmughal
Use Net::Async::ZMQ instead of IO::Async::Handle
c8e9a4c 
This moves the specific handling of the ZMQ file descriptors into
Net::Async::ZMQ where it can handle things in a more cross-platform
manner.

This is related to
<#1>,
<#41>.
@zmughal zmughal mentioned this issue Dec 17, 2017
Merged
@zmughal
Copy link
Member Author

zmughal commented Dec 17, 2017

Fixed by #82.

@zmughal zmughal closed this as completed Dec 17, 2017
@zmughal
Copy link
Member Author

zmughal commented Dec 17, 2017

Note:

The results of getting this issue closed:

Distributions created

PRs opened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug category:build in progress
Projects
None yet
Milestone
Devel::IPerl v0.009
Development

No branches or pull requests
2 participants
@zmughal @asimonov