-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Results of the spike investigation into CMake. #7114
Conversation
Manage this branch in SquashTest this branch here: https://amossspike-cmake-clean-5aq6q.squash.io |
Note: I did not find an explicit way to select compiler when both `clang` and `gcc` are | ||
present. We might have an implicit way (like redirecting `cc`) but we should put one in. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you have 3 blank lines here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For luck :) I can remove them...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, I did not wanna force nobody approve it again! :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a format problem, but this is small, congratulations @amoss !
The BUILD.md will be updated during the progress of netdata#7150.
The BUILD.md will be updated during the progress of netdata#7150.
Summary
Fixes #4310
Component Name
area/deamon
Additional Information
This is a summary of the investigation results from the spike. Everything is contained in
BUILD.md
in the root of the repo. The tl;dr is "yes, we should switch to cmake", and we know how to implement each of the cases that we will encounter. This is not a strict recipe for how to do this as we had to control the scope of the investigation and start writing a prototype of the new build-system.Everybody who is affected by changing build-systems should review the file. [If I've missed anybody as reviewer that is affected please add them]. If you any major problems please comment straight away so that we can start discussing them. If you don't see anything major then the next step will be an internal meeting to check that we have a common understanding of how the replacement will work, and what effect it will have on everybody's areas. After that meeting I will create a fresh issue (connect/close any old outstanding issues) and describe what needs to be done in the prototype in enough detail that we can estimate timescales (based on the steps in the Recommendations section).
The document is not attached to the pull-request separately as it will need changes based on feedback and I don't want a stale copy of it.