Reported by Adrien Michel, Aug 8, 2019
I am wondering why is a Makefile present in doc/examples. Indeed, a CMakeList.txt file is also present so user can run cmake. The makefile prescribes a compiler (g++), which makes the compilation fail if meteoio has been complied with another compiler. In other words, while cmake will read CC and CXX env. variables, the Makefile won't. So in my opinion no makefile should be provided. It could be automatically generated from running cmake in trunk, to be adjusted to the computer requirements.
Comment 1 by Michael Reisecker, Aug 8, 2019
I was quite confused by this as a completely new user, since it's a version controlled file that is automatically changed if you compile the documentation. It's sometimes annoying to handle with svn, so I would rename it. I'd keep it though because it's a useful template to distribute MeteoIO programs - kind of an example program by itself. Just my two cents. :-)
Comment 2 by Mathias Bavay, Aug 26, 2019
Yes, the goal was to provide both a CMakeList and a classical Makefile that show how to use MeteoIO in a build system. I've renamed the Makefile into something like "makefile.example" to make it clearer and to prevent it from interfering with svn (see commit 2481)