Jump to content



Recommended Posts




So far I've spent about a day setting everything up to build Cura 4.8.


I have followed the steps for native build of cura-build-environment which appears to work fine (no errors) and so I attempted the Ubuntu native cura-build, including the AppImage step which recommended to download a pre-built one.  I have done this, renamed it to appimagetool, saved it to $HOME/Applications and added that to my $PATH.  I can execute appimagetool.


Now, when I run cmake ..  I get the following:

-- Found Python3: /usr/bin/python3.8 (found version "3.8.5") found components: Interpreter
CMake Warning (dev) at /usr/local/lib/cmake/Arcus/ArcusConfig.cmake:30 (set):
  implicitly converting '' to 'STRING' type.
Call Stack (most recent call first):
  projects/CuraEngine.cmake:1 (find_package)
  CMakeLists.txt:106 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found Python3: /usr/bin/python3.8 (found suitable version "3.8.5", minimum required is "3.4") found components: Interpreter
CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
  cmake/FindAppImageKit.cmake:5 (find_package_handle_standard_args)
  packaging/python3.7/linux.cmake:2 (find_package)
  CMakeLists.txt:124 (include)

-- Configuring incomplete, errors occurred!


I have also copied the renamed appimagetool to /usr/bin - no joy.


I'm sorry if I have missed something basic, but I spent yesterday afternoon trying different things, including downloading different Git repos of AppImageKit, but all with the same result.


One thing I did was grep the build files for AppImageKit, and it appears that the filename needs to be "appimagetool.AppImage" - this is not mentioned in the instructions linked above - is this a documentation issue?


Once renamed the "APPIMAGEKIT_APPIMAGETOOL_EXECUTABLE" part of the error is no longer reported, but I still get the "APPIMAGEKIT_APPRUN_EXECUTABLE" error.


So, my question is:  What do I need to do for cmake to be able to locate and use AppImageKit, specifically AppRun?





  • Link to post
    Share on other sites


    I'm far from an expert on building Cura from scratch. Truth be told, I've never done so.


    As far as I know, the AppRun executable should be in the AppDir that has been created. If all else fails, you could try extracting the AppRun file from an official AppImage.

    Edited by ahoeben
    • Like 1
    Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
          • Like
        • 7 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
        • 0 replies
    • Create New...