×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

I don't have Altair drivers from libindi_3rdparty package

  • Posts: 5
  • Thank you received: 0
Hello,
I installed libindi_3rdparty package from the AUR, everything is working perfectly, I have a long list of camera vendors in Ekos, but there's no Altair. I tried to find if Altair driver was installed and I couldn't find anything. Upon further investigation, I found that there's nothing about Altair drivers in CMakeLists.txt file in 3rdparty/ directory in the latest v1.7.5.tar.gz release from GitHub, so this is not an issue with AUR package. So could anyone at INDI please fix it? Thank you! :)
5 years 2 months ago #34704

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
I think it is currently on. If you run the 3rd party cmakelists, it should build indi-altaircam, as long as you already have libaltaircam built already.

In the current file on GIT: github.com/indilib/indi/blob/master/3rdparty/CMakeLists.txt

You see this? option(WITH_ALTAIRCAM "Install Altair Driver" On)

And then later this:

## ALTAIR
if (WITH_ALTAIRCAM)
find_package(ALTAIRCAM)
if (ALTAIRCAM_FOUND)
add_subdirectory(indi-altaircam)
else (ALTAIRCAM_FOUND)
add_subdirectory(libaltaircam)
SET(LIBRARIES_FOUND FALSE)
endif (ALTAIRCAM_FOUND)
endif (WITH_ALTAIRCAM)
5 years 2 months ago #34726

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
Oh, so I should build version from git rather than use latest release in "Releases" tab?
5 years 2 months ago #34727

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
Okay, I installed libaltaircam successfully, but I'm getting these errors when trying to install indi-altaircam:
indi/build/indi-altaircam on master 
➜ make
Scanning dependencies of target indi_altair_ccd
[ 50%] Building CXX object CMakeFiles/indi_altair_ccd.dir/indi_altair.cpp.o
In file included from /usr/include/c++/8.2.1/x86_64-pc-linux-gnu/bits/os_defines.h:39,
                 from /usr/include/c++/8.2.1/x86_64-pc-linux-gnu/bits/c++config.h:508,
                 from /usr/include/c++/8.2.1/bits/stl_algobase.h:59,
                 from /usr/include/c++/8.2.1/bits/stl_tree.h:63,
                 from /usr/include/c++/8.2.1/map:60,
                 from /home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.h:24,
                 from /home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:22:
/usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
 #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
    ^~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp: In member function ‘void ALTAIRCAM::eventPullCallBack(unsigned int)’:
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:22: error: ‘unique_lock’ is not a member of ‘std’
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                      ^~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:22: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:30:1:
+#include <mutex>
 
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:22:
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                      ^~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:39: error: ‘mutex’ is not a member of ‘std’
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                       ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:39: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:52: error: ‘ccdBufferLock’ was not declared in this scope
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                                    ^~~~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2025:46: error: ‘guard’ was not declared in this scope
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                              ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:22: error: ‘unique_lock’ is not a member of ‘std’
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                      ^~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:22: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:39: error: ‘mutex’ is not a member of ‘std’
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                       ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:39: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:52: error: ‘ccdBufferLock’ was not declared in this scope
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                                    ^~~~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2040:46: error: ‘guard’ was not declared in this scope
                 std::unique_lock<std::mutex> guard(ccdBufferLock);
                                              ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2054:30: error: ‘unique_lock’ is not a member of ‘std’
                         std::unique_lock<std::mutex> guard(ccdBufferLock);
                              ^~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2054:30: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2054:47: error: ‘mutex’ is not a member of ‘std’
                         std::unique_lock<std::mutex> guard(ccdBufferLock);
                                               ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2054:47: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:18: error: ‘unique_lock’ is not a member of ‘std’
             std::unique_lock<std::mutex> guard(ccdBufferLock);
                  ^~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:18: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:35: error: ‘mutex’ is not a member of ‘std’
             std::unique_lock<std::mutex> guard(ccdBufferLock);
                                   ^~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:35: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:48: error: ‘ccdBufferLock’ was not declared in this scope
             std::unique_lock<std::mutex> guard(ccdBufferLock);
                                                ^~~~~~~~~~~~~
/home/pawel/Desktop/indi/3rdparty/indi-altaircam/indi_altair.cpp:2086:42: error: ‘guard’ was not declared in this scope
             std::unique_lock<std::mutex> guard(ccdBufferLock);
                                          ^~~~~
make[2]: *** [CMakeFiles/indi_altair_ccd.dir/build.make:63: CMakeFiles/indi_altair_ccd.dir/indi_altair.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/indi_altair_ccd.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
5 years 2 months ago #34730

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
I typically built straight from GIT. Things change very quickly in INDI. Obviously the stable releases are probably more stable, but if you find that something isn't there, like a new feature, then you should use the latest version. Just don't rely on it in the field until you thoroughly test it inside.

As to the build errors, I didn't get any build errors 2 days ago, the last time I did it, but I built it on a Mac. Something could have changed in the code, I don't know.
5 years 2 months ago #34731

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
Thank you for help! :)
5 years 2 months ago #34733

Please Log in or Create an account to join the conversation.

Time to create page: 0.236 seconds