On 04/06/2016 10:18, Georg Baum wrote:
Abdelrazak Younes wrote:
Hi Guys,
Funny to discover that the same discussion is coming back every couple
of years :-)
I am not surprised at all, maintaining two build systems with such a small
amount of developers is simply stupid.
I agree.
The main disadvantage of GLOB is that it can mess up your build if you
let in the source tree some files that was renamed for debugging or
development purpose. Personally I never do that because git branching
and stashing are so good that it is much simpler to use git instead of
manual renaming; but I can fully understand that you are not comfortable
with that.
For renaming files or adding new files I would prefer to handle that
completely in git as well. However, it does not work. If I add a new file
and then stash the changed away, git adds the new file to the stash, but
does not delete the one in the local working tree, so when I pop from the
stash again I get a conflict. Therefore, I do not add new files to the
stash, and then I can easily move around.
In this case branching is the solution, not stashing indeed.
1) Switch to CMake now
2) Take advantage of GLOB to do the much needed file hierarchy cleanups
now (both folder hierarchy and file/class names)
3) Switch file listing mode without GLOB.
Switching to cmake first and some time later from GLOB to explicit file
listing would create a huge amount of work, since you would need to recreate
all file lists from scratch.
Creating a list with all files in the tree is very simple... You can
even automate that with CMake I think.
Anyway, those are details I think, the important thing to decide is to
switch or not.
Thanks,
Abdel.
