FreeCAD 32bit 18.4 not available

I have read around June somewhere that with a change of Qt5 FreeCAD is not being able to build on Tumbleweed for the foreseeable future.
For some time now there are builds for x86_64 distributed from the official repo.

However, the i586 version was never added. Why is that and will it be provided?

Unlikely, see change log note from February;

Tue Feb 12 21:10:12 UTC 2019 - Adrian Schröter <>

- enable FEM module
- disable builds for 32bit and s390x, test suite fails and it makes no
  sense to use FreeCAD on small systems or mainframes...

You could try branching and building yourself?

How come then FreeCAD 18.4 is available and running perfectly fine in 32bit on debian?

I have tried to build it myself, but failed due to various dependencies not available.

The statement “FreeCAD on small systems makes no sense” seems to be coming from a software devloper who doesn’t do 3D printing.

You would have to ask them, if they want to support it as well as all the underlying libraries, good for them (must be a nightmare security wise)…

Then you need to build those dependencies as well, which likely will take you down the rabbit hole…

Tumbleweed roles forward, at some point there will be fallout for older hardware…

Looks like FreeCAD tries to make it easy for openSUSE Users to compile themselves…

  1. Clone the source…
git clone
  1. Install dependencies
    You may need to modify the dependency list for 32-bit libraries instead, the official list looks like 64-bit packages. I’m guessing also if there was some reason to build with python 2 libraries, that’d be possible, too…
zypper in --no-recommends -t pattern devel_C_C++ devel_qt5zypper in libqt5-qtbase-devel libqt5-qtsvg-devel libqt5-qttools-devel boost-devel swig libboost_program_options-devel libboost_mpi_python3-devel libboost_system-devel libboost_program_options-devel libboost_regex-devel libboost_python3-devel libboost_thread-devel libboost_system-devel libboost_headers-devel libboost_graph-devel python3 python3-devel python3-matplotlib python3-matplotlib-qt5 python3-pyside2 python3-pyside2-devel python3-pivy gcc gcc-fortran cmake occt-devel libXi-devel opencv-devel libxerces-c-devel Coin-devel SoQt-devel freetype2-devel eigen3-devel libode6 vtk-devel libmed-devel hdf5-openmpi-devel openmpi2-devel netgen-devel freeglut-devel libspnav-devel f2c doxygen dos2unix glew-devel

They seem to recommend using QT Creator and the gdb debugger to build so that you can identify errors as you build… especially with so many modifications and possible unknowns that could happen, this may be necessary

zypper in libqt5-creator gdb
  1. Follow the instructions for building. If you decided to build using Qt Creator, follow those instructions. If you’re not using Qt Creator and building just for yourself, then I’d recommend the “In source” instructions which would generally mean that once you complete successfully, you’d just run it from within the same directory tree, you won’t delete your source. I’d also guess that would mean that to update your FreeCAD in the future, you’d just update your Github source (git update) and re-run your compile commands.

Before you do any of this, though…
I’d suggest you re-visit your decision to run 32-bit TW on your machine. Most hardware dated after 2003 and <definitely> all hardware after 2008 supports 64-bit although it might have originally been sold with a 32-bit OS on it. If your machine supports 64-bit, there really isn’t any reason to avoid doing so no matter the age of your hardware… The OS will simply manage your resources better and nowadays there’s a good chance your device drivers will work better, too. And, that is regardless how little RAM you have in your machine.

You may find that it’s just time to upgrade your machine to 64-bit as the better path than to run 32-bit software.

Also note that the FreeCAD project itself doesn’t distribute pre-built 32-bit versions, the AppImage release is only 64-bit. When you consider that along with the dependency package list which looks like it’s 64-bit, that strongly suggests that the upstream maintainers (FreeCAD itself) are the ones encouraging 64-bit only.


tsu2, thank you for the time to write your post. It was more than i hoped for. Pls ignore my following rant :slight_smile:

I used to be able to compile FreeCAD in the past without many problems.

But currently this is next to impossible or at least very time consuming.
Qt-Creator is just one dependency not available in Tumbleweed.

And i figured:

ok, they don’t provide a working 3D acceleration for old cards (amd/intel frequently broken), Cura, FreeCAD, lib-shiboken and related stuff, Qt-Creator for Tumbleweed 32bit anymore.

So it seems to really come to an end with Tumbleweed for 32bit; without software and libraries it makes no sense to use it.
I have switched a testing machine to debian and everything is there and works like it should and even the relevant packages are nearly up to date.

I know it is the nature of tumbleweed to be a rolling distribution. I liked it very much albeit being forced to use it if i wanted these machines to stay on openSUSE. But now you do an update and it will deinstall half of your software base. So as sad as it is, i have to leave openSUSE with about 10 machines working perfectly well until it was decided not to provide software anymore.

I just wanted to let everybody know that i’m about to leave openSUSE with my old machines, so you can’t claim not to know it, that someone left as you did before:

The decision to drop 32bit when Leap came out was made on the base: we checked our servers and 32bit clients access counts have dropped significantly. Well no wonder, since most of those old machines serve a dedicated purpose or they would have been gone to trash already. And by dedicated it most certainly means they do not connect to the internet, but are updated from a local repository mirror.

So good luck to openSUSE if it continues on its way to ignore their users. The result is very visible on distrowatch where the antiX distribution for old computers is already ranked 2 places above openSUSE.

The trouble is those ancient computers are slow, I can probably do more with a $35 RPI3… :wink: and it’s 64bit (or 32bit)…

Unfortunately Distrowatch relies on page hits nothing to do with actual downloads etc… so can be very skewed…

Likewise I can have multiple machines running from one download of the iso and updates (like I do with my SLE x86_64 and aarch64 machines), the only ones that can count are two tumbleweed x86_64 systems and a RPi3…

Took a look at the problems with Qt Creator…
Yes, it seems that no openSUSE build is available for TW (both 32bit and 64bit) (build failurs),
But there is good reason.

This is the Qt project on Github,

Note that the project only develops to debian systems, they may say that the app is cross platform, but they target on MSWindows, MacOS and Deb systems… Everyone else is excluded. When I do a general Internet search for anyone building to RPM systems, I see a few private efforts, but nothing organized. Whatever someone did to enable a 15.1 build must be remarkable.

So, armed with that information…
Best options for deploying QT Creator on Tumbleweed would likely be one of the many cross-platform distributables based on containers… For now I’d also exclude technologies like docker and lxc which target hard core developers and other technologists and focus mainly on those that target ordinary Users…

These are options I located that should deploy on TW…



I could not find a flatpack build at flathub.


It’s unmaintained on OBS by the looks, the only reason would be not up to date with the current release and built with QT5 since 4 is dead and buried…

I see a build is queued… but only for x86_64 which won’t help the @OP of this thread (He wants an i586).
Maybe a build just had to be activated?
Here’s hoping for a successful result with fingers crossed… But I still don’t see that a 32-bit version may ever have been set up.


A little more Qt Creator research…
Seems that the main project dropped 32bit downloads (and official support for 32-bit with version 5.6 on or about Feb 2016.
Starting then, any person who wants a 32bit version of Qt Creator has had to compile it himself.

The more I think about my AppImage and Snap recommendations, they may not work.
I’m thinking that the apps which would certainly be built to run in a 64bit kernel would probably have a problem running on a 32bit kernel.


AppImage is 64bit only. So this will not work on a 32bit system.

In case anyone else needs the latest FreeCAD running on TW 32bit, i have tested several viable methods:

  • use wine with FreeCAD 32bit for Windows
  • use debootstrap to install a debian chroot of any flavor up to sid and use their compiled 32bit FreeCAD
  • use a virtual machine with a windows 32bit guest and gpu acceleration