Thanks for this suggestion, I definitely know that's something that could be added. Unfortunately currently this is a manual process, and it's too much work for me to do manually for each release.
I would be very open to a high-quality PR that adds automatic release artifacts to the CI build scripts.
Also it is worth mentioning that eos is first and foremost a library for developers. The library is header-only, thus it does not need to be built - it can simply be #included into projects. And the examples (which could be compiled) are just that: Simple examples of the library, making it easy to get started - but not meant as "final" or full-fledged apps.
Second, the Python bindings can also be installed via pip install eos-py, not requiring the user to compile anything manually.
Hi,
Thanks for this suggestion, I definitely know that's something that could be added. Unfortunately currently this is a manual process, and it's too much work for me to do manually for each release.
I would be very open to a high-quality PR that adds automatic release artifacts to the CI build scripts.
Also it is worth mentioning that eos is first and foremost a library for developers. The library is header-only, thus it does not need to be built - it can simply be #included into projects. And the examples (which could be compiled) are just that: Simple examples of the library, making it easy to get started - but not meant as "final" or full-fledged apps.
Second, the Python bindings can also be installed via
pip install eos-py, not requiring the user to compile anything manually.