Hi everyone
So I just built a version of kstars from git and want to test it but keep my working version in /usr/bin
I do not use sudo make install
Is it correct to assume that running the newly built kstars from the build/kstars/kstars folder gives me the new version only?
TIA and clear skies,
Steve

Yes. Running kstars/kstars from the build directory (on linux) should run the new binary.
It is different on the mac (kstars/kstars.app/Contents/MacOS/kstars) and I'm not familiar with Windows.

Hy

Thanks for the prompt reply. That's good to know.
I wonder if there's an easy way to do the same for INDI? I can't see a way of being able to call an INDI binary (e.g. indi-asi) in the indi build directory from EKOS...

Steve,

I have never developed for Indi, but there's this reference set of pages: www.indilib.org/develop/developer-manual.html.

That said, I took a quick shot and tried this in my binary directory on a mac

cd PATH_TO_ALL_MY_INDI_BINARIES
./indiserver -v ./indi_simulator_ccd

and it did start. I did't try to do anything, but, give this, it looks like you can manually start the indiserver binary from wherever you compile that binary, and for the indiserver's args specify the full path to any/all drivers you want to test. Then you could configure KStars to use the existing indiserver instead of starting its own.

Hy

Yes, OK, got it.
So, now with the indi server already running, I need to disable ekos trying to connect again. I'm sure I've seen an option for that somewhere...
Cheers

Yes, I think when you start up Ekos or KStars, it will notice there's already an indiserver running, and ask you if you want to use that one that's already running, or if you want KStars to kill it and start a new one.
As I said, I've never debugged that way, but that's what I'd try.
Hy

I *think* you could also configure a "remote" indiserver on host 127.0.0.1 and instruct KStars to connect to this "remote" host. Should avoid the error message.