[Libwebsockets] 回复: 答复: A question about libwebsockets dns resolve

o_O凌雲 550470999 at qq.com
Sun May 10 18:54:29 CEST 2020


Hi, 
    we want to limit wait time for each when dns resolve connect because 20s is too long. And I set lws_timeout. and time limit tabke effect. but this is something wrong that tsi fds count is 1. it is normall is zero when trying end. please help to check my code whether there is something wrong. thanks.



------------------ 原始邮件 ------------------
发件人: "andy"<andy at warmcat.com>;
发送时间: 2020年4月29日(星期三) 晚上6:37
收件人: "huangkaicheng"<huangkaicheng at huawei.com>;"libwebsockets at ml.libwebsockets.org"<libwebsockets at ml.libwebsockets.org>;
抄送: "Zhangdong (Welber)"<welber.zhang at huawei.com>;"Chenyake"<chenyake at huawei.com>;
主题: Re: [Libwebsockets] 答复: A question about libwebsockets dns resolve and newest tag





On 4/29/20 9:52 AM, huangkaicheng wrote:
> Hi,
> 
>>From here 5.5.5.5 routes to Telefonica and then goes in a blackhole.
> 
>>If lws (or anything else) tries to connect there, it just sits there
> 
>>until the connection attempt times out.
> 
>      5_1.rtc_test.huawei.com is our internal domain for test.
> 
>      Why not try next instead of attempting time out ? Is there some way 
> to control to try next?. It is strategy or a bug?

If the single connection attempt wants to sit there 30s (the OS chooses 
that number) and our overall connection timeout is 20s, you get one 
chance and this behaviour.  If it waited less long, it would continue to 
do the iterative retry through the dns results behaviour.

If you want to put a limit on the connection attempt, FWIW I looked at 
this using setsockopt() and it doesn't work on Linux to try to reduce 
the connection wait by setting the read wait limit... googling around 
this was supposed to work, but it doesn't.

If you want to implement this, a patch is welcome... I guess it'll work 
to set a timeout on the wsi but notice during the close flow that it was 
in LRS_WAITING_CONNECT and attempt to rejoin the retry flow that happens 
if the connect() returns an explicit error.

> And we need a newest tag for tracing to the source;.Can you help us to 

The situation with stable tags isn't really pleasing anyone, I think 
they're redundant, since the commit has the same hash tagged or not you 
can just use that unambiguously, but at any given time people who 
believe the ordinal in tags has some magic meaning are waiting for 
vx.y.(z + 1) and missing out on patches already on the -stable branch. 
I looked at openembedded the other day and while their lws recipe is 
pretty up-to-date, it's on 4.0.1 and the patch updating it was only a 
couple of days old at the time I looked.  But as of a week ago, there 
are 25 backported patches ahead of that on v4.0-stable openembedded 
users are not getting the benefit of yet, presumably because they didn't 
see v4.0.2+++ tagged out.

The problem is there isn't any real logic for when to make a new tag, 
for any particular patch if it fixes what you care about you would 
naturally think that should be cause for a tag.  It leads to tagging 
every commit - this is the approach for kernel stable tree - which is 
more work for me just to stop the tag-belivers using 
broken-but-already-fixed code.

I think I probably have to give up and move to tagging every stable 
commit to stop these kind of requests coming and get people to use the 
latest stuff.  It's messy because CMakeLists.txt wants its version 
updating accordingly each time.

-Andy

> release new version 4.0.2 in stable 4.0 branch. Thanks .
> 
> -----邮件原件-----
> 发件人: Andy Green [mailto:andy at warmcat.com]
> 发送时间: 2020年4月28日20:58
> 收件人: huangkaicheng <huangkaicheng at huawei.com>; 
> libwebsockets at ml.libwebsockets.org
> 抄送: Chenyake <chenyake at huawei.com>; Zhangdong (Welber) 
> <welber.zhang at huawei.com>
> 主题: Re: 答复: A question about libwebsockets dns resolve.
> 
> On 4/28/20 1:32 PM, huangkaicheng wrote:
> 
>> Hi,
> 
>>      I made a test about dns resolver of libwebsockets for ws client.
> 
>>      
> 
>>      Server address is domain like 5_1.rtc_test.huawei.com
> 
> This is NXDOMAIN from the public internet.
> 
>>      Domain has multi address as follows.
> 
>> 5.5.5.5
> 
>> 1.1.1.1
> 
>> 2.2.2.2
> 
>> 100.94.16.193
> 
>> 4.4.4.4
> 
>>      I found websockets clients resolve 5.5.5.5(invalid address). so it connect failed. But it did not try to next address. In fact 100.94.16.193 is valid address. Please help to see why it did not try next address.  Is there something wrong of uses about libwebsockets? Please see more 
> in attachments. thanks.
> 
>  From here 5.5.5.5 routes to Telefonica and then goes in a blackhole.
> 
> If lws (or anything else) tries to connect there, it just sits there
> 
> until the connection attempt times out.
> 
> The tcp connection was still trying to wait... the lws connection
> 
> timeout fired first.
> 
> [2020/04/28 13:44:52:4921] I: lws_client_connect_2_dnsreq: 0xf34440:
> 
> lookup 5.5.5.5:443
> 
> [2020/04/28 13:44:52:4921] I: lws_client_connect_3_connect: 5.5.5.5 ipv4
> 
> 5.5.5.5
> 
> [2020/04/28 13:44:52:4923] I: lws_state_transition_steps:
> 
> CONTEXT_CREATED -> OPERATIONAL
> 
> [2020/04/28 13:45:22:4923] I: wsi 0xf34440: TIMEDOUT WAITING on 2 (did
> 
> hdr 0, ah 0xf70b90, wl 0)
> 
> [2020/04/28 13:45:22:4923] I: __lws_close_free_wsi: 0xf34440: caller:
> 
> timeout
> 
> [2020/04/28 13:45:22:4923] N: __lws_close_free_wsi: closing in
> 
> unestablished state 0x202
> 
> [2020/04/28 13:45:22:4924] E: CLIENT_CONNECTION_ERROR: closed before
> 
> established
> 
> I added several test subdomains to warmcat.com DNS when I originally did
> 
> this, these are publicly resolveable.  Eg,
> 
> onevalid.bogus          IN      A       127.0.0.1
> 
>                           IN      A       127.0.0.2
> 
>                           IN      A       127.0.0.3
> 
>                           IN      A       46.105.127.147
> 
> These tests are not that repeatable because the client DNS resolve
> 
> rotates through the result list each time to provide round-robin between
> 
> the servers.  But, eg
> 
> $./bin/lws-minimal-http-client --server onevalid.bogus.warmcat.com -d 1039
> 
> ...
> 
> [2020/04/28 13:50:21:2046] I: lws_adns_parse_udp: create cache entry for
> 
> onevalid.bogus.warmcat.com, 283
> 
> [2020/04/28 13:50:21:2046] I: lws_async_dns_store: 0:
> 
> onevalid.bogus.warmcat.com: 127.0.0.2
> 
> [2020/04/28 13:50:21:2046] I: lws_async_dns_store: 1:
> 
> onevalid.bogus.warmcat.com: 127.0.0.1
> 
> [2020/04/28 13:50:21:2046] I: lws_async_dns_store: 2:
> 
> onevalid.bogus.warmcat.com: 46.105.127.147
> 
> [2020/04/28 13:50:21:2046] I: lws_async_dns_store: 3:
> 
> onevalid.bogus.warmcat.com: 127.0.0.3
> 
> [2020/04/28 13:50:21:2046] I: lws_client_connect_3_connect:
> 
> onevalid.bogus.warmcat.com ipv4 127.0.0.2
> 
> [2020/04/28 13:50:21:2049] I: lws_client_connect_3_connect: (null) ipv4
> 
> 127.0.0.1
> 
> [2020/04/28 13:50:21:2050] I: lws_client_connect_3_connect: (null) ipv4
> 
> 46.105.127.147
> 
> [2020/04/28 13:50:21:2210] I: lws_client_connect_3_connect: getsockopt
> 
> check: conn OK
> 
> [2020/04/28 13:50:21:2210] I: lws_client_connect_3_connect: Connection
> 
> started 0x875100
> 
> [2020/04/28 13:50:21:2210] I: lws_client_connect_4_established: wsi
> 
> 0x837440: h1 http client created own conn (raw 0) vh defaultm st 0x202
> 
> [2020/04/28 13:50:21:2210] I: h1 client conn using alpn list 'h2'
> 
> [2020/04/28 13:50:21:2421] E: SSL error: Hostname mismatch
> 
> (preverify_ok=0;err=62;depth=0)
> 
> [2020/04/28 13:50:21:2421] I: lws_client_socket_service: closing conn at
> 
> LWS_CONNMODE...SERVER_REPLY, wsi 0x8374
> 
> ...
> 
> So he tries 127.0.0.2, then 127.0.0.1, then 46.105.127.147 where he
> 
> connects.  The SSL fails because the cert hostname is not this test DNS
> 
> name we're using, but it's not the point.
> 
> If one of the results just sits there until the whole connection timeout
> 
> occurs, the retry strategy doesn't cover that.
> 
> -Andy
> 
>> -----邮件原件-----
> 
>> 发件人: andy at warmcat.com <mailto:andy at warmcat.com> [mailto:andy at warmcat.com]
> 
>> 发送时间: 2020年4月28日16:20
> 
>> 收件人: huangkaicheng <huangkaicheng at huawei.com 
> <mailto:huangkaicheng at huawei.com>>; libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>> 抄送: Chenyake <chenyake at huawei.com <mailto:chenyake at huawei.com>>; 
> Zhangdong (Welber) <welber.zhang at huawei.com 
> <mailto:welber.zhang at huawei.com>>
> 
>> 主题: Re: A question about libwebsockets dns resolve and about next 
> release version in 4.0-stable
> 
>> 
> 
>> 
> 
>> 
> 
>> On April 28, 2020 8:11:52 AM UTC, huangkaicheng <huangkaicheng at huawei.com <mailto:huangkaicheng at huawei.com>> wrote:
> 
>>> Hi,
> 
>>>
> 
>>>
> 
>>>
> 
>>>> Yes on v4.0+ should iterate through all the resolved address trying to
> 
>>> connect with them until the connection succeeds or it runs out of
> 
>>> addresses, also including mixed ipv6 / v4 results if you have enabled
> 
>>> ipv6.
> 
>>>
> 
>>>> That's also the case if you use the optional built-in Async DNS
> 
>>> resolver.
> 
>>>
> 
>>>
> 
>>>
> 
>>> What you mean that only build in Async DNS resolver can support this
> 
>>> case?
> 
>> 
> 
>> No, 'that's also the case' means it's also true for async dns resolver.  Not that it is only true for async dns resolver.  The retry mechanism is the same either way.
> 
>> 
> 
>>> And we want to know when you plan to release next version base in
> 
>>> stable 4.0 branch like v4.0.2? thanks to help answer for me.
> 
>> 
> 
>> Dunno, just use v4.0-stable branch to get the latest backported stuff immediately.  It makes no difference if they are tagged out or not.
> 
>> 
> 
>> -Andy
> 
>> 
> 
>>> [cid:image001.jpg at 01D61D77.B80E7FC0]
> 
>>>
> 
>>> -----邮件原件-----
> 
>>>
> 
>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>> 发送时间: 2020年4月27日 21:10
> 
>>>
> 
>>> 收件人: huangkaicheng <huangkaicheng at huawei.com 
> <mailto:huangkaicheng at huawei.com>>;
> 
>>> libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>> 抄送: Chenyake <chenyake at huawei.com <mailto:chenyake at huawei.com>>; 
> Zhangdong (Welber)
> 
>>> <welber.zhang at huawei.com <mailto:welber.zhang at huawei.com>>
> 
>>>
> 
>>> 主题: Re: 答复: A question about libwebsockets dns resolve and comile
> 
>>> warning in vs2015
> 
>>>
> 
>>>
> 
>>>
> 
>>>
> 
>>>
> 
>>>
> 
>>>
> 
>>> On 4/27/20 1:54 PM, huangkaicheng wrote:
> 
>>>
> 
>>>> Hi,
> 
>>>
> 
>>>>        I have found why libwebsockets has warning(C4819) .because file
> 
>>> "lws_config_private.h.in"  has Unicode character.  I has repaired. See
> 
>>> more in the attaments. Please put a patch to master or stable 4.0.
> 
>>>
> 
>>>
> 
>>>
> 
>>> The UTF-8 char is legal on most platforms, including Linux... it didn't
> 
>>> make any problem building on OSX or Windows 10 using... whatever
> 
>>> "codepage" or whatever it is for English on that.
> 
>>>
> 
>>>
> 
>>>
> 
>>> I guess this is a really caused by UTF16 munging, or some
> 
>>> Chinese-specific locale... anyway it's easy to fix it, it's pushed on
> 
>>> Master + v4.0-stable.  FWIW I worked on an IDE on a machine with
> 
>>> Japanese locale for a while, there were ways to tell the IDE about the
> 
>>> locale with which to process specific source files as a property of the
> 
>>> file.
> 
>>>
> 
>>>
> 
>>>
> 
>>>>        And I have another question about dns resolve of libwebsockets.
> 
>>>
> 
>>>>        If websockets server is domain like "libwebsocket.org". and If
> 
>>> libwebsockets.org has multi address like 112.125.156.85 and 45.53.95.4
> 
>>> . if websockets try to connect  112.125.156.85 failed, and  it will try
> 
>>> to connect next addr 45.53.95.4? Can it support for ws client? Thanks
> 
>>> for help to answer?
> 
>>>
> 
>>>
> 
>>>
> 
>>> Yes on v4.0+ should iterate through all the resolved address trying to
> 
>>> connect with them until the connection succeeds or it runs out of
> 
>>> addresses, also including mixed ipv6 / v4 results if you have enabled
> 
>>> ipv6.
> 
>>>
> 
>>>
> 
>>>
> 
>>> That's also the case if you use the optional built-in Async DNS
> 
>>> resolver.
> 
>>>
> 
>>>
> 
>>>
> 
>>> -Andy
> 
>>>
> 
>>>
> 
>>>
> 
>>>> -----邮件原件-----
> 
>>>
> 
>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>> 发送时间: 2020年4月23日13:44
> 
>>>
> 
>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com 
> <mailto:huangkaicheng at huawei.com>>;
> 
>>>
> 
>>>> libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>> 抄送: Chenyake <chenyake at huawei.com <mailto:chenyake at huawei.com>>; 
> Zhangdong (Welber)
> 
>>>
> 
>>>> <welber.zhang at huawei.com <mailto:welber.zhang at huawei.com>>
> 
>>>
> 
>>>> 主题: Re: 答复: A question about libwebsockets log and ios compiler
> 
>>> error.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>>
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> On 4/23/20 4:37 AM, huangkaicheng wrote:
> 
>>>
> 
>>>>> I found why mater can not build success .because cmakelist of master
> 
>>>
> 
>>>>> add “add_complile_option”, if any warning , it will build fail. And
> 
>>>
> 
>>>>> stable
> 
>>>
> 
>>>>> 4.0 will not.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> Before the last weeks I didn't use windows myself, but currently I am
> 
>>> using it to implement my own CI for lws, on my own hosted builers on
> 
>>> multiple platforms including windows, so I can replace Travis and
> 
>>> Appveyor.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> So windows has had an "upgrade" in lws, master builds without any
> 
>>> warnings now on VS 2019 for the options I test it with and I enabled
> 
>>> the equivalent of -Werror on it so in future, no warnings will be
> 
>>> allowed to creep back in.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> If your build of master with your tools and options on windows is
> 
>>> generating warnings, please paste them in an email and I'll clean them
> 
>>> (or provide a patch to clean them).
> 
>>>
> 
>>>>
> 
>>>
> 
>>>>> Can you put a patch to 4.0_stable branch about
> 
>>>
> 
>>>>>     -DLWS_LOGGING_BITFIELD_SET="(LLL_INFO | LLL_DEBUG)" ?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> It work well in master about LWS_LOGGING_BITFIELD_SET.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> Normally we can't add features to the stable branch, but because this
> 
>>> is a NOP unless you use it at build time, I added it.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>>> And last question about compile error in IOS about  “net/route.h”in
> 
>>>
> 
>>>>> 4.0_stable branch. I define macro  “LWS_PLAT_IOS”so that it can build
> 
>>>
> 
>>>>> success in IOS.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> I made so changes in stable_4.0 as follows. Can you help to put a
> 
>>>
> 
>>>>> patch about this to 4.0_stable branch ? thanks.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Unix-sockets.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> #if !defined(LWS_PLAT_IOS)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> #include <net/route.h>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> #endif
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> CMakeLists.txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws_config.h.in
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> #cmakedefine LWS_PLAT_IOS
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> if(IOS)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>        set(LWS_PLAT_IOS 1)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> endif()
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> Thanks, I pushed it on master and v4.0-stable.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> FYI it's not hard to generate patches if you use git, you can just
> 
>>>
> 
>>>> type
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> $ git diff > my.patch
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> to see what you changed since you last set the reset your tree from
> 
>>> git in patch format.  You can edit out any sections that don't matter.
> 
>>>
> 
>>>>
> 
>>>
> 
>>>> -Andy
> 
>>>
> 
>>>>
> 
>>>
> 
>>>>> -----邮件原件-----
> 
>>>
> 
>>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>>> 发送时间: 2020年4月22日21:33
> 
>>>
> 
>>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com 
> <mailto:huangkaicheng at huawei.com>>
> 
>>>
> 
>>>>> 抄送: Chenyake <chenyake at huawei.com <mailto:chenyake at huawei.com>>; 
> Zhangdong (Welber)
> 
>>>
> 
>>>>> <welber.zhang at huawei.com <mailto:welber.zhang at huawei.com>>
> 
>>>
> 
>>>>> 主题: Re: 答复: A question about libwebsockets log
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> On 4/22/20 2:28 PM, huangkaicheng wrote:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> HI,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>    I download the latest code in master,it seems that libwebsockets
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> compiled fail. And brach 4.0-stable can build success.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ./cmake/lws_config_private.h has not changed for a very long time,
> 
>>> it
> 
>>>
> 
>>>>> should be identical to the one in v4.0-stable.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> It's processed as part of the cmake action... maybe it's corrupted
> 
>>> by
> 
>>>
> 
>>>>> the chinese codepage I dunno.  Here's current master built perfectly
> 
>>>
> 
>>>>> well on wndows 10 + VS2019, I think there is no problem in lws about
> 
>>> it.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> NSSTATE_INIT
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> NSSTATE_STARTING_MIRROR
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> Starting REMOTE MIRROR FETCH
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> MIRROR in use, waiting (4)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> MIRROR Started
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> Remote->Local->Checked out
> 
>>>
> 
>>>>>> saib> Remote->Local->069e741d18514e50bf6f499234f99342562a4ed3
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> NSSTATE_BUILD
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> CLINK C:\Users\agreen\sai2\build>set SAI_INSTANCE_IDX=2
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> CLINK C:\Users\agreen\sai2\build>cd
> 
>>>
> 
>>>>> /Users/agreen\jobs\warmcat_com-windows-10.2\libwebsockets && mkdir
> 
>>>
> 
>>>>> build && cd build && cmake ..
> 
>>>
> 
>>>>> -DLWS_EXT_PTHREAD_INCLUDE_DIR="C:\Program Files
> 
>>>
> 
>>>>> (x86)\pthreads\include" -DLWS_EXT_PTHREAD_LIBRARIES="C:\Program
> 
>>> Files
> 
>>>
> 
>>>>> (x86)\pthreads\lib\x64\libpthreadGC2.a" && cmake --build . --config
> 
>>>
> 
>>>>> DEBUG && set CTEST_OUTPUT_ON_FAILURE=1 && ctest . -C DEBUG -j4
> 
>>>
> 
>>>>> --output-on-failure
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Building for: Visual Studio 16 2019
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Selecting Windows SDK version 10.0.18362.0 to target Windows
> 
>>> 10.0.18363.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- The C compiler identification is MSVC 19.25.28614.0
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
> 
>>>
> 
>>>>> Visual
> 
>>>
> 
>>>>>
> 
>>> Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.ex
> 
>>>
> 
>>>>> e
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
> 
>>>
> 
>>>>> Visual
> 
>>>
> 
>>>>>
> 
>>> Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.ex
> 
>>>
> 
>>>>> e
> 
>>>
> 
>>>>> - works
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Detecting C compiler ABI info
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Detecting C compiler ABI info - done
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Detecting C compile features
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Detecting C compile features - done
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Compiled with LWS_WITH_DIR and LWS_WITH_LEJP_CONF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- CMAKE_TOOLCHAIN_FILE=''
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Found Git: C:/Program Files/Git/cmd/git.exe
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_inline
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Git commit hash: 069e741d
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_inline - Success
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE___inline__
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE___inline__ - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE___inline
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE___inline - Success
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MALLOC_TRIM
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MALLOC_TRIM - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MALLOC_USABLE_SIZE
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MALLOC_USABLE_SIZE - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for fork
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for fork - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getenv
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getenv - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for malloc
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for malloc - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for memset
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for memset - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for realloc
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for realloc - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for socket
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for socket - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for strerror
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for strerror - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for vfork
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for vfork - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for execvpe
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for execvpe - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getifaddrs
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getifaddrs - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for snprintf
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for snprintf - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _snprintf
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _snprintf - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _vsnprintf
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _vsnprintf - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getloadavg
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for getloadavg - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for atoll
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for atoll - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _atoi64
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _atoi64 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _stat32i64
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for _stat32i64 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for clock_gettime
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for clock_gettime - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for dlfcn.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for dlfcn.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for fcntl.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for fcntl.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for in6addr.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for in6addr.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for memory.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for memory.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for netinet/in.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for netinet/in.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for stdint.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for stdint.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for stdlib.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for stdlib.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for strings.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for strings.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for string.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for string.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/prctl.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/prctl.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/socket.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/socket.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/sockio.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/sockio.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/stat.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/stat.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/types.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/types.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for unistd.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for unistd.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for vfork.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for vfork.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/capability.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for sys/capability.h - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for malloc.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for malloc.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for pthread.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for pthread.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for inttypes.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for inttypes.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for cap_set_flag in cap
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for cap_set_flag in cap - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for 4 include files stdlib.h, ..., float.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for 4 include files stdlib.h, ..., float.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_INTPTR_T
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_INTPTR_T - Success
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_PTHREAD_SETNAME_NP
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_PTHREAD_SETNAME_NP - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_GETOPT_LONG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAS_GETOPT_LONG - Failed Compiling with SSL
> 
>>>
> 
>>>>> support
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Found OpenSSL: C:/Program Files/OpenSSL/lib/libcrypto.lib (found
> 
>>>
> 
>>>>> version "1.1.1d")
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for openssl/ecdh.h
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> OpenSSL include dir: C:/Strawberry/c/include OpenSSL libraries:
> 
>>>
> 
>>>>> C:/Program Files/OpenSSL/lib/libssl.lib;C:/Program
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Files/OpenSSL/lib/libcrypto.lib
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for openssl/ecdh.h - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_set1_param
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_set1_param - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_set_info_callback
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_set_info_callback - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for X509_VERIFY_PARAM_set1_host
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for X509_VERIFY_PARAM_set1_host - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for RSA_set0_key
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for RSA_set0_key - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for X509_get_key_usage
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for X509_get_key_usage - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_PKEY_new_raw_private_key
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_PKEY_new_raw_private_key - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_get0_certificate
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_get0_certificate - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_get0_alpn_selected
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_get0_alpn_selected - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_set_alpn_protos
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_set_alpn_protos - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_cfb8
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_cfb8 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_cfb128
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_cfb128 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_192_cfb8
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_192_cfb8 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_192_cfb128
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_192_cfb128 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_256_cfb8
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_256_cfb8 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_256_cfb128
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_256_cfb128 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_xts
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_xts - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for RSA_verify_pss_mgf1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for RSA_verify_pss_mgf1 - not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for HMAC_CTX_new
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for HMAC_CTX_new - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_set_ciphersuites
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for SSL_CTX_set_ciphersuites - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_SSL_EXTRA_CHAIN_CERTS
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_SSL_EXTRA_CHAIN_CERTS - Success
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_EVP_MD_CTX_free
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_EVP_MD_CTX_free - Success
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for ECDSA_SIG_set0
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for ECDSA_SIG_set0 - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for BN_bn2binpad
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for BN_bn2binpad - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_wrap
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EVP_aes_128_wrap - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EC_POINT_get_affine_coordinates
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for EC_POINT_get_affine_coordinates - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for TLS_client_method
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for TLS_client_method - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for TLSv1_2_client_method
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Looking for TLSv1_2_client_method - found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_PIPE2
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_PIPE2 - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MBEDTLS_NET_SOCKETS
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_MBEDTLS_NET_SOCKETS - Failed
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_TCP_USER_TIMEOUT
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Performing Test LWS_HAVE_TCP_USER_TIMEOUT - Failed Searching for
> 
>>>
> 
>>>>> OpenSSL executable and dlls OpenSSL executable: C:/Program
> 
>>>
> 
>>>>> Files/Git/mingw64/bin/openssl.exe GENCERTS = 1 Generating SSL
> 
>>>
> 
>>>>> Certificates for the test-server...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> OPENSSL_INPUT_WIN_PATH =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\ope
> 
>>>
> 
>>>>> n
> 
>>>
> 
>>>>> ssl_input.txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> cmd = "C:/Program Files/Git/mingw64/bin/openssl.exe" req -new
> 
>>> -newkey
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> rsa:2048 -days 10000 -nodes -x509 -keyout
> 
>>>
> 
>>>>>
> 
>>> "C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build/libwebsockets-test-server.key.pem"
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -out
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> "C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build/libwebsockets-test-server.pem"
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> SUCCSESFULLY generated SSL certificate
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- RPM tools not available on Win32 systems
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Configuring done
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> ---------------------------------------------------------------------
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Settings: (For more help do cmake -LH <srcpath>)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> ---------------------------------------------------------------------
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_STATIC = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_SHARED = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_SSL = ON (SSL Support)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_SSL_CLIENT_USE_OS_CA_CERTS = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_WOLFSSL = OFF (wolfSSL/CyaSSL replacement for OpenSSL)
> 
>>>
> 
>>>>> LWS_WITH_MBEDTLS = OFF (mbedTLS replacement for OpenSSL)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_BUILTIN_SHA1 = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_BUILTIN_GETIFADDRS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_CLIENT = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_SERVER = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_LINK_TESTAPPS_DYNAMIC = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_TESTAPPS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_TEST_SERVER = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_TEST_SERVER_EXTPOLL = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_TEST_PING = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_TEST_CLIENT = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_EXTENSIONS = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITHOUT_DAEMONIZE = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_LIBEV = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_LIBUV = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_LIBEVENT = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_GLIB = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_IPV6 = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_UNIX_SOCK = 0
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_HTTP2 = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_ROLE_MQTT = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_SSL_SERVER_WITH_ECDH_CERT = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_MAX_SMP = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_PTHREAD_H = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_CGI = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_OPENSSL_ECDH_H = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_SSL_CTX_set1_param = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_RSA_SET0_KEY = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_HTTP_PROXY = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LIBHUBBUB_LIBRARIES =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> PLUGINS =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_ACCESS_LOG = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_SERVER_STATUS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_LEJP = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_LEJP_CONF = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_GENERIC_SESSIONS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_STATIC_PIC = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_RANGES = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_PLAT_OPTEE = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_PLAT_FREERTOS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_ZIP_FOPS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_AVOID_SIGPIPE_IGN = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_STATS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_SOCKS5 = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_SYS_CAPABILITY_H =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_LIBCAP =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_PEER_LIMITS = OFF
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_ATOLL = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE__ATOI64 = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAVE_STAT32I64 =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_HAS_INTPTR_T = 1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_EXPORT_LWSTARGETS = ON
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> LWS_WITH_ABSTRACT =
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ----------------------------------------- Generating done
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> -- Build files have been written to:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ------------------------------
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET
> 
>>>
> 
>>>>> Framework Copyright (C) Microsoft Corporation. All rights reserved.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Checking Build System
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> alloc.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> buflist.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> context.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws_dll2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> libwebsockets.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> logs.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> system.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> base64-decode.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws-ring.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> vfs.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> dummy-callback.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> output.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> close.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> network.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> vhost.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> pollfd.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> service.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sorted-usec-list.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> state.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> stats.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> wsi.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> wsi-timeout.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> adopt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-pipe.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sequencer.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> dir.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> header.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> parsers.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-h1.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-parser-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-raw-skt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-raw-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lwsac.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> cached-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> connect.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-http.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-handshake.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-listen.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-network.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-tls.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-x509.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-ssl.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sha-1.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> http2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> hpack.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-h2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-fds.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-init.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-misc.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-pipe.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-plugins.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-service.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-sockets.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws-spa.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> poll.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lejp.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lejp-conf.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> gettimeofday.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> websockets.vcxproj ->
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\lib
> 
>>>
> 
>>>>> \
> 
>>>
> 
>>>>> Debug\websockets_static.lib
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt_long.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> gettimeofday.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-client.vcxproj ->
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\bin
> 
>>>
> 
>>>>> \
> 
>>>
> 
>>>>> Debug\libwebsockets-test-client.exe
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-lejp.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt_long.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> gettimeofday.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-lejp.vcxproj ->
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\bin
> 
>>>
> 
>>>>> \
> 
>>>
> 
>>>>> Debug\libwebsockets-test-lejp.exe
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> getopt_long.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> gettimeofday.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> test-server.vcxproj ->
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\bin
> 
>>>
> 
>>>>> \
> 
>>>
> 
>>>>> Debug\libwebsockets-test-server.exe
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> alloc.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> buflist.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> context.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws_dll2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> libwebsockets.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> logs.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> system.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> base64-decode.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws-ring.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> vfs.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> dummy-callback.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> output.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> close.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> network.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> vhost.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> pollfd.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> service.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sorted-usec-list.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> state.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> stats.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> wsi.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> wsi-timeout.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> adopt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-pipe.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sequencer.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> dir.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> header.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> parsers.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-h1.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-parser-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server-ws.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-raw-skt.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-raw-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lwsac.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> cached-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> connect.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-http.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> client-handshake.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-listen.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-network.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-tls.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-x509.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-ssl.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> tls-client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> openssl-client.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> sha-1.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> http2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> hpack.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> ops-h2.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-fds.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-file.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-init.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-misc.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-pipe.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Compiling...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-plugins.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-service.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> windows-sockets.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lws-spa.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> poll.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lejp.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> lejp-conf.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> gettimeofday.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Generating Code...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> server.c
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Creating library
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build/lib
> 
>>>
> 
>>>>> /
> 
>>>
> 
>>>>> Debug/websockets.lib
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> and object
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build/lib
> 
>>>
> 
>>>>> /
> 
>>>
> 
>>>>> Debug/websockets.exp
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> websockets_shared.vcxproj ->
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:\Users\agreen\jobs\warmcat_com-windows-10.2\libwebsockets\build\bin
> 
>>>
> 
>>>>> \
> 
>>>
> 
>>>>> Debug\websockets.dll
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Building Custom Rule
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>
> 
>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/CMakeList
> 
>>>
> 
>>>>> s
> 
>>>
> 
>>>>> .txt
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> Test project
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> C:/Users/agreen/jobs/warmcat_com-windows-10.2/libwebsockets/build
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>> No tests were found!!!
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> saib> NSSTATE_DONE
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> -----邮件原件-----
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> 发送时间: 2020年4月22日15:00
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com
> 
>>>
> 
>>>>> <mailto:huangkaicheng at huawei.com>>;
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> 抄送: Chenyake <chenyake at huawei.com <mailto:chenyake at huawei.com 
> <mailto:chenyake at huawei.com%20%3cmailto:chenyake at huawei.com>>>;
> 
>>>
> 
>>>>> Zhangdong (Welber)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <welber.zhang at huawei.com <mailto:welber.zhang at huawei.com 
> <mailto:welber.zhang at huawei.com%20%3cmailto:welber.zhang at huawei.com>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> 主题: Re: 答复: A question about libwebsockets log
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> On 4/22/20 4:11 AM, huangkaicheng wrote:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Hi,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     In fact, log level is setted and log callbact is also setted.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     I maybe found why log is not print; In lws_config.h.in file ,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> /* lws_config.hGenerated from lws_config.h.in*/
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> #ifndef NDEBUG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     #ifndef _DEBUG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     #define _DEBUG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     #endif
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> #endif
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> The lines above mean that If project defined NDEBUG, libwesocket
> 
>>>
> 
>>>>>>> will
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> not define _DEBUG, so the log will not print(). Normally, we want
> 
>>>
> 
>>>>>>> to
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> It doesn't quite mean that... log levels _err, and _user are always
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> compiled in._warn, and _notice will also be included unless you
> 
>>> kill
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> them explicitly by setting LWS_WITH_NO_LOGS, which is usually
> 
>>> unwise.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> It's the other, more verbose log levels like _debug that are
> 
>>>
> 
>>>>>> affected
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> by whether it thinks you're building in debug mode or not.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> build libwebsockets with release mode, and VS or XCode will add
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> NDEBUG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> macro in project.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> If we not build in release mode ,the library size is bigger so
> 
>>> much
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> than in release mode.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> I am not sure how it works for windows, but in ELF-land (at least,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> Linux and OSX) the size of the file is a very bad guide to the size
> 
>>>
> 
>>>>>> of
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> the footprint of the code and data footprint, because usually huge
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> debugging sections are included in the ELF file that are never
> 
>>>
> 
>>>>>> loaded
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> into memory, just available for a debugger to get them out of the
> 
>>>
> 
>>>>>> file
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> conveniently if it needs them.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> For example if I build lws with RELEASE on Fedora and a lot of
> 
>>> extra
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> cmake options enabled, the .so is 700KB; in DEBUG it's 3MB.But if
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> you use the size tool to look at the actual footprint the
> 
>>> difference
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> is not so huge.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> RELEASE: (700KB elf file)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>    textdatabssdechexfilename
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>    40893513784324227516735f
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> lib/libwebsockets.so.16
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> DEBUG: (3MB elf file)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>    textdatabssdechexfilename
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>    594960147923260978494df8
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> lib/libwebsockets.so.16
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> The actual size difference is caused by DEBUG build turning off
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> compiler optimizations (-O0), include the additional logging, and
> 
>>> in
> 
>>>
> 
>>>>>> a
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> few cases there is code to dump structs and suchlike that is only
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> included in DEBUG build.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> So Is there a better way to Judge open debug logs instead of
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> “NDEBUG”in lws_config.in like define another macro
> 
>>> “LWS_LOG_DEBUG_SWITCH”eg?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> Ultimately, using "NDEBUG" is a decision set by CMake, it's not a
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> random choice.When you tell cmake -DCMAKE_BUILD_TYPE=RELEASE, the
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> crossplatform way to ask for that, it sets NDEBUG.And we do want
> 
>>> the
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> behaviour that RELEASE doesn't build in the verbose logs, at least
> 
>>>
> 
>>>>>> by
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> default, so we want to follow specifically NDEBUG.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> We want to print logs of libwebsockets with release mode, please
> 
>>>
> 
>>>>>>> help
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> to answer for me. Thanks.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> Lws always will "print logs" unless you forcibly turn that off, if
> 
>>> I
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> understand you, you mean "include the more verbose logging" in
> 
>>>
> 
>>>>>> release
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> mode.When you talk about lws not printing logs, it sounds like you
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> are saying it does not print anything at all.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> I pushed a patch on master that keeps everything as it is by
> 
>>>
> 
>>>>>> default,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> but lets you give cmake two bitfields to force adding and disabling
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> individual log levels from the build.Eg, you can give
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> -DLWS_LOGGING_BITFIELD_SET="(LLL_INFO | LLL_DEBUG)"
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> and those levels will be built in even in release.There's also
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> LWS_LOGGING_BITFIELD_CLEAR which forces levels you give it there
> 
>>> out
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> of the build.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> -Andy
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> -----邮件原件-----
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 发送时间: 2020年4月18日22:36
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:huangkaicheng at huawei.com>>;
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 抄送: Zhangdong (Welber) <welber.zhang at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:welber.zhang at huawei.com>>; Chenyake
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <chenyake at huawei.com <mailto:chenyake at huawei.com
> 
>>>
> 
>>>>> <mailto:chenyake at huawei.com%20%3cmailto:chenyake at huawei.com>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 主题: Re: 答复: some question about libwebsockets.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> On 4/18/20 3:05 PM, huangkaicheng wrote:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> Hi,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> I delete this line " #include <net/route.h>" in unix-sockets, t
> 
>>>
> 
>>>>>>>> can
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> build success in IOS platform. so this line is not used in IOS
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> platform in fact. How can I define like macro " TARGET_OS_IPHONE "
> 
>>> as you said?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>   From google, if you build for iOS, TARGET_OS_IPHONE should be
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> defined
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> on your compiler already somehow.Anyway this is good news.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> We have some questions as follows ,please help to answers for us.
> 
>>> Thanks.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 1、And as you said, you mean that libwebsocket doesnot support in
> 
>>> IOS?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> What does it really mean, "support"... it's not a commercial
> 
>>> product.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> The license says there are no promises about anything including
> 
>>>
> 
>>>>>>> even
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> that it works at all.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> There's CI for lws atm on Windows 10, current OSX, Mediatek
> 
>>> Linkit,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Fedora 32, Ubuntu Bionic and Xenial.These are platforms for one
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> reason or another I'm interested in keeping working right now, and
> 
>>>
> 
>>>>>>> I
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> stood a chance to make the CI work on them.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> People have been using lws on Android and iOS and Arm64 Windows...
> 
>>>
> 
>>>>>>> I
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> personally don't have those platforms and don't have much idea how
> 
>>>
> 
>>>>>>> to
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> set up CI for them.But so long as the other platforms work well,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> probably lws will continue to work on these other ones too.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> But if you or others care about a platform, you can monitor lws
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> master
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> and let me know if I break something / send patches.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 2、I have another question about libwebsocket logs level. I have
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> defined
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> -DCMAKE_BUILD_TYPE=DEBUG in scripts as follows.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #bash!
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> echo
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> echo libwebsockets mac
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> mkdir build-mac
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> cd build-mac
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> /Applications/CMake.app/Contents/bin/cmake .. -G Xcode
> 
>>> -DCMAKE_OSX_ARCHITECTURES=x -DCMAKE_BUILD_TYPE=DEBUG
> 
>>> -DLWS_OPENSSL_INCLUDE_DIRS=../../../openssl/include/
> 
>>> -DLWS_OPENSSL_LIBRARIES="../../../openssl/lib/mac/libcrypto.a;../../../openssl/lib/mac/libssl.a"
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> xcodebuild -configuration Release
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> But the log of libwesockets is not output. It seem that
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> DCMAKE_BUILD_TYPE=DEBUG does not take effect. And I found macro
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> _DEBUG
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> is not exits in project.And I found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> There are three different things here
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - output logs at all... by default these come out on stderr if
> 
>>>
> 
>>>>>>> you
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> set up
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> lws_set_log_level(LLL_USER | LLL_ERR | LLL_WARN | LLL_NOTICE,
> 
>>>
> 
>>>>>>> NULL);
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> like the examples.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - build more verbose logs... with CMAKE_BUILD_TYPE RELEASE, any
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> verbosity for INFO and above are removed from the build.With
> 
>>> DEBUG,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> these are included.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - actually show more verbose logs.If you set the logging
> 
>>>
> 
>>>>>>> bitfield
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> to
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> 1151 or so, you will get many logs, it's the same as run the
> 
>>>
> 
>>>>>>> minimal
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> examples with -d 1151.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Don't assume CMAKE_BUILD_TYPE=DEBUG is broken, if you have no logs
> 
>>>
> 
>>>>>>> at
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> all it sounds like you don't call lws_set_log_level or stderr is
> 
>>>
> 
>>>>>>> not
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> visible.The second parameter lets you set your own log emit
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> function, so you can wire it up to your platform logging api.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Sanity-check using lws out of the box with cmake commands on Linux
> 
>>> or OSX.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> NDEBUG macro. How to make it table effect with release build
> 
>>> mode.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> I recently started to set up new CI arrangements based on Sai and
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> CTest, including on OSX.If you're literally building for OSX, the
> 
>>>
> 
>>>>>>> CI
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> for the variant with the minimal examples looks like this, using
> 
>>>
> 
>>>>>>> brew
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> to install openssl.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> mkdir build; cd build; cmake ..
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> -DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/opt/openssl at 1.1/include 
> <mailto:-DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/opt/openssl at 1.1/include>
> 
>>>
> 
>>>>>
> 
>>> <mailto:-DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/opt/openssl at 1.1/include
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>> <mailto:-DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/opt/openssl at 1.1/includ
> 
>>>
> 
>>>>>> e
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>> <mailto:-DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/opt/openssl at 1.1/inclu
> 
>>>
> 
>>>>>>> d
> 
>>>
> 
>>>>>>> e
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>> -DLWS_OPENSSL_LIBRARIES="/usr/local/opt/openssl/lib/libssl.dylib;/usr/local/opt/openssl/lib/libcrypto.dylib"
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> -DLWS_WITH_MINIMAL_EXAMPLES=1 && make -j
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> Is there confict between " DCMAKE_BUILD_TYPE=DEBUG " and "
> 
>>>
> 
>>>>>>>> xcodebuild
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> -configuration Release" ?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Dunno.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> How can make library with release mode and the logs of
> 
>>>
> 
>>>>>>>> libwebsockets
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> can
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> output well(debug level). In stable 4.0 version, "Notice Level"
> 
>>> seem
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> that cannot output normally Without " DCMAKE_BUILD_TYPE=DEBUG " and
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> old version (2.3 version) can output normally. Is something
> 
>>> Changed?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> Don't think so since it works well here.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 3、another question, because we use libwebsockets for ws client.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> We hope
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> that we build library as little as possible. We only use the ws
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> client
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> with ssl in libwebsockets(windows、ios、android、mac). Is there some
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> ways
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> to make the library more little?
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - build it in RELEASE
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - -DLWS_WITHOUT_SERVER=1
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - -DLWS_WITH_HTTP2=0 -DLWS_ROLE_H2=0 if you don't need it
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - -ffunction-sections, -fdata-sections
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>     - use mbedtls
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> On bare metal arm, client h1 + ws should be ~50KB total flash
> 
>>> size.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> If you are using openssl, you can be sure lws is not the big thing
> 
>>>
> 
>>>>>>> in
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> your system bloating the size...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> -Andy
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> -----邮件原件-----
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 发送时间: 2020年4月13日21:39
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:huangkaicheng at huawei.com>>;
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> libwebsockets at ml.libwebsockets.org 
> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 抄送: Zhangdong (Welber) <welber.zhang at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:welber.zhang at huawei.com>>; Chenyake
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> <chenyake at huawei.com <mailto:chenyake at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:chenyake at huawei.com%20%3cmailto:chenyake at huawei.com>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> 主题: Re: A question about build fail for ios platform in mac
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> On 4/13/20 1:22 PM, huangkaicheng wrote:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> Hi,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> IF (CMAKE_SYSTEM_NAME STREQUAL Linux)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> CHECK_FUNCTION_EXISTS(eventfd LWS_HAVE_EVENTFD)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> ENDIF()
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> After We change the line, we meet another fail. How to solve
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> this problem as follows. . Please check out the attachment for
> 
>>>
> 
>>>>>>>>> more
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> details
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> libwebsockets-4.0-stable/lib/plat/unix/unix-sockets.c:31:10:
> 
>>>
> 
>>>>>>>>> fatal
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> error: 'net/route.h' file not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> #include <net/route.h>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> It seem ios platform does not support “net/route.h”. Have you
> 
>>>
> 
>>>>>>>>> build
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> success with your CI for IOS? Old version (2.3)seem that it does
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> not
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> use “net/route.h”.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> I think there's a little confusion here... there's no CI for iOS.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> There's CI for OSX and Linux and Windows.But I am not an Apple
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> developer or and Android developer personally so
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> it's not what I am going to spend my time on without some reason.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> This FOSS, if you contribute fixes and help to maintain the
> 
>>>
> 
>>>>>>>> platform
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> you care about that's great we can support it.But we are not some
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> kind of supplier with a support contract that has to
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> run around making it workfor you on your proprietary platform.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> If your platform doesn't have net/route.h, well, OK there is
> 
>>> quite a bit of variation on unixy and posixy platforms with that kind
> 
>>> of thing...
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> the usual method would be comment out the include and see what
> 
>>> breaks if anything in the compile that was expecting things from that
> 
>>> include.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> If, eg, someapi() can't build then, grep around for someapi() in
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> your
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> platform toolchain includes to see if it exists somewhere else on
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> that
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> platform.If so, then good, hack that include in instead and send
> 
>>> a
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> patch, preferably like
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #if defined(TARGET_OS_IPHONE)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #include <xxx.h>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #else
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #include <net/route.h>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> #endif
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> If not, well, let's discuss what apis are affected and see what
> 
>>> we can figure out.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>> -Andy
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>> imap://andy@warmcat.com:993/fetch%3EUID%3E.INBOX%3E125878?header=
> 
>>>
> 
>>>>>>>>> q
> 
>>>
> 
>>>>>>>>> u
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> o
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> t
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> e body&part=1.1.2&filename=image001.png
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> -----邮件原件-----
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> 发件人: Andy Green [mailto:andy at warmcat.com]
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> 发送时间: 2020年4月11日19:55
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> 收件人: huangkaicheng <huangkaicheng at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:huangkaicheng at huawei.com>>;
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> libwebsockets at ml.libwebsockets.org
> 
>>>
> 
>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> 抄送: Zhangdong (Welber) <welber.zhang at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:welber.zhang at huawei.com>>; Chenyake
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> <chenyake at huawei.com <mailto:chenyake at huawei.com
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:chenyake at huawei.com%20%3cmailto:chenyake at huawei.com>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> 主题: Re: [Libwebsockets] 答复: A question about build fail for ios
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> platform in mac
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> On 4/11/20 12:41 PM, huangkaicheng wrote:
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> Hi,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> We build stable 4.0 libwebsockts in ios platform, But It build
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> fail. Please check out the attachment for more details
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> fatal error: 'sys/eventfd.h' file not found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> But cmake check as follows,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> -- Looking for eventfd
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> -- Looking for eventfd –found
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> How to build success for ios platform in mac,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> I don't have this platform... lws builds well on Linux and OSX
> 
>>> though.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> Currently it looks for eventfd function and thinks it means it
> 
>>>
> 
>>>>>>>>> must
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> have linux eventfd + sys/eventfd.h... that's not enough if some
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> other
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> platform exposes eventfd. From googling around OSX / BSD doesn't
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> have eventfd but something named differently, it's unlikely (but
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> not
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> impossible) the build host itself exposes an "eventfd()"
> 
>>> function.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> You'll need to look around in your platform cross toolchain
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> includes
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> what if anything exposes eventd() and if it's related to Linux
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> eventfd support.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> If it's unrelated, or nothing about eventfd in your cross
> 
>>>
> 
>>>>>>>>> toolchain
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> headers, let me know andwe can change this line
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> CHECK_FUNCTION_EXISTS(eventfd LWS_HAVE_EVENTFD)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> to
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> IF (CMAKE_SYSTEM_NAME STREQUAL Linux)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> CHECK_FUNCTION_EXISTS(eventfd LWS_HAVE_EVENTFD)
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> ENDIF()
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> If it's related but on iOS the header for it is different or not
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> needed, if you can explain the details we can work around it
> 
>>> accordingly.
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> -Andy
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> Greets,
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> huangkaicheng
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> _______________________________________________
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> Libwebsockets mailing list
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> Libwebsockets at ml.libwebsockets.org
> 
>>>
> 
>>>>> <mailto:Libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>> <mailto:Libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>> <mailto:Libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>> <mailto:Libwebsockets at ml.libwebsockets.org>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>> https://libwebsockets.org/mailman/listinfo/libwebsockets
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>>
> 
>>>
> 
>>>>>
> 
>>>
> 
>>>>>>
> 
>>>
> 
>>>>>
> 
_______________________________________________
Libwebsockets mailing list
Libwebsockets at ml.libwebsockets.org
https://libwebsockets.org/mailman/listinfo/libwebsockets
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2904ED04 at BE3FE22F.C531B85E.jpg
Type: image/jpeg
Size: 70587 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lws-timeout-timer.h
Type: application/octet-stream
Size: 10407 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wsi-timeout.c
Type: application/octet-stream
Size: 11585 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: client-handshake.c
Type: application/octet-stream
Size: 47773 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0009.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: private-lib-core-net.h
Type: application/octet-stream
Size: 37024 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0010.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test-client.c
Type: application/octet-stream
Size: 23404 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0011.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libwebsocket log1
Type: application/octet-stream
Size: 347855 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0012.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: websocke-log2
Type: application/octet-stream
Size: 180914 bytes
Desc: not available
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200511/9dc07fd5/attachment-0013.obj>


More information about the Libwebsockets mailing list