-
Notifications
You must be signed in to change notification settings - Fork 53
How to install CreawsomeMod on Cura for Linux? #27
Comments
I don't know about the AppImage as I don't use them but I installed cura through the repos on arch. my method was this: Install cura Find where cura resources were kept backup current resources folder extract zip and copy resources
obviously your mileage might vary. |
For an AppImage, please see #9 (comment). |
@Roxsen I am running Arch Linux as well, and did the same steps as you described. Those are the correct steps. |
@trouch did you test the AppImage? A build for testing is available at https://github.com/probonopd/CreawsomeMod.AppImage/releases/tag/continuous Credits go to @TheAssassin for the bunch of the work. Is there still something to be done, hence you added "good first issue"? |
The instructions just the other day May 28 2019 on youtube < https://youtu.be/mOn-VNqg2ac> https://github.com/trouch/CreawsomeMod/releases/download/20190527-0.3.0/CreawsomeMod-Beta3.zip So that's what I did here with Linux Manjaro. It's working fantastic. My prints are absolutely amazing. Install cura Find where cura resources were kept backup current resources folder extract zip and copy resources
**Open up both file locations as ROOT. Go Copy (as Thunar Root in the right click menu) in the unzipped Downloads Folder and open up the extracted unzipped CreawsomeMod folder and drag that "RESOURCES" file into /usr/share/cura file location. You need to be in Root in both files... put the "RESOURCES" file... right beside the file named "resources_backup" **Done. |
@stelgenhof glad my instructions helped. |
The AppImage should remove the need for those manual steps. |
@probonopd you are right they would remove the need for manual steps but not everyone likes AppImages, I know I don't. but thats the beauty of open source and Linux, do things the way YOU like. :) |
Merging this mods enhancements into Cura itself removes the need for any manual steps, forks, offbeat hacks :) |
@stelgenhof there is that! 👍 |
I put together some instructions on rebundling the Ultimaker Cura AppImage with Creawesome on Linux: https://www.foell.org/justin/cura-creawesome-mod-for-linux/ |
I didn't realize... I'll update my post with a link to your work (and fork). |
If this project here likes my work I can send a pull request to have it integrated into this repository here, I'd actually prefer that over having to maintain a fork of the fork ;-) |
Thanks everyone for your contributions to make it work on Linux. Feel free to submit a PR I could try in an Ubuntu VM; but I'll be honest this is not a priority. |
Indeed, I think that would be preferred by everyone! 👍 |
The official Cura AppImage keeps configuration files in
Full disclaimer, I have yet to actually print anything with it, but the mod is working. Here's some quick screenshots. FWIW I'm on Debian testing, but that should be irrelevant with AppImages. |
@WolfgangAxel why did you not just use the CreawsomeMod AppImage? No need to copy nor rename anything... https://github.com/probonopd/CreawsomeMod.AppImage/releases |
@probonopd I didn't use the AppImage because I didn't feel it was necessary. Your AppImage is a valid and functional way to have the mod pre-installed, but I didn't see a reason why GNU/Linux needed its own unique method of installation. I knew Yes, with your AppImage there's no need to copy or rename anything, but with using the method I used there's no need to trust another entity to extract, modify, rebuild, and reupload an entire AppImage after each update this way, even if it is automated. I don't mean to sound rude. Both methods are functional and viable. One of them has 0 user input, the other doesn't require a 3rd party to modify 1st party files and redistribute them. Both have clear advantages and disadvantages related to convenience and security. It comes down to user preference, much in the same way that there are people who prefer to download prebuilt binaries and people who prefer compiling from source. If nothing else, we now have multiple options for installation, which was the whole reason I made the comment in the first place. I wasn't trying to undermine anything you had done, I just wanted to notify the developers that the AppImage Cura builds don't have to change the method of installing the mod compared to the Windows executable builds or the Mac app builds. Slight grammar edits |
@WolfgangAxel thanks for finding a manual method for Linux without needing root/Sudo :) |
@Roxsen just for completeness, the CreawsomeMod AppImage also does not need root/sudo... |
@probonopd as it should be for AppImage but you still have to deal with a 3rd party like @WolfgangAxel pointed out. |
Honestly I have run appimage on Linux Mint and had no problems and I was running Linux Manjaro which is completely foreign to me and I was just trying to make the darn thing work. I downloaded Cura 4.1 which crashed on Windows 10 for me...but I also just found out my Hexcore Intel Cpu, one of the cores is causing program crashes. So I might try 4.1 Cura. I turned off the core. Computer Hardware. Never buy a refurbished system. ugh. |
Glad to hear! |
After Using Linux Mint for a couple years and switching to Manjaro and having to learn terminal commands in Manjaro it was like learning French in German 😆 |
thanks everyone, I guess you can now rely on Cura upstream ! |
I'm not deeply familiar with Linux packaging systems. Cura is supplied as an AppImage. I cannot edit it directly. But I can extract the contents of the image into a folder, replace resource folder and make AppImage with https://github.com/AppImage/AppImageKit
But after I create a modified AppImage file it won't run cura. It just does nothing. No error or anything.
Any ideas what else I can try to mod cura for linux?
The text was updated successfully, but these errors were encountered: