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

infrastructure: Use CMake instead of the current build system #268

Open
cristian-vijelie opened this issue Apr 9, 2023 · 2 comments
Open
Labels
area/infra Update to infrastructure / scripts kind/improve Improve / Update existing content / item

Comments

@cristian-vijelie
Copy link
Contributor

The current build system, with included Makefiles from 6 folders up in the directory tree seems to me like reinventing the wheel. We should consider using a more standardised build system, like CMake, ninja or the like

@teodutu
Copy link
Member

teodutu commented Apr 10, 2023

We have this in mind somehow. I introduced the generic makefiles in #6 because I was always copying and pasting the same makefile to every exercise. But now this makes extracting a single exercise (if you want to use it in another context such as another class) difficult. Using CMake seems to be a solution for most of our troubles.

@teodutu teodutu added area/infra Update to infrastructure / scripts kind/improve Improve / Update existing content / item labels Apr 10, 2023
@gabrielmocanu
Copy link
Contributor

Bazel might be a solution. We need someone to take ownership on this.😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra Update to infrastructure / scripts kind/improve Improve / Update existing content / item
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants