4 ms·
I don't trust "make uninstall" anyway. Instead, I usually put self-compiled packages into separate directories, such as: make install INSTALL_PREFIX=/opt/l
by vog 10y ago
I don't trust "make uninstall" anyway. Instead, I usually put self-compiled packages into separate directories, such as:
make install INSTALL_PREFIX=/opt/lzfse
or
make install INSTALL_PREFIX=$HOME/.../lzfse
Uninstalling is then as simple as:
rm -r /opt/lzfse
For convenience, I either add /opt/lzfse/bin to $PATH, or create a symlink from /opt/lzfse/bin/lzfse to /usr/bin/lzfse.
More generally, I believe that uninstalling, upgrading and related operations are the task of a package manager, not a build script.
- michel-slm 10y agoI do that, and then use GNU Stow to manage the symlinks. That way I only need to add a single directory to PATH and to library paths
- mschuster91 10y agoGood luck with getting pkg-config to recognize your include files automatically, for example. Or the good old "man" utility. Alternative: maintain a HUUUUUGE list of xPATH env variables, and update them every time you recompile something and change the directory in the process. Oh, and hope that other people's Makefiles are intelligent enough to not mess up shit (e.g. use headers from system, and library .so files from your own compile)...
- vog 10y agoIf you are alluding to cross-compiling, rest assured that I wrote my comment being fully aware of the plenty of pitfalls, which is why I started the MXE (mingw-cross-env) project some time ago: http://mxe.cc/ http://mxe.cc/
- mschuster91 10y agoCross-compiling is yet another pile of dungheap in addition to the dungheap I mentioned. I usually set up a Debian chroot with qemu and compile "natively" (e.g. for RPi). It's dog slow, yes, but at least it works reliably in contrast to cross compilation. The only way I ever got CC to work is with the buildroot toolchain, which has the downside that it isn't Debian.