-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Alexey.Petruchik has submitted a cmake build file for libogg. https://github.com/xiph/ogg/pull/6 I'm curious how many people here would find this useful, particularly Visual Studio users. I don't object in principle, but I'm wary of adding yet another build description which would need to be maintained. -r -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVZQrRAAoJEEcAD3uxRB3vIhEH/RgpTsy/5n35Epx1+eemk/Qq mBo45eHanzjpB9ENKFA9IJG0Sy2V8KqtWAtHepUu710DZctNC0ckqqvmlA3SdYr6 aBzoauaq1RHn3XB1vG8pkGayMVfGByE5cly0V+AoDnXn59OzJ1QUgXilck4e5sBg Yb9lVIH6gMLic9XuOzP7bsQnrxieAHkznAyge1RbXzbB9tfZ3gzdBIalCa2Iy0YP ABAZ6+IngXgEwifTJK82beaIpzE8amp8JSPQ2XXsdTrBgp2+p8kYydZ0z2M8LP9E Kav6+4KVSgIl6Uc+8nLh1bItEQAEKt5NPRnh4/xQxDdqn8o+SUlGQ4XhR9iM+xo=Ku4z -----END PGP SIGNATURE-----
Yes please. CMake support is somehow mandatory for any C/C++ project nowadays. Death to autotools! But that's just my ignorance speaking :-) I have also commented on that pull request. Cheers, Cristian. On Wed, May 27, 2015 at 2:07 AM, Ralph Giles <giles at thaumas.net> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Alexey.Petruchik has submitted a cmake build file for libogg. > > https://github.com/xiph/ogg/pull/6 > > I'm curious how many people here would find this useful, particularly > Visual Studio users. I don't object in principle, but I'm wary of > adding yet another build description which would need to be maintained. > > -r > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJVZQrRAAoJEEcAD3uxRB3vIhEH/RgpTsy/5n35Epx1+eemk/Qq > mBo45eHanzjpB9ENKFA9IJG0Sy2V8KqtWAtHepUu710DZctNC0ckqqvmlA3SdYr6 > aBzoauaq1RHn3XB1vG8pkGayMVfGByE5cly0V+AoDnXn59OzJ1QUgXilck4e5sBg > Yb9lVIH6gMLic9XuOzP7bsQnrxieAHkznAyge1RbXzbB9tfZ3gzdBIalCa2Iy0YP > ABAZ6+IngXgEwifTJK82beaIpzE8amp8JSPQ2XXsdTrBgp2+p8kYydZ0z2M8LP9E > Kav6+4KVSgIl6Uc+8nLh1bItEQAEKt5NPRnh4/xQxDdqn8o+SUlGQ4XhR9iM+xo> =Ku4z > -----END PGP SIGNATURE----- >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/ogg-dev/attachments/20150527/ddce8354/attachment.htm
Cristian Adam wrote:> Yes please. CMake support is somehow mandatory for any C/C++ project > nowadays.This is objectively not true.> Death to autotools! But that's just my ignorance speaking :-)I hate autotools as much as the next guy, but I don't think you're going to supplant it, just because it embodies 20 years of deployment experience, experience which cuts in both directions: libogg has changed to deal with the crap that other systems do just as much as distributions, etc., have changed to deal with the crap that libogg does. CMake was presented as a solution to one particular problem: the fact that MSVC requires new project files in an incompatible format every time they release a new version. Let's start with solving just that problem, and see how that works out.
On 2015-05-26 11:31 PM, Cristian Adam wrote:> Yes please. CMake support is somehow mandatory for any C/C++ project > nowadays.Fascinating. Do the Visual Studio projects it generates know how to invoke cmake to update themselves?> Death to autotools! But that's just my ignorance speaking :-)I don't like autotools _or_ cmake. Fortunately, I'm not libogg's only user... I've merged Alexey's CMakeLists.txt. Let me know if you have any refinements. -r