On Sat, 2009-05-02 at 10:02 +0200, Øyvind Harboe wrote: > So it has come to pass: CMake can do stuff that automake can not > do. > > This is what we feared :-) > > Should we embrace CMake as providing features that automake doesn't > do or should we insist that automake is updated?
I would say we commit CMake but keep autotools for now. I will update the autotools scripts to keep up with Dick, and he has show that he can keep up with us just fine. We do need to work out some remaining issues regarding config.h compatibility (raised earlier by Michael Bruck). > Personally I don't need those new features, but if you dig to the > depths of the mailing lists, they have been requested over time... > > At this point I'm not for or against CMake, I'm just trying to figure > out what the community wants. We will not really know what the community wants unless we commit it and find out. Otherwise, only those that apply patches on this list will be testing it and they are not the community; the community uses whatever the maintainers bless by committing to the repository. Selection bias. At the moment, however, Dick needs to address larger issues than CMake, having repeatedly threatened to fork the project. I will be reluctant to see CMake support committed until he comes clean on those things he thinks we are doing so wrong as to deserve such a fate. If we can work through this current rough spot, I am all for committing this patch. Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
