On Fri, 12 Oct 2012 23:27:40 +0200, Peter Stuge said: >> On Mac at least, that's now 3 dependencies: >> - install Xcode >> - install homebrew >> - 'brew install' libtool >> >> vs >> >> - install Xcode >> - install CMake > >vs what is currently needed by tarball consumers > >- install Xcode
Which you could reduce to zero steps if you provided binaries. >The requirements for developers in a project usually doesn't matter >so much, because they tend to be smaller in numbers than the users >of the project. Optimize for the common case and all that. True. >CMake unfortunately doesn't affect only developers, it also means >that every user now needs CMake, where before they didn't. It's a >significant disadvantage. :\ You are contrasting "developers" and "users", yet what you call a "user" is someone who needs to compile source code! For a library like libusbx, the users _are_ developers. Do I assume correctly that on linux autotools is usually present, and CMake rarely is? If so, I can understand that requiring CMake would be annoying. From my perspective as a Mac user though, neither comes by default, so it's a wash. If libusbx provided binaries, "users" could just use them, and "developers" could handle building with whatever tool. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
