weird cmake structure in this project #145
MasakatsuFunaki
started this conversation in
General
Replies: 1 comment
-
Having one CML file per directory is dogmatic. The only time when it makes sense is if you are used to make style in-source builds squirting build artifacts all over the source directory, but that's already very bad practice (in-source builds), so with that gone having a CML in every directory loses its purpose. The project generates a flat structure for the simple case, which can be tweaked freely in any fashion. Tests for example are already separated where possible (library projects). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Best practice is to have one CMakeFilelist.txt per folder . This project uses a root cmake from which everything is added , like exes , shared libraries etc . This is terrible idea and contradict with the basic principle of sw development called partitioning or decomposition.
I thought this was a well defined project
Beta Was this translation helpful? Give feedback.
All reactions