Skip to content
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

Remove 'Experimental' label from Core Build Makefile projects. #805

Merged
merged 5 commits into from
May 30, 2024

Conversation

ewaterlander
Copy link
Contributor

Removed the 'Experimental' label in project creation wizard for Core Build Makefile projects. Seven years after the inception it's time to remove it. Core Build Makefile is now in a usable state. The 'Experimental' label scares users away from it, making them fall back to the old Managed Build Makefile projects.

Removed the 'Experimental' label in project creation wizard for Core
Build Makefile projects. Seven years after the inception it's time to
remove it. Core Build Makefile is now in a usable state. The
'Experimental' label scares users away from it, making them fall back
to the old Managed Build Makefile projects.
@ewaterlander
Copy link
Contributor Author

I can add that at Intel we built a custom flow on top of Core Build Makefile which is working fine.

…ld projects.

To lower the risk of overwriting existing code the option to create an
example is by default disabled.
Update service number.
Undid accidental update of org.eclipse.cdt.cmake.ui version.
Copy link
Member

@jonahgraham jonahgraham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than minor fix, lets go for this. Thank you for moving this forward!

@jonahgraham jonahgraham added this to the 11.6.0 milestone May 30, 2024
@jonahgraham jonahgraham added the build Build components of CDT, anything to do with running the compiler, using Make, CMake, or any builder label May 30, 2024
@jonahgraham jonahgraham merged commit d8328fb into eclipse-cdt:main May 30, 2024
5 checks passed
@ewaterlander
Copy link
Contributor Author

ewaterlander commented May 30, 2024

@jonahgraham

In addition I want to say that we must not fall in the trap of adding lots of features to Core Build Makefile to make it 'in parity' with the bloated Managed Build Makefile. Core Build flow (all flavors of it) has intentional less build features. The motto is 'keep it simple'. The use case is a multi-user environment where some people use IDE and some use command line. The IDE is not the master of project build settings. Compare it to how vscode works. The projects vary from single to multi-target applications. There are discussions ongoing about making Core Build CMake equally feature rich as Managed Build Makefile. I think this is a mistake, comparing apples with oranges, and ignoring the ideas that Doug Schaefer had about Core Build. My 2 cents...

We are now using Core Build Makefile and we plan to use Core Build CMake in the future. I would like to participate in the discussions about CMake. I plan to join the next CDT monthly meeting.

@ewaterlander ewaterlander deleted the remove_experimental branch May 30, 2024 13:28
@jonahgraham
Copy link
Member

The IDE is not the master of project build settings.

+1 to your whole comment - especially this. This is certainly a change from how things used to be.

I plan to join the next CDT monthly meeting.

Wonderful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build components of CDT, anything to do with running the compiler, using Make, CMake, or any builder
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants