What I was trying to do earlier was specifying too much on the command
line. Combined with confusion about what "/PATH/TO/HUGIN/SOURCES" meant.
I interpreted it to mean it needed to point to the /src directory, when
it really means the parent directory of /src.
Sometimes I find compilation instructions too complex for their own
good. I know, they have to be general enough to cover a lot of
situations, but sometimes I think they're too general, trying to cover
too many possible situations. ;)
Or they're too specific. I use Debian, not Ubuntu/Fedora/Redhat, so
detailed instructions on how to do it under those other distros don't
necessarily help. ;)
Either way, it beats the days when I had to use alien to convert an RPM
to a DEB because developers only developed for Redhat.
On make install vs make package then install, when I compiled in January
2022, I used the make package option and installed the resulting
package. This time I decided not to make the package. No particular
reason, just what I did this time.
I can see one benefit to making a package and keeping it around. If I
needed to uninstall and reinstall, being able to re-install using the
package would be faster. So I went back just now and made a package to
keep around just in case.
Thanks for the help and advice!
On 10/6/22 04:26, johnfi...@gmail.com
> How is what finally worked different from what earlier didn't work?
> For example, the instructions had /PATH/TO/HUGIN/SOURCES where your
> final working version had ..
> I assume.. is the path to hugin sources (from the place where you had