FreeCad

[bigpup]

Here is a applmage for Freecad
https://www.freecadweb.org/downloads.php (913 MB)

It is 64bit.
I tried it in Fossapup64 9.0.5
Seems to work OK.

It needs to have exec permissions to run.
After downloading.
Right click on it.
Select properties.
Give it exec permissions.

Left click on it to run.
It took about 7 to 10 seconds to startup. So do not think it is not working when you click on it.

NOTE:
I know nothing about using this.
I guess you can ask and maybe someone that does will answer.

[Vverve]

Thanks bigpup
Wow,freecad 19 appimage is now 800mb!!!(latest,not the quickpet ver:18)
but here;Experimental in-app updating is possible.
Tested 19.1 on fossapup64 .

[dancytron]

That link didn't work for me.

I downloaded it at https://www.freecadweb.org/downloads.php

edit: works in Debian Dog stretch, at least to open a sample file. Wouldn't run as root, had to use "run-as-user" (DD equivalent to run-as-spot).

Version FreeCAD_0.19-24276-Linux-Conda_glibc2.12-x86_64.AppImage

[gauravvermacse]

freecad is works at lightweight pc also, you can download the freecad again. Or you can try another [link removed by moderator to prevent spam] such as leocad, openscad etc.

[paulski]

Just had issues with Freecad 0.19 AppImage not liking being run as Root in Fatdog811.

Problem comes down to their new changes, that the FreeCAD team have decided to use the QTWEbengine instead of the Webkit in previous versions.

Fix is realatively easy.

1. Unpack the appimage
cd to the folder where the file is, ensure it is set to be executeable over permissions, and in a console enter:

Code: Select all

./FreeCAD_0.19.3-Linux-Conda_glibc2.12-x86_64.AppImage --appimage-extract

2. Browse the appimage. In the folder you should find "squashfs-root" - Right mouse button on it and "look inside"
3. At the top level folder is a file "AppRun" - edit it
4. At just about any line (I chose to add after line 9) add the line "export QTWEBENGINE_DISABLE_SANDBOX=1"
Here is a snippet from that file with my line added

Code: Select all

export FONTCONFIG_PATH=/etc/fonts
#Added by Paulski
export QTWEBENGINE_DISABLE_SANDBOX=1
# export QTWEBENGINEPROCESS_PATH=${HERE}/usr/libexec/QtWebEngineProcess line

Don't forget to save the file

5. Repackage the App Image using the App image tool (lost link for that but its easy enough to find)

Code: Select all

./appimagetool-x86_64.AppImage squashfs-root

You should have a new app image for FreeCAD that won't complain in the background that "Runing as root without --no-sandbox is not supported" and will finally work in most recent Puppies.

[Vverve]

Hi Fc users,
Oh ,yes ,almost forgot that freecad.appimage issue..

paulski,
Thank's ,that's a very simple solution!!!

Note to all:
The latest freecad daily found is 930Mb appimage.
Extracted ,its 3.1Gb, i mean, just to change 1 permission ,its a shame... ssd's lifetime speaking,
so,here with impup64 frugal/no swap, 8gb/ram + libreoffice.sfs+ browser ,it struggled to have enough space
eXtracting that huge appimage to ram.
Just a little reminder, have/free some ram,save the planet trash ¨system¨ from too many obsolete ssd..
or keep your good old spinning drives.
Of course its for non-dev like me..real woof dev/kernel compilers are use to deal with 10-15-20 Gb...

[Lekium]

I dont know how the guys behind Knoppix did it but I have their 4.7Gb live version running from a prendrive and it includes Freecad, OpenScad, Meshlab, Blender, Slic3r, etc and it runs in both 32bit and 64bit cpus. I have freecad in a BionicPup64 pendrive but I couldnt get it to work in BionicBeaver32.

[Vverve]

I dont know how the guys behind Knoppix did it .

How? Dont use portability of appimage..
let's have fun;
500mb puppy+
all those install from package manager,here from impup64,
760mb blender & dependencies+
700mb fc &119 dependencies
150mb of heavy browser
17mb of openscad
17mb of slic3r
200mb of extra
x1.7 (32+64 bits) no scientific proof,rough assumption here...
=4.5Gb
I guess there is no miracle !!

That was fun!!

feeling nostalgic? not at all

[Vverve]

This works too,
Create a script;
#!/bin/bash
export QTWEBENGINE_DISABLE_SANDBOX=1
# exec /path to/your/appimage ___in my case
exec /mnt/home/FreeCAD_weekly-builds-27078-Linux-Conda_glibc2.12-x86_64.AppImage

Name/save it whatever/where you like,make it executable(appimage too ,as usual).

No need to extract/repack...sweet..

[Vverve]

freecad ,appimage or not ?
as the stable version can be installed from puppy pkg manager from all woof-ce ubuntu/debian builds,
note that it's been a long time i tested how ppm perform at finding all dependencies needed ,
that the appimage is 900Mb +- , yes it could be update if extracted(+3Gb total (2.1Gb of libs to be ¨portable ¨ in all distros))/edit/repack ,
you see the pain of following the pace of it daily/weekly... in case you would like to test recent features/fixes ,
then installing from ppm all dependencies from your favorite puppy and ¨FC newest pkg¨ from
this daily ppa where we find all ¨main freecad &+¨ deb packages,well,the ubuntu ones , is a good alternative.

[Vverve]

Curious how ppm would perform at installing freecad 0.19 stable in impup64, buzzZzer ...no go, missing dependencies.
Hmm...will test some more puppys and edit this post...

[rottenMILKweiler84]

@bigpup I'm going to assume this wouldn't work well on a 32-bit system, NoblePup32, to be exact? And running on old hardware to boot

[mikewalsh]

@Vverve / all :-

Just re-read the thread this evening, and decided to try the AppImage-update function in the FreeCAD-portable. Apart from a slow start, the current build - released just 3 days ago; now @ v1.0.0 (at long last!) - downloaded itself nicely. Renamed the AppImage to just "FreeCAD64", deleted the old one, and edited the launcher to use the 'xdg-tweak' trick that MochiMoppel put me onto a couple of years back. Result?

No more "symlinking gymnastics", config stuff remains firmly within the portable directory.....and the whole thing is running very sweetly in my customized Tahrpup64; Xenialpup64's original k4.9.58, glibc upgraded to 2.28 from josejp2424's Busterpup64 of a few years back, and running the official nVidia drivers for my Asus GeForce GT 710.

NICE one. Oh; and with the update to v1.0.0, there's a BIG drop in size.....from a truly "porky" 940 some-odd MB, we're back down to a more "reasonable" 650 MB again!

Mike.