You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@zookeeper.apache.org by GitBox <gi...@apache.org> on 2019/11/29 10:45:20 UTC

[GitHub] [zookeeper] symat commented on issue #1159: ZOOKEEPER-3630: Autodetection of openssl during ZooKeeper C client build

symat commented on issue #1159: ZOOKEEPER-3630: Autodetection of openssl during ZooKeeper C client build
URL: https://github.com/apache/zookeeper/pull/1159#issuecomment-559747775
 
 
   > (I am not a C expert)
   
   (me neither :) )
   
   > are we compiling statically openssl lib ? 
   
   I think we basically link together all the dependent libs, when building the command line client. At least, I was able to connect to a ZK server using the C command line client with SSL, even when I executed it in a docker container with no openssl installed. So the openssl is only compile-time dependency, but it will end up in the ZooKeeper client binary.
   
   We are also building the ZooKeeper libraries (they are used e.g. by the python binding). Based on the README file in the c-client folder, we can compile both static and shared libraries with autotools, but with cmake we only build static and the shared library function is not implemented yet. Unfortunately I am also quite inexperienced in the C world, so I can not really verify these statements :)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services