Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Arthur Barrett wrote:
> It's been a very long time since I've needed to modify a makefile because a
> file changed it's name or a file was added. There is syntax to look for all
> *.c files (or whatever) and loop cc -c {filename} or whatever.
I guess that depends a lot on your specific build environment.
> Yes I can see that if you merge a change in a makefile that changes the
> filename from fred.c to fred.cpp and the same merge doesn't change the
> filename then you have a problem - but the problem is in the build
> system not the CM system. Yes I do believe we need a better open source
> build system - there is no equivalent for things like 'clearmake' in the
> FOSS world and there should be.
I don't think it makes sense to restrict a CM system to a specific build
system. There are way too many different types of "builds", I think, and
not always is it possible to include all files in a directory in a build;
sometimes you may have to specify exactly which files to include in what
build.
Besides, this is not only about makefiles and the like. If you rename foo.h
to baz.h, you have to change all relevant #includes (talking about C or C++
here). Merging the changed #include lines but not the rename is guaranteed
to break the build.
Gerhard