Ah, no problem, this does not sound silly at all. Regardless of the fact that libindi is very well designed and compiles rather well, the whole process is all but trivial for people who do not work with C++ on a regular basis.

First of all, you should follow the instructions in Jasem's forum post "HOWTO: Building latest libindi & Ekos", paragraph 3, "Building INDI from Source
". If you use Raspbian on your PI, the described steps should work without problems (at least they did for me). As a first test, I would recommend to compile the sources without the Starsense patch, just to make sure that the toolchain and the whole compilation process works flawlessly. For this purpose, simply type "sudo make" rather than "sudo make install" for this purpose.

If compilation works well, as a next step, you can apply the Starsense patch. To do this, enter the libindi directory created when downloading the sources via git, copy the patch to the same directory, and then type

patch -p1 <celestrongps_starsense.diff.txt

You should get then the following three messages:

patching file libindi/drivers/telescope/celestrondriver.cpp
patching file libindi/drivers/telescope/celestrondriver.h
patching file libindi/drivers/telescope/celestrongps.cpp

After this, you are ready to recompile the modified sources. To do this, and in the same step install the modified indi drivers use the command "sudo make install" this time.

If everything has worked correctly, you should now have a modified version of the celestrongps driver on your PI.

If the hole process sounds too complicated, maybe you kindly may ask Jasem, whether he could include the patch in his nightly builds. Since the patch is able to detect the Starsense controller and distinguishes between standard Nexstar controllers and Starsense, it should also be safe for all non-Starsense users. At least, I tested it with my AVX Nexstar+ controller and it worked flawlessly.

Read More...