Any interest in using a build system ? about version2 HOT 2 CLOSED

Thank you for your proposal.
I don't want to confine the vector class library to any particular build system. Many users will prefer different build systems for various reasons. The Apache license allows you to make any forking you like, but it would be your responsibility to keep it up to date.

The manual in .pdf format can be read in standard web browsers. I made it from .tex so that github can show diffs.

from version2.

Thank you for your feedback!

There's one thing I wasn't clear enough on, about the build system: I was making the suggestion to you in particular. When I talked about the build system lock-in, it was regarding your own use of your library, in the sense that you would have to change your own development process to integrate the build system, and switching to another one will require yet another learning curve.
Otherwise, the library can offer support for various build systems at the same time: the folder structure of the project can be fixed, and interested parties can simply contribute the build system they use, for example. But the main one would be the one you would adopt.

Also, I expect that this library is not packaged by linux distributions because of the lack of build system 🤔 not that it makes any significant difference with the simple way we can use the library, as it is (nearly) header only.

I understand very well your stance in both using a build system and about using Latex.

Shall we close this issue or keep it open so people who are interested in using build systems see it ?

Thanks again!

from version2.