Thanks Amedee,
I've managed to successfully run Cura on my virtualenv by following the GOLD thread above. :-P
I will also try to package by downgrading what's listed there.
You've really saved me many hours ... and headaches!
Cheers
Thanks Amedee,
I've managed to successfully run Cura on my virtualenv by following the GOLD thread above. :-P
I will also try to package by downgrading what's listed there.
You've really saved me many hours ... and headaches!
Cheers
We didn't write the build steps for OSX, someone from the comunity did. We try to stay clear from developing on osX because they seem to hate developers.
A rant about operating system is not opportune and does not help anybody -- in particular this issue is more about a mess in the python bindings dependencies than anything else.
Let's continue to work on this as a community, making Cura a slicer of choice whatever the platform the end user wants to use.
Note that the above problem seems to relate to pyobjc, not to Cura.
I cannot really provide you with much assistance here. It works on our Mac build machine, not sure why. But as Nallath already pointed out (in a not so friendly way), developing on a Mac is tricky, we try to touch the build machine as little as possible to make sure the build environment does not break.
Recommended Posts
amedee 349
This is a problem with the version of the python packages you are using...
It is a nightmare to have a consistent set of packages -- look at http://umforum.ultimaker.com/index.php?/topic/7577-cura-mac-os-x-sources-compil/, I have something running fine on Maveriks (should work on the Lions a s well)
Link to post
Share on other sites