FreeBSD Cura (or the fun building this thing)

[zBeeble 2]

So... I'm a fairly competent ports maintainer for FreeBSD.  I see that someone has already gotten the CuraEngine ported.  I thus have been working in the direction of getting the Cura graphical front end going.

 

So... is anyone else working on this?

 

It almost seems like the job of porting things written in python is made nearly impossible by their build systems.

 

I think I have all the requirements built... but I'm still getting rather dumb output from cmake.

 

Help?

[gr5 2,176]

There's a version that runs in ubuntu - it has (strange to me) extention ".AppImage".  Does that not work in FreeBSD?  I'm guessing not.

 

Well maybe @ghostkeeper can help you - maybe if you posted some specific issue(s) of things you have problems with?

[zBeeble 2]

Well... an appimage might run if I fired off a VM running linux.  The linux emulation tends to work fine for binaries that you can run, but the sheer volume of libraries this requires is unlikely to be less work to run under emulation.

 

Besides... its written primarily in Python.  The C++ part is already ported (and seems like it was easier to port).  I realize that portable software can be difficult to write... but we're dealing with the low-hanging fruit here --- it's written in python.

 

argh.  I suppose one big problem is that I'm not familliar with cmake and while cmake exists on FreeBSD ... whatever this cmake does is broken.  More tomorrow, maybe.

[ghostkeeper 105]

Honestly, I know very little of BSD-family operating systems.

 

While the front-end is written in Python and the back-end (and auxillary libraries) is written in portable C++, I suspect that the binaries for our libraries are not compiled with BSD in mind. I'd expect Qt to be the most difficult one to get right. Besides that there might be some libraries we depend on that could be missing. And some resource paths that we have hard-coded, such as the config path being ~/.config/cura.

 

In our code we've always been talking about "Windows, MacOS and Linux" as our supported platforms; never "Unix" or "BSD". You're the first person I know of that seems to have tried.

[zBeeble 2]

Qt is actually fine.  KDE runs well and I've used Qt in projects ... both in python and C++ on FreeBSD.

 

It seems the previous version of Cura was ported to BSD, but whoever did that has moved on.

 

[zBeeble 2]

OK.  I've beaten down a bunch of errors.  There's two things I can't get past.

 

If I checkout the git tree, and after making, there's no option to make install or run in place.

 

I have a different tree checked out that has a cura_app.py to try to run... but there I get:

 

[2:114:414]dgilbert@canoe:~/Cura-master> LD_LIBRARY_PATH=/usr/local/lib/gcc6:/lib:/usr/local/lib ./cura_app.py
[MainThread] cura.CrashHandler.show [36]: An uncaught exception has occurred!
[MainThread] cura.CrashHandler.show [39]: Traceback (most recent call last):
[MainThread] cura.CrashHandler.show [39]:   File "./cura_app.py", line 69, in <module>
[MainThread] cura.CrashHandler.show [39]:     app = cura.CuraApplication.CuraApplication.getInstance()
[MainThread] cura.CrashHandler.show [39]:   File "/usr/local/lib/python3.6/site-packages/UM/Application.py", line 340, in getInstance
[MainThread] cura.CrashHandler.show [39]:     Application._instance = cls(**kwargs)
[MainThread] cura.CrashHandler.show [39]:   File "/home/dgilbert/Cura-master/cura/CuraApplication.py", line 154, in __init__
[MainThread] cura.CrashHandler.show [39]:     ContainerRegistry.getInstance().addResourceType(self.ResourceTypes.QualityInstanceContainer)
[MainThread] cura.CrashHandler.show [39]: TypeError: addResourceType() missing 1 required positional argument: 'container_type'

 

ideas?

[ghostkeeper 105]

8 hours ago, zBeeble said:

I have a different tree checked out that has a cura_app.py to try to run... but there I get:

 

[2:114:414]dgilbert@canoe:~/Cura-master> LD_LIBRARY_PATH=/usr/local/lib/gcc6:/lib:/usr/local/lib ./cura_app.py
[MainThread] cura.CrashHandler.show [36]: An uncaught exception has occurred!
[MainThread] cura.CrashHandler.show [39]: Traceback (most recent call last):
[MainThread] cura.CrashHandler.show [39]:   File "./cura_app.py", line 69, in <module>
[MainThread] cura.CrashHandler.show [39]:     app = cura.CuraApplication.CuraApplication.getInstance()
[MainThread] cura.CrashHandler.show [39]:   File "/usr/local/lib/python3.6/site-packages/UM/Application.py", line 340, in getInstance
[MainThread] cura.CrashHandler.show [39]:     Application._instance = cls(**kwargs)
[MainThread] cura.CrashHandler.show [39]:   File "/home/dgilbert/Cura-master/cura/CuraApplication.py", line 154, in __init__
[MainThread] cura.CrashHandler.show [39]:     ContainerRegistry.getInstance().addResourceType(self.ResourceTypes.QualityInstanceContainer)
[MainThread] cura.CrashHandler.show [39]: TypeError: addResourceType() missing 1 required positional argument: 'container_type'

 

ideas?

To me it looks like the Uranium checkout is more modern than your Cura checkout.

 

You're getting an error because the Uranium function addResourceType() requires two arguments:

def addResourceType(self, resource_type: int, container_type: str) -> None:

In the current Cura front-end code, our call to this function is a little different from what you seem to have:

ContainerRegistry.getInstance().addResourceType(self.ResourceTypes.QualityInstanceContainer, "quality")

So maybe update the Cura repository? Though the Cura repository must be pretty old to not have that container_type parameter.