search

cpp-redis / cpp_redis

C++11 Lightweight Redis client: async, thread-safe, no dependency, pipelining, multi-platform
MIT License
720 stars 199 forks source link

CMake Error: install(EXPORT "cpp_redis" ...) includes target "cpp_redis" which requires target "tacopie" that is not in any export set. #120

Closed alphamarket closed 1 year ago

alphamarket commented 1 year ago

Describe the bug When I am trying to compile the project I am getting the following error from CMake:

CMake Error: install(EXPORT "cpp_redis" ...) includes target "cpp_redis" which requires target "tacopie" that is not in any export set.

To Reproduce Steps to reproduce the behavior:

git clone https://github.com/cpp-redis/cpp_redis.git --depth 1 && \
    cd cpp_redis && \
    git submodule init && \
    git submodule update && \
    mkdir build && cd build && \
    cmake .. -DCMAKE_BUILD_TYPE=Release && \
    make -j`nproc`

Expected behavior I can compile the project the without any problem.

Screenshots image

Desktop:

AliSalehian commented 1 year ago

Same problem in Ubuntu Focal Fossa 20.04

alphamarket commented 1 year ago

I just changed my library to work with redis to this library

AliSalehian commented 1 year ago

I just changed my library to work with redis to this library

I used to use the redis-plus-plus library, and it worked properly. However, I encountered an issue with its pub/sub implementation. I wanted to listen to a Redis channel without consuming excessive CPU resources. Additionally, I wanted to achieve this without employing the uv_loop for creating event behavior. Do you have any experience with this situation?

alphamarket commented 1 year ago

I just changed my library to work with redis to this library

I used to use the redis-plus-plus library, and it worked properly. However, I encountered an issue with its pub/sub implementation. I wanted to listen to a Redis channel without consuming excessive CPU resources. Additionally, I wanted to achieve this without employing the uv_loop for creating event behavior. Do you have any experience with this situation?

No, I don't have any experience on that topic; I usually handle pub/sub operations using Kafka as MQ, which is very easy to use and doesn't require that much of resources, You can signal the data in Kafka, and the other component will pick it up.

Also please be advised that this library doesn't support cluster Redis deployments; if you are doing something serious.