Maybe. But maybe they did nothing because there was no ./configure script and you had to use another tool, e. g. one of that I mentioned, so you need to learn another shit.
BTW installing anything from source like this is the right way only in (B)LFS.
But you definitely don’t need to learn this if you are a developer and starting a new project in 2024. You can use cmake or write plain makefiles, even shell scripts if you want, but as you value life or your reason keep away from the autotools. It is a nightmare to debug thousands lines of scripts they generate and put into your source tree.
Maybe. But maybe they did nothing because there was no
./configurescript and you had to use another tool, e. g. one of that I mentioned, so you need to learn another shit.BTW installing anything from source like this is the right way only in (B)LFS.
But you definitely don’t need to learn this if you are a developer and starting a new project in 2024. You can use cmake or write plain makefiles, even shell scripts if you want, but as you value life or your reason keep away from the autotools. It is a nightmare to debug thousands lines of scripts they generate and put into your source tree.
You assume everyone has root.
On a system I don’t administer, I can compile and install software in my home directory (or shared directories that I have write access) by using:
./configure --PREFIX=/home/myuser/software/
make # to compile
make install #without sudo, to install to ~/software/bin
So when you say “only in (B)LFS”, you’re overlooking a VERY common use case - especially in HPC and other systems NOT running on my desk/lap.