Could we have this patch as a quick fix, package won't build without it. https://github.com/FreeCAD/FreeCAD/pull/2964
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: | 104 |
Popularity: | 0.011924 |
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-waylandAUR, glew-osmesa-gitAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- medAUR (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR, opencascade-rcAUR, opencascade-f3dAUR)
- 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-headlessAUR, qt6-base-gitAUR)
- qt6-svg
- qt6-tools
- Show 19 more dependencies...
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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 58 Next › Last »
bartus commented on 2020-02-03 21:37 (UTC)
dviktor commented on 2019-12-23 12:05 (UTC)
Just add -DPYSIDE2RCCBINARY=/usr/bin/rcc
to cmake options in PKGBUILD to resolve issue with PYSIDE2RCCBINARY-NOTFOUND
lonaowna commented on 2019-12-19 16:51 (UTC) (edited on 2019-12-19 16:52 (UTC) by lonaowna)
This package does not build with PySide2 5.14 (currently in testing). It fails with the following message:
[ 4%] Generating Material_rc.py
/bin/sh: PYSIDE2RCCBINARY-NOTFOUND: command not found
See FreeCAD issue 4229 for more information.
dviktor commented on 2019-11-27 13:43 (UTC)
Tried with latest PySide2 and Shiboken2 but problem still exists
bebR commented on 2019-11-23 20:03 (UTC)
@s218, it's great that you found a workaround. but for me, tweaking pkgbuild and stuff is counterproductive. Plus, the time to compile this package takes a long time. I did use distcc to speed the process but then comes compilation issues... I'll currently stick with the AppImage version, and it's delivered by Freecad developers, rather official. Thanks.
s218 commented on 2019-11-23 18:31 (UTC) (edited on 2019-11-24 16:06 (UTC) by s218)
upd 2019-11-24 уже исправлено, т.е. можно не читать is already fixed, so you don't have to read -
this package is built, installed and running if you change the string -
-DPYSIDE_LIBRARY="/usr/lib/libpyside2.cpython-${PYVER//.}m-${CARCH}-linux-gnu.so" \
to this one (delete the letter m)
-DPYSIDE_LIBRARY="/usr/lib/libpyside2.cpython-${PYVER//.}-${CARCH}-linux-gnu.so" \
s218 commented on 2019-11-23 16:42 (UTC)
https://forum.freecadweb.org/viewtopic.php?f=4&t=40986&sid=deb0a69eb4a7450e8e49be29332fec17
Pyside2 + python3.8 is not yet working. pyside2 version 5.14 will adress these issue. You can follow these links to get more information: https://github.com/conda-forge/freecad- ... -551993747 https://bugreports.qt.io/browse/PYSIDE-939
s218 commented on 2019-11-23 16:23 (UTC)
This program assembly breaks the related sketches. That is, if you make a sketch of 1 figure A and then in the next sketch (2) to use a link to this figure A from the sketch 1, and then in the first sketch to change the same figure A, then in the sketch 2 we get an accident. This problem is solved in https://aur.archlinux.org/packages/freecad-linkstage3-git, which, however, also is not going to. So it makes sense to finish it off.
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.