Jump to content

Trouble building Cura 5 on Arch Linux


Nirnex

Recommended Posts

Posted (edited) · Trouble building Cura 5 on Arch Linux

I am attempting to build Cura 5 on my Arch Linux PC in an attempt to get past the OpenGL issue I'm experiencing. I am using the cura-build-environment repo and have an error from cmake while building the engine. 

In file included from /home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/ArcusCommunication.cpp:12:
/home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/Listener.h:23:23: error: ‘Arcus::SocketState’ is not a type
23 |     void stateChanged(Arcus::SocketState) override;
|                       ^~~~~
/home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/Listener.h:23:10: error: ‘void cura::Listener::stateChanged(int)’ marked ‘override’, but does not override
23 |     void stateChanged(Arcus::SocketState) override;
|          ^~~~~~~~~~~~
/home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/ArcusCommunication.cpp: In member function ‘void cura::ArcusCommunication::connect(const std::string&, uint16_t)’:
/home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/ArcusCommunication.cpp:296:43: error: invalid new-expression of abstract class type ‘cura::Listener’
296 |     private_data->socket->addListener(new Listener);
|                                           ^~~~~~~~
/home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/Listener.h:17:7: note:   because the following virtual functions are pure within ‘cura::Listener’:
17 | class Listener : public Arcus::SocketListener
|       ^~~~~~~~
In file included from /home/pat/cura-build-environment/build/CuraEngine-prefix/src/CuraEngine/src/communication/Listener.h:8:
/usr/include/Arcus/SocketListener.h:60:22: note:     ‘virtual void Arcus::SocketListener::stateChanged(Arcus::SocketState::SocketState)’
60 |         virtual void stateChanged(SocketState::SocketState newState) = 0;
|                      ^~~~~~~~~~~~
make[5]: *** [CMakeFiles/_CuraEngine.dir/build.make:742: CMakeFiles/_CuraEngine.dir/src/communication/ArcusCommunication.cpp.o] Error 1
make[4]: *** [CMakeFiles/Makefile2:85: CMakeFiles/_CuraEngine.dir/all] Error 2
make[3]: *** [Makefile:156: all] Error 2
make[2]: *** [CMakeFiles/CuraEngine.dir/build.make:89: CuraEngine-prefix/src/CuraEngine-stamp/CuraEngine-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:358: CMakeFiles/CuraEngine.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

Anything that can help me get past this and to a successful build is very appreciated. 

Edited by Nirnex
  • 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
        • 18 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.
          • Like
        • 0 replies
    ×
    ×
    • Create New...