It does that using conditional sections at compile time (#ifdef). The code
generation just makes it easier to maintain.
On Jun 25, 2012 10:55 AM, "Brian Knox" wrote:
> Aha! Is that how it handles building against multiple libzmq versions?
>
> Brian
>
> On Sun, Jun 24, 2012 at 8:22 PM, Pieter Hin
Aha! Is that how it handles building against multiple libzmq versions?
Brian
On Sun, Jun 24, 2012 at 8:22 PM, Pieter Hintjens wrote:
> On Mon, Jun 25, 2012 at 4:56 AM, Brian Knox wrote:
>
> > Ah, thanks for the info, I missed that.
> > https://github.com/zeromq/libzmq/pull/383
> > fixed in my
On Mon, Jun 25, 2012 at 4:56 AM, Brian Knox wrote:
> Ah, thanks for the info, I missed that.
> https://github.com/zeromq/libzmq/pull/383
> fixed in my fork and sent a pull request.
Thanks for this. In fact the zsockopt.c/.h files are produced
mechanically from the sockopts.xml spec, using a litt
Ah, thanks for the info, I missed that.
https://github.com/zeromq/libzmq/pull/383
fixed in my fork and sent a pull request.
Brian
On Sun, Jun 24, 2012 at 3:22 PM, Ivan Pechorin wrote:
>
>
> 2012/6/24 Brian Knox
>
>> zsockopt.c: In function 'zsocket_set_fail_unroutable':
>> zsockopt.c:970:38:
2012/6/24 Brian Knox
> zsockopt.c: In function 'zsocket_set_fail_unroutable':
> zsockopt.c:970:38: error: 'ZMQ_FAIL_UNROUTABLE' undeclared (first use in
> this function)
> zsockopt.c:970:38: note: each undeclared identifier is reported only once
> for each function it appears in
>
this option wa
Hello zmq'ers. I just wanted to pass along that czmq (from git head) is
currently not building against libzmq (from git head today as well).
Here's the break:
/bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H
-I. -I../include -pedantic -Werror -Wall -Wno-unused -D_GNU_
