Werner LEMBERG <w...@gnu.org> writes: >>> No doubt about that, but we're not in the situation to fix Windows. >> >> Is the problem Windows, or that many of the GNU dependencies are >> difficult to install on Windows? > > It's mainly a problem that we don't have a single devoted Windows > developer with good knowledge of all the nasty intricacies of that > operating system. As far as I know, all developers on Windows > contribute either Scheme stuff or documentation.
No, that isn't the problem. The problem is that Windows has no working packaging and dependency system, no working installation conflict management, and requires working through a global and fragile registry. That results in incredible amounts of effort to get a dozen dependencies into a working combined installation. All the dependencies of LilyPond _can_ already be properly satisfied on Windows. But after you finished it, you'll not be in the mood to do anything with LilyPond any more. Or Windows. Ever. And crap like bad line end conventions and strange permissions will continue to plague your contributions. > Maybe this changes eventually. It seems that LLVM will soon work on > Windows also; this essentially means that there will be a native > compiler on Windows which (more or less) understands gcc and g++ > syntax. Huh? GCC is perfectly available for Windows. <URL:http://www.mingw.org/>. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
