I built everything on Debian 10 about a week ago using the latest stable tagged branches from each repo. Should you choose to do it manually rather than via the script above the main issue is installing all the dependencies you need Assuming you already know how to use git that is. If not, have a read about how to checkout a repo and switch to a named/tagged branch and you'll be all set.

If it's of any help, here's what I built and iirc the order I did it in:

• IndiLib "v1.9.0" (and 3rd party + MUPAstroCAT)
• StellarSolver "1.5"
• KStars "stable-3.5.3"
• PHD2 (v2.6.9)

One tip is to first install "GNU Stow". Then for each of the above items when you run ccmake, for example with indilib, change the install prefix to "/usr/local/stow/indilib-v1.9.0" then configure/make/make install as normal. You can then as root cd into /usr/local/stow and "activate" the indilib install with

  stow indilib-v1.9.0

now make/install/activate the indilib 3rd party, then stellar solver and so on.

The beauty of this is, when a new release of any of the software comes out or you want to test the develop version, you build it as normal but set a different install prefix "indilib-dev" or "indilib-v1.10.0" etc and then cd into /usr/local/stow and deactivate the old version, activate the new.

  stow -D indilib-v1.9.0
  stow indilib-dev

That way if in an imaging session you encounter new bugs, you can simply stow -D indilib/kstars/stellar/phd2 and stow the last version you know worked fine. Takes a few minutes and makes experimenting with new versions less risky

Also fwiw I had to build PHD2 with USE_SYSTEM_* OFF. I'm not sure which lib it was, but it didn't play nicely with the latest system versions and would fail to connect to my equipment via indi.
 

Read More...