Gour wrote: > On Tue, 22 Feb 2011 14:10:59 +0100 > Jens Mueller <[email protected]> wrote: > > > Hmm. I do it like this. > > Download CMake from the official site and install it to > > /path/to/myhome/local. Then I set PATH and LD_LIBRARY_PATH as needed. > > And if I configure CMakeD using my cmake it will install the files to > > /path/to/myhome/local/where/cmake/puts/its/files. > > I've asked on #cmake about the possibility to include CMakedD in the > official release...
Thank you for asking. > Here are some tips I got: > > * "well it needs to be cleaned up more" Definitely. > * "as I said before the D support is not in a state that it can be accepted" I heard that. CMakeD had so many maintainers in such a short time. I think they already asked for it a while ago. > * "you need to create a git branch add it" Minor problem. I prefer git. > * "compile cmake and it needs to pass ctest -R ModuleNotices -V...and > other stuff" I do not know about these internals. > I hope it helps and can be tailored for inclusion into release. I mainly push it as far as I need it because writing CMake code is no fun for me (and I do it in my free time). Further I have the impression that nobody really cares. I mean there _many_ viable ways to have better configuration/build support for D. Jens
