On 10/2/2016 3:24 PM, Oswin Krause wrote:
Hi,
On 2016-10-02 19:01, Edward Diener wrote:
On 10/1/2016 8:58 PM, Paul Fultz II wrote:
On Oct 1, 2016, at 7:39 PM, Vinnie Falco
wrote: On Sat, Oct 1, 2016 at 8:20 PM, Paul Fultz II
wrote: The library looks nice
Thanks!
I tried to run the tests and install it using cmake and it both failed.
If you could please be so kind as to create an issue on the Beast GitHub repository page with the details, I will try to address it right away: https://github.com/vinniefalco/Beast/issues
Ok, will do.
Also, looking at the cmake, it looks like you use coroutines.
Beast is header-only, the Jamfile and CMakeLists.txt are only for building the unit tests and the examples.
Well, cmake should install the library, even its header-only.
Why should CMake "install" a header-only library ? Boost does not use CMake and header-only libraries do not need to be "installed".
to install the header files into the final location of the boost libraries
If you follow the Boost directory structure your header files are in the right place as soon as you unzip your library beneath the Boost libs subdirectory. Afterward running 'b2 headers' from the Boost top-level directory creates the links to your header files under the Boost boost subdirectory. There is absolutely no need for anything else for a header-only library, nor is there a need to make things more complicated than they need to be. Of course if you are not going to follow the Boost directory structure you will make things needlessly complicated.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost