Change #include in headers to relative paths
dok-net opened this issue · comments
Currently, there must be an include path setting during compilation. In my understanding, in modern C++ the meaning of #include "" syntax used by libcoro for all recursive includes in the library is that path resolution is defined as relative to the includers location.
I am using libcoro in environments where I use only a subset, only the header-only parts, and setting additional include-paths is difficult or fails. It would be very helpful to change the includes upstream instead of patching them each time.
I am proposing PR #150 that changes the #includes.