If the .dylib ID is not written with @rpath in the CMakeLists.txt of the INDI 3rd party driver, it causes FATAL_ERROR and cmake stops.
Someone needs to ask the vendors to fix it or change it with the tools provided with Xcode.
Otherwise, we will not be able to build INDI 3rd party drivers for MacOSす?
I would like to know what the future plan is.
The timestanp() function was changed to indi_timestamp() in indi branch stable-2.0.0 #1837.
kstars was also changed to call indi_timestamp() to match this change.
Until this version of kstars is released, I will define a timestamp function in my personal indi to get by.
I want to download KStars available on the latest INDI for use with Raspi.
I got indi and indi-3rdparty from GitHub on StellarMate OS, built and installed them, but Kstars would not boot.
The indi and some built indi-3rdparty drivers work and I can use them from KStars 3.6.3 on my PC.
The following KStars are currently installed on Raspi.
kstars-bleeding,now 6:3.6.3-stable~202302081248 arm64
$ kstars kstars: symbol lookup error: kstars: undefined symbol: timestamp
[Inferior 1 (process 47146) exited with code 0177]
Thanks for pointing that out.
I had not seen that article.
Yesterday I reported this matter to BTS at KStars. It appears that the source has already been corrected.
In the Capture Module of Ekos, I have specified _%s3 for the format of the sequence number of the filename, but the sequence number of all files is 001.
Kstars is 3.6.3 Build 2023-02-03T15:32:48Z for Windows.
I understand what Tips is trying to explain, but it is not direct and difficult to understand.
"Upload" is from the driver's perspective and not primarily about the user experience of using Ekos.
It should have been written like your first Tips description.
The description in this tooltip does not read "images are stored without going through the network where the indi driver is running," which is the problem in the first place.
I read the source code.
In the member function CCD::ExposureCompletePrivate of indiccd.cpp, there is code to save image data to the terminal where the indi ccd driver is running in case of Save Remotely.
If KStars is running on Windows and indi ccd driver is running on Raspi, indi ccd driver saves image data directly to Raspi in Save Remotely. The image data does not go through the network.
I will now comment on the ARTICLE of 2023/01/05.
Can you give me a direct URL to the forum?
I could not find the location of the forum from the given page.