Jasem,
I have built INDI from source, as per instructions (ARMHF Linux).
There is no instruction I can find on how to run kstars.
As a much older version of kstars came with the OS, typing 'kstars' runs the old version.
Installing PHD2 you run ./phd2 from the directory but what is the equivalent for INDI?

The first link contains all the instructions for building KStars as well. What's the problem exactly?

The problem is not with the build.

I just don't know how to run kstars after the build.

After you run sudo make install, the new kstars should be installed to /usr/bin and so when you type kstars, it should launch the one you just installed. If not, you have another KStars lurking elsewhere in your system. Type which kstars to find out where it is running from.

Jasem,

Thanks, I can now see that there must be an issue with the install not overwriting the older copy.

I'll rename it and try again.

Regards

Paul

Jasem,

I've tried again but it still isn't adding an executable to that directory and I cannot find any other occurance.

There do not seem to be any errors.

kstars is now okay, I wasn't thinking clearly - I bet you hear that all the time
I needed to build kstars and not just indi.

Now kstars is running fine but no Ekos options appear.

Do I need to rebuild Ekos after building Kstars?

phomer60,

What are you building kstars on?

Ekos is built as part of kstars, you don't have to build it after you build kstars.

If I have an old version of kstars from the distribution I am using I unistall it first using
the systems package manager.

Follow the instructions Instructions
to build indi on the system first, then build kstars.
Look for any errors in the kstars build with respect to things missing.

If it builds, run it with kstars at a promt and look at the help window to ensure it is the version you just built.

The Ekos icon is the little observatory on the right of the icons.
If it is not there ensure that you check that Settings -> Toolbars Show-> Indi toolbar is ticked.

Clear skys,

I built INDI first and the Kstars.

In the Kstars configure option under FITS, it shows Xplanet? but no INDI or Ekos. Settings, Toolbars Shown shows INDI and Telescope Toolbars are both ticked but nothing appears in the toolbar.

It is definately running the correct version.

I have not tried to unistall any previous version but I did rename the original executable and it is not running.

Thanks for the great instructions. I was able to fully compile and run indi/kstars/ekos using your Building INDI from Source link above. I compiled it on a Raspberry Pi running Ubuntu 16.04, and ran it on that platform as well. There were a few minor things to figure out, mostly related to compiling 3rdParty, but it worked!

My question is this: I assume what I've compiled and am running is HEAD at the time I did the git clone. I'd rather compile/run/experiment-with a more stable version. I assume there's a way e.g. to get git to clone a tag related to, say, the recent version 3.0 of this software, but I could not find the tags for that. (e.g. tried 'git tag -l' and given the tags, looked at the dates with 'git show TAG' but there we no tags dated around the end of 2018, in fact nothing past the summer). I'm obviously not that facile with git. What commands would I run to get and compile the source for a stable release?

Thanks,
Hy

If you go here: github.com/indilib/indi

Click on "master" then switch to tags and you'll see all the project tags.

Hi, I said I would leave some feed back as to why I struggled getting a development environment working, so here goes. (Spolier: Use Kubuntu 16.04 and don't upgrade!)

Background: I installed Indi, Kstar and Ekos on a raspberry Pi, and found all my equipment was supported, except my focuser (MyFocuserPro2). A bit more research showed that someone was maybe looking at developing one, but no feedback on it in a very long time, so I decided to create a simple driver myself. I have c and cpp experience and felt comfortable giving it ago. Unfortunately the bulk of my OS experience is Windows, with a little Linux thrown in and no GIT experience, so a very steep learning curve.

I have managed to cobble together a development environment, following the getting started instructions, but fell foul of the statement "Ubuntu 16.04 or newer ONLY ", as I upgraded to 18.04 (this was a mistake). It built fine, but I wanted to develop, so found some more instructions "Setting development Environment". 18.04 is newer that 16.04, but for the life of me I could not get debugging to work using 18.04 and I believe the main reason being that "kdesudo" was removed. I had no clue how to resolve the issue, still don't. I eventually realised that I may as well just stay with 16.04, and everything worked fine.

I have successfully written a driver, in debug, but now realise that GIT is going to be my problem.

I have created/modified 3 files mydriver.cpp mydriver.h and cmakelist(?). Now what?

Should my driver be in the main project or third party? It does not contain any external references and I don't know what the release cycle of Indi is, so have no opinion either way? So which should I choose as deafult. I have also been reading instructions about thir party drivers that state I need an xml file, really? What for? I checked out the developer examples, but the bit that is missing for me is how to use GIT.

How do I check out my own copy of the project, and check changes back in, or just treat it as a scratch pad or share it for others to test my code? I could go away and try to find the answers to all these questions, and the ones I don't know yet, but the chances are that will take longer that developing the driver!!. I am sure I am not the only person that has stumbled at this point, or maybe some people just havent started because of the lack of understanding of GIT.

As I am writing this more and more questions pop into my head. (Someone mentioned a Pull request, is there a corresponding Push request (are my changes Pulls or Pushes, pushes would make sense to me, is there a check list before submitting a change? Who reviews changes???))

Anyway, is their an idiots (me ) guide to GIT for this project that maybe I have overlooked?

TIA.

Update: I did g and find some primers and found this very useful Git and Github: A Beginner’s Guide for Complete Newbies

Updated Update: Just came across exactly what I was looking for How to contribute to the Indi project (Think this should be linked in the getting started section ( I realise it's way past getting started, but reference to complete cycle for development in one place would be useful)).