Thanks, no rush,but your FreeCAD's expert.
I also want to add some "Call for testing PY3", I will do this, but if you have some ideas I'm open. This is not my strong suit.
Code: Select all
#### Note on Python 3 Please test Python 3 (Conda) builds in your FreeCAD daily routine and [report issues](https://forum.freecadweb.org/viewtopic.php?f=10&t=12534). #### AppImage (delta) updates [Download](https://github.com/AppImage/AppImageUpdate/releases) AppImageUpdate (GUI or the command line version). To perform an update: ```bash # Using GUI chmod +x ./AppImageUpdate.AppImage ./AppImageUpdate.AppImage ./FreeCAD.AppImage # Command line chmod +x ./appimageupdatetool.AppImage ./appimageupdatetool.AppImage ./FreeCAD.AppImage ```
I forgot to mention I added this: https://github.com/FreeCAD/FreeCAD/rele ... g/0.18_pre
Sure. Update information can be added for the next stable release. And i guess documentation. If that is desired and the size isn't the problem. Best if we do all of this once FreeCAD 0.18 gets released? As likely still a few months until that happens.
This is what I am thinking too.
You've made much progress with this over this dev cycle. It's heavily used as evident in the forums, so its worth the effort. Thanks
Primarily to keep the package size as small as possible.
Well, damnsgrogan wrote: ↑Sat Oct 06, 2018 1:03 pmPrimarily to keep the package size as small as possible.
FreeCAD doesn't link directly to Calculix or GMesh for example, but rather calls the executable in a sub-process.
This means that the packages can be installed outside the AppImage. Then in FEM preferences the paths to the executables can be set.