Closed andimik closed 6 years ago
Yes, I don't know why this is necessary. If you find a way to improve the boost configure check please do a pull request.
Even a hint in the README would be useful.
Of course, I will change the INSTALL file and make a PR to the next branch
Great! Otherwise, you can try replacing boost::asio by http://think-async.com/Asio/ and we will then be able to remove the dependency on boost. That would be neat.
This needs adding asio.hpp
into the repository, and replacing boost in src/RemoteControl
I'll replace boost by asio.hpp
now
The boost requirement is gone in next
.
I found out that the boost version or path (?) produces an error under a RPi3.
Then I found the solution
worked then