Oliver, On Tuesday, 2016-08-16 19:50:44 +0200, you wrote:
> ... > There would be a doc folder if there would be an easy way to tell the > makefile > where to produce the output. The natural way when using "make" is to place the output into the same directory as the input. The easiest way is to just leave it that way and to instruct the users to issue the command $ make -C doc doc $ If you hate the idea of modifying the source directory tree in any way, "cmake" should be told to copy changed files from the "doc/" directory into directory "../build_QMapShack/doc/" using something similar to the "-pru" options of the "cp" command. Then we could advise the users to just run $ cd build_QMapShack $ make -C doc doc $ > You might remember I asked for it a couple of > month ago. But as you refused to add such a feature I abandonned the idea to > integrate document creation into the cmake process. I respect your decision to base QMapShack on "cmake". But I also expect you to respect my decision not to dig into the art of maintaining pro- jects using "cmake". Statements like the one above (you "asked for it" but I "REFUSED to add" it (capitalization by me), and so it's my fault that you "abandoned the idea") is nothing I'd like to read here again. To clarify: I wanted offline QMapShack documentation, cloned the wiki repository, found John Gruber's original Perl script from 2004 not to be up to the task of converting more modern Markdown dialects, wrote my own scripts and shared them with you, in case someone else might have simil- ar needs. I'm perfectly comfortable with the current situation, and I never understood my contributions as signing a contract to integrate my scripts into "cmake"! Sincerely, Rainer ------------------------------------------------------------------------------ _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
