From: Hendrik S. <po...@he...> - 2008-05-18 11:55:07
|
Marcel Holtmann schrieb: > it is the fact that I don't do CMake. There is no need to move a > project to CMake that has perfect autoconf/automake setup. Doing CMake > means most of the times that the maintainer has no clue about autoconf/ > automake and is simply lazy. For me m4 is not some foreign concept and > so OpenOBEX will stay this way. > > Also since when are we using a Subversion repository. I never switched > to it and this means that the CVS on Sourceforge is still the main > repository. I will move it to using git actually once we have switched > BlueZ over to use git. > Automake only works with GNU make, nothing else. And far from being called perfect (no solution is that currently) unless you deny all the criticism about it. But thanks for calling me clueless and lazy :-( "Doing CMake" in my case means being able to use cl+nmake from the same configuration files that work with gcc+gmake. I have a description at hand that uses the latter solution on Win32 (including mingw + msys + lots of other stuff to get it to work to some degree) but using ./configure, there, is rather a PITA then a good solution (if you ever used that you would know that). I have nothing against moving to git (except that it pins you to the presence of /bin/sh and thus to MSys or Cygwin on win32). It does not even conflict with using CMake. Just as it is possible to let the current autoconf/automake files coexist with the CMake files. You maintain the one, me the other? Sounds ok to me. HS |