Hacker News Reader

Comment by tomjakubowski | Hacker News Reader

If you squint, `cmake ..` looks like `./configure`. From there, you `make` and `make install`.

Part of the issue is also the lack of standardized flags. I will remember "./configure --prefix=/opt/foo" until the day I die, but "cmake -DCMAKE_INSTALL_PREFIX=/opt/foo" is something I have to look up every time (like I did just now to type it here).

That could be solved by a "configure" script that translates its arguments to ones that cmake will understand. And it seems it's such a good idea that someone has already made one: https://github.com/Richard-W/cmake-configure-wrapper

You can run ccmake or cmake-gui to inspect and change the configure options interactively (either in the terminal via ccmake, or in a "proper" UI application via cmake-gui).

You need CMake installed on your system to do "cmake ..". You don't need autotools installed on your system to do "./configure".

And then it fails because you don't have "make" or a compiler installed. Build dependencies aren't an issue as long as they are reasonably standard and easy to install.

Yes, you need autogen.sh.

You don't need to run autogen.sh. The maintainer can run that ahead of time when they make the tarball.

Depends on the system. If it was old, or the release date was a while back, you might need to do it anyway.

Many Linux distributions do it as a matter of course to ensure it's actually possible to regenerate and that it's up to date. At that point, you start to question the necessity of embedding it in the first place given that its primary consumers don't care.

Reply on news.ycombinator.com