ooga Try: sudo eopkg it -c system.devel to install most common tools needed to compile source code. You may then have to install other needed dependencies probably listed on the BUILD.md file you're referring to (make sure to install the -devel packages).

      kyrios progress, although one more error

      CMake Error at /usr/share/cmake-3.20/Modules/FindPkgConfig.cmake:556 (message):

      A required package was not found
      Call Stack (most recent call first):
      /usr/share/cmake-3.20/Modules/FindPkgConfig.cmake:778 (_pkg_check_modules_internal)
      lib/libappimage/cmake/scripts.cmake:113 (pkg_check_modules)
      lib/libappimage/cmake/imported_dependencies.cmake:10 (import_pkgconfig_target)
      lib/libappimage/cmake/dependencies.cmake:7 (include)
      lib/libappimage/CMakeLists.txt:29 (include)

      -- Configuring incomplete, errors occurred!
      See also "/home/ooga/AppImageLauncher/build/CMakeFiles/CMakeOutput.log".
      See also "/home/ooga/AppImageLauncher/build/CMakeFiles/CMakeError.log".

          ooga The message says you're missing a dependency. You have to install the missing -devel package(s) or build them if they are not in the repository.

          Did you check the build instruction and make sure all the needed packages are installed ?

            jrsilvey that picture is exactly what I'm aspiring to, thank you. Also, we drink to Solus. I haven't been able to bork it up for a long time now either, and I have always found a way before🙂

              kyrios I did run "sudo eopkg it -c system.devel" and installed a lot of dependencies with no issues, but still something left

                  ooga Yes but you didn't check if all the dependencies listed on the BUILD.md file you mentioned are installed. The system.devel contains the commonly used packages but not everything that each and every application in the galaxy may require.

                  For example, in the dependencies list, I see cairo and librsvg and if I look at libcairo-devel and librsvg-devel, I see it is in programming.devel and not in system.devel so it is probably not installed on your computer. You have to check if the following dependencies are installer or not until you get all the required packages installed.

                  https://github.com/TheAssassin/AppImageLauncher/blob/master/BUILD.md#dependencies

                      ooga & kyrios

                      I would refer you to my previous post..

                      jrsilvey AppImageLauncher is a great tool to integrate AppImages into your desktop. It creates a folder called Applications in your /home folder and any AppImages you download or try to install will end up moved to that folder. Instead of marking the files as executable just make sure you download the files into the Applications folder and AppImageLauncher will handle everything else.

                      I recall being confused when I tried to install the AppImageLauncher. There are a ton of different file formats to choose from. The file you should be choosing is

                      appimagelauncher-lite-2.2.0-travis995-0f91801-x86_64.AppImage located on the AppImageLauncher releases page.

                      I personally use AppImageHub to get all of my AppImages and have found the selection to be stellar. I have a ton of AppImages and the AppImageLauncher handles everything exceptionally well.

                      Just run the AppImage of AppImageLauncher-Lite in the above link. No building from source or development commands needed.

                      The issues you are running into are exactly what happened to me. It is literally as simple as marking the AppImage as executable and then running it. The documentation about this is confusing so don't feel bad.. I went through the same issues as you are now experiencing my first time trying to integrate AppImages.

                            kyrios JoshStrobl @DataDrake

                            I am fully aware of the stance shared by the Solus development team about AppImages. As I understand your views on AppImages, they are simply binaries and need to be marked executable and so there is no need for any integration into the Solus system.

                            However @ooga ran into the same issues I experienced when it came to trying to install AppImageLauncher to integrate the package installer format. There is no need to to try and build anything from source if you just run the AppImage version of the AppImageLauncher-Lite. This third party software isn't exactly clear about that though.

                            Would it be possible to perhaps add a section to the Solus website Help Center about integrating AppImages into Solus OS?

                            If both @ooga and I went through the wrong set of steps to install this piece of software it is likely other people have as well. I would help write the steps down for you so we can prevent further issues and enhace user experience on the matter going forward.

                                  ooga did you mark the AppImage file as executable?

                                  • ooga replied to this.

                                      algent wow, look at that, much appreciated! and now I only have to find desktop files like you have in your other thread you linked previously.

                                          ooga Yes, just save them in one place. AppImageLauncher deamon will do all the job to manage the desktop files to add or remove them from Menu.

                                          • ooga replied to this.

                                              jrsilvey yes, but not with the original way with installing all the dependencies manually, the AppImageLauncher worked with little to no manual commands.

                                              algent gotcha, will do.

                                              thanks a lot for all the help