Hi Hendrik, >>> since SVN r339, CMake is supported as build system. Please read the >>> INSTALL*.txt files before using this! >>> >>> I'd be glad if some could test this and tell me if the descriptions >>> are >>> understandable. >>> >>> @zany: if this works out, I would like to do additional cleanups, >>> like >>> moving the .pc.in files to lib/ and glib/. >>> >> >> are we talking about openobex here. Then there is no way this moves >> to >> CMake as build system. Using autoconf/automake is just fine. > > Yes, we are talking about openobex. And autoconf/automake/libtool is > "fine"[1] only on Linux/*BSD. What's your argument against CMake? Note > that the result after the configuration step is absolutely equal.
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. Regards Marcel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
