Please take a look at: https://aur.archlinux.org/packages/freecad/ for building process. FreeCAD doesn't build with autotools anymore.
Search Criteria
Package Details: freecad-git 0.22.0.36999.ged77603af9-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/freecad-git.git (read-only, click to copy) |
---|---|
Package Base: | freecad-git |
Description: | A general purpose 3D CAD modeler - git checkout |
Upstream URL: | https://www.freecad.org/ |
Licenses: | LGPL |
Conflicts: | freecad, freecad-appimage, freecad-appimage-git |
Provides: | freecad |
Submitter: | gborzi |
Maintainer: | greyltc (adrianinsaval) |
Last Packager: | adrianinsaval |
Votes: | 107 |
Popularity: | 1.70 |
First Submitted: | 2012-03-03 13:46 (UTC) |
Last Updated: | 2024-04-30 00:29 (UTC) |
Dependencies (39)
- boost-libs
- coin (coin-gitAUR)
- fmt (fmt-gitAUR)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- medAUR (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR)
- openmpi (openmpi-gitAUR)
- pyside6
- pyside6-tools
- python-matplotlib (python-matplotlib-gitAUR)
- python-packaging
- python-pivy
- python-ply
- python-yaml (python-yaml-gitAUR)
- qt6-5compat
- qt6-base (qt6-base-gitAUR, qt6-base-headlessAUR)
- qt6-svg
- qt6-tools
- shared-mime-info
- verdict
- vtk (vtk-gitAUR, vtk93AUR)
- xerces-c
- yaml-cpp
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR, cmake3AUR) (make)
- eigen (eigen-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- nlohmann-json (nlohmann-json-gitAUR) (make)
- shiboken6 (make)
- swig (swig-gitAUR) (make)
- pugixml (pugixml-gitAUR) (check)
- calculix-ccxAUR (optional) – FEM solver backend
- graphviz (optional) – dependency graph support
- libspnav (libspnav-gitAUR) (optional) – 3D mouse support
- openscad (openscad-objects-gitAUR, openscad-qt6-gitAUR, openscad-gitAUR) (optional) – OpenSCAD support
- python-pip (optional) – support installing python dependencies for addons
Required by (4)
- freecad-a2plus-git (requires freecad)
- freecad-cadquery-git (requires freecad)
- freecad-fcgear-git (requires freecad)
- openmc-git (requires freecad)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 39 40 41 42 43 44 45 46 47 48 49 .. 58 Next › Last »
Samsagax commented on 2013-02-17 15:34 (UTC)
Samsagax commented on 2013-02-14 13:52 (UTC)
@gborzi: FreeCAD is deprecating the use of autotools in favor of cmake. The latest release only comes with the cmake option. Could you reflect that change?
gborzi commented on 2013-01-06 14:34 (UTC)
Updated with "--enable-assembly".
Samsagax commented on 2013-01-06 13:52 (UTC)
Just add "--enable-assembly" for now. This package should have all experimental features enabled. there is also a template module but never tested it. indeed "--enable-cam" breaks compilation.
vinvin commented on 2013-01-05 21:34 (UTC)
Thanks for the fix Samsagax, and yes gborzi, same here. The error is due to the cam module, so for now --enable-cam should not be used I guess.
gborzi commented on 2013-01-05 19:29 (UTC)
Fixed with the sed command suggested by Samsagax. I tried "--enable-assembly" and "--enable-cam" in the configure step, but the compilation failed.
Samsagax commented on 2013-01-05 15:59 (UTC)
Just add this line after the freecad-build git clone:
sed -i -e 's/AM_CONFIG_HEADER/AC_CONFIG_HEADERS/g' configure.ac
And vinvin issue is gone. Still it should be reported upstream.
Samsagax commented on 2013-01-05 15:41 (UTC)
I'm having the same errors as vivin. Maybe the two are related and need to be reported upstream.
Also, could you add the "--enable-assembly" and "--enable-cam" flags to configure step? Those where recently merged into master.
vinvin commented on 2013-01-05 00:51 (UTC)
The new automake version brought lots of "undefined macro" kind of errors (for example: AM_INIT_AUTOMAKE AM_CONFIG_HEADER AC_CXX_HAVE_STD_IOSTREAM).
configure also complains about the --with-qt* and --with-boost* args.
Pinned Comments
adrianinsaval commented on 2023-03-12 14:50 (UTC)
If the check fails there is little I can do about it as it most likely needs to be fixed upstream, in such cases report those upstream (maybe wait a day or two as sometimes it's quickly solved upstream) or skip the check with
makepkg --nocheck
if you don't care about the functionality that is being reported as failing in the check.