@greyltc: would be nice to move out of /usr/local/freecad
to e.g: /usr/lib/freecad/
( check out Debian package file-list ) ( debian package cmake flags )
Search Criteria
Package Details: freecad-git 1.1.0.41361.g774ec2cc93-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.18 |
First Submitted: | 2012-03-03 13:46 (UTC) |
Last Updated: | 2025-04-22 00:51 (UTC) |
Dependencies (40)
- boost-libs
- coin (coin-gitAUR)
- fmt (fmt-gitAUR)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- med (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR)
- openmpi (openmpi-gitAUR)
- pybind11 (pybind11-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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 58 Next › Last »
bartus commented on 2021-04-11 13:51 (UTC) (edited on 2021-04-11 13:58 (UTC) by bartus)
Woodhousezb commented on 2021-04-11 07:32 (UTC)
Hi there,
Kind of got the impression the problem got tackled, but I still get the same errors when trying to compile. @greylts: Is tis supposed to woork after your last comment?
greyltc commented on 2021-04-08 10:36 (UTC)
@bartus sorry about that. I didn't mean to leave that testing line active in my commit.
bartus commented on 2021-04-08 07:55 (UTC) (edited on 2021-04-08 10:54 (UTC) by bartus)
@greyltc: Sorry but this won't work 10fb2eb61467 if users has no github config (username/email) or if build inside chroot (also it breaks pkgver()
)
Please switch to --no-commit
flag.
greyltc commented on 2021-04-07 10:25 (UTC)
Generally for me check() fails when there's an upstream bug and passes when there's not.
There still might be an issue with the current install somehow leaking into the check() environment when you rebuild the package, any help with addressing that is welcome.
neo2001 commented on 2021-04-07 10:16 (UTC)
I think if the check function always(?) prevents a successful package build, it should be commented out, until a solution is available. If everyone builds with "--nocheck" it's of no use anyway. Or are there people out there for which the package builds fine with the all the checks successful?
greyltc commented on 2021-04-07 10:06 (UTC)
I think the TestImportCSG failure is an upstream bug. I've reported it here: https://tracker.freecadweb.org/view.php?id=4622
cculpepper1214 commented on 2021-04-04 20:14 (UTC)
Running makepkg with --nocheck worked, however uninstalling freecad did not. ( I just pacman -R'd it, no reboots though. I'll just run with --nocheck for now. Thank you!
greyltc commented on 2021-04-04 19:01 (UTC)
I suspect the check() function is not being sandboxed properly and so part of the existing install is leaking into check() when it runs here. If anyone has any ideas for fixing that I'd love to hear them.
@cculpepper1214 you might try uninstalling freecad, then building this again or you can build it with --nocheck to hopefully avoid the issue for now.
cculpepper1214 commented on 2021-04-04 17:50 (UTC)
Hello! I've been having trouble building this package, for about a week. The length of time makes me suspect something in my install is causing it, but I don't know what/how to find it. I've built from raw github source, and that worked fine.
Here's the output I'm getting:
testAll (TestPythonSyntax.PythonSyntaxTestCase) ... ok
======================================================================
FAIL: test_import_resize (OpenSCADTest.app.test_importCSG.TestImportCSG)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/chris/.cache/yay/freecad-git/src/FreeCAD/build_dir/check/Mod/OpenSCAD/OpenSCADTest/app/test_importCSG.py", line 352, in test_import_resize
self.assertAlmostEqual (object.Shape.BoundBox.XLength, 2*8.5, 1)
AssertionError: 25.499999999999996 != 17.0 within 1 places (8.499999999999996 difference)
======================================================================
FAIL: test_known_quantity_units (femtest.app.test_material.TestMaterialUnits)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/chris/.cache/yay/freecad-git/src/FreeCAD/build_dir/check/Mod/Fem/femtest/app/test_material.py", line 77, in test_known_quantity_units
self.assertTrue(
AssertionError: False is not true : Unit of quantity material parameter ElectricalConductivity is not known by FreeCAD unit system.
I've also updated to the latest openscad (from openscad-git). Does anyone have any ideas?
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.