Thanks, I only looked in the repo. On Mon, Jan 18, 2016 at 11:17 AM, Pieter Hintjens <p...@imatix.com> wrote:
> Ah, I missed your patches. Merged it now. > > The release process for tarballs is documented here as it has for a > while: http://zeromq.org/docs:distributions > > For testing on Windows, I believe there's an appveyor CI running. > Though probably not testing the tweetnacl integration. > > > On Mon, Jan 18, 2016 at 11:10 AM, MinRK <benjami...@gmail.com> wrote: > > I added it to Makefile.am upstream, and opened a PR backporting that and > the > > Windows support to 4.1. But I wasn't able to verify that it actually > fixes > > the problem, since the release process appears to be undocumented. > > > > -MinRK > > > > On Mon, Jan 18, 2016 at 11:03 AM, Pieter Hintjens <p...@imatix.com> wrote: > >> > >> Not packaging tweetnacl was an oversight; someone added it to the > >> project and did not update Makefile.am. I will make this change. I > >> think it should also go into src/foreign rather than into the root > >> directory. > >> > >> On Mon, Jan 18, 2016 at 10:52 AM, MinRK <benjami...@gmail.com> wrote: > >> > I noticed that tweetnacl isn't included in the releases. Is this > >> > intentional? > >> > > >> > How are the tarballs made? I started trying to fix this, but didn't > find > >> > any > >> > documentation for how zeromq is released, and `make dist` seems to > fail > >> > due > >> > to missing Makefile sources in `build/cmake`. > >> > > >> > -MinRK > >> > > >> > On Wed, Jan 13, 2016 at 12:15 PM, Sergei Nikulov > >> > <sergey.niku...@gmail.com> > >> > wrote: > >> >> > >> >> 2016-01-13 13:34 GMT+03:00 James Chapman <ja...@linux-101.org>: > >> >> > Hi Pieter > >> >> > > >> >> > I've just tried to build 4.1.4 on Windows using VS2015. The build > >> >> > fails with the following compilation error: > >> >> > > >> >> > tcp_address.cpp(440): error C3861: 'if_nametoindex': identifier not > >> >> > found > >> >> > > >> >> > I should also add that the VS projects on 4.1 branch do not build > >> >> > without a lot of tweaking. I've taken to ignoring the packaged > >> >> > solution files and just using my own. > >> >> > > >> >> > James > >> >> > > >> >> > > >> >> > >> >> It seems that it was already been fixed on master 4.1 branch. > >> >> And it was bumped support from XP to Vista in upcoming 4.1.5 because > >> >> of this change 849e5b07d982e7c0917a13d9ff22d447817dd7fe (support for > >> >> IPv6 link local addresses). > >> >> > >> >> -- > >> >> Best Regards, > >> >> Sergei Nikulov > >> >> _______________________________________________ > >> >> zeromq-dev mailing list > >> >> zeromq-dev@lists.zeromq.org > >> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >> > > >> > > >> > > >> > _______________________________________________ > >> > zeromq-dev mailing list > >> > zeromq-dev@lists.zeromq.org > >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >> > > >> _______________________________________________ > >> zeromq-dev mailing list > >> zeromq-dev@lists.zeromq.org > >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > > > > > _______________________________________________ > > zeromq-dev mailing list > > zeromq-dev@lists.zeromq.org > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
