You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually there are minimal and separate cmake in the folders of library tools and tests.
I think that will be good have a complete one in the root folder, that make possibile configure, build and install of all components (or optionally only one or 2 instead).
The complete and better one probably can be done when the project will be in more mature state, but a minimal from main folder using mainly cmake files already done will be useful.
Usage tips
Please use the 👍 reaction to show that you are interested into this.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this.
Subscribe to receive notifications on status change and new comments, you can do also without add comment.
The text was updated successfully, but these errors were encountered:
about the build system it can still be improved, improvements I had done I would define as only the essentials
about stable-v2.0 merge to master is good as master it had gotten a little confusing but other changes are needed from a fast look to the commit
I don't have time to deep check and do a PR now, for example one thing in README should be re-adding the part at the top regarding the old module for veeam users
Description
Actually there are minimal and separate cmake in the folders of library tools and tests.
I think that will be good have a complete one in the root folder, that make possibile configure, build and install of all components (or optionally only one or 2 instead).
The complete and better one probably can be done when the project will be in more mature state, but a minimal from main folder using mainly cmake files already done will be useful.
Usage tips
The text was updated successfully, but these errors were encountered: