GitHub user anand-ftc added a comment to the discussion: raspberry 3 - 
pulsar-client python

@tisonkun I tried first compiling the cpp shared objects following 
https://github.com/apache/pulsar-client-cpp#compilation


Then followed the https://github.com/apache/pulsar-client-python to build the 
python client wheel files. this is where there are errors in finding the 
dependencies. 

> pi@raspberry:~/sources/pulsar/pulsar-client-cpp $ cmake 
> -DCMAKE_TOOLCHAIN_FILE=./toolchain-arm32.cmake 
> -DCMAKE_FIND_ROOT_PATH=/usr/arm-linux-gnueabihf  .
> -- ARCHITECTURE: x86_64
> -- BUILD_DYNAMIC_LIB:  ON
> -- BUILD_STATIC_LIB:  ON
> -- BUILD_TESTS:  OFF
> -- BUILD_PYTHON_WRAPPER:  ON
> -- BUILD_WIRESHARK:  OFF
> -- BUILD_PERF_TOOLS:  OFF
> -- LINK_STATIC:  OFF
> -- USE_LOG4CXX:  OFF
> -- CMAKE_BUILD_TYPE:  RelWithDebInfo
> CMake Error at 
> /usr/share/cmake-3.7/Modules/FindPackageHandleStandardArgs.cmake:138 
> (message):
>   Could NOT find Threads (missing: Threads_FOUND)
> Call Stack (most recent call first):
>   /usr/share/cmake-3.7/Modules/FindPackageHandleStandardArgs.cmake:378 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.7/Modules/FindThreads.cmake:212 
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   CMakeLists.txt:90 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also 
> "/home/pi/sources/pulsar/pulsar-client-cpp/CMakeFiles/CMakeOutput.log".
> See also 
> "/home/pi/sources/pulsar/pulsar-client-cpp/CMakeFiles/CMakeError.log".
> CMake Error: Unable to open check cache file for write. 
> /home/pi/sources/pulsar/pulsar-client-cpp/CMakeFiles/cmake.check_cache
> 

@tisonkun I tried the pip3 install pulsar-client. It says the following

>  Could not find a version that satisfies the requirement pulsar-client (from 
> versions: )
> No matching distribution found for pulsar-client

GitHub link: 
https://github.com/apache/pulsar/discussions/18423#discussioncomment-4114571

----
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

Reply via email to