| 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-21 17:00 (UTC) |
This does not run for me, it appears that the recent boost upgrade needs to be accounted for.
FreeCAD: error while loading shared libraries: libboost_filesystem.so.1.75.0: cannot open shared object file: No such file or directory
If I downgrade to 1.75.0 of boost and boost-libs, I cannot compile, it fails because OpenSCAD expects 1.76...
I had the same issue with the aur appimage package, so this might be an upstream arch/freecad issue?
This doesn't build for me at the moment: it appears to be complaining that ospray has the wrong version (in the repos currently is 2.5.0).
~ » aur sync freecad-git
==> Using [custom] repository
-> freecad-git: 0.19_pre.r5362.gcbc3fbd157-1 -> 0.19.r582.g0cfea3fee3-1
==> Retrieving package files
From https://aur.archlinux.org/freecad-git
= [up to date] master -> origin/master
Running makepkg --syncdeps --clean
==> Making package: freecad-git 0.19.r796.g4a9963a03f-1 (Thu 10 Jun 2021 08:56:52 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating FreeCAD git repo...
Fetching origin
==> Validating source files with md5sums...
FreeCAD ... Skipped
==> Extracting sources...
-> Creating working copy of FreeCAD git repo...
Reset branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
-- Compiler: GNU, version: 11.1.0
-- prefix: /usr/lib/freecad
-- bindir: bin
-- datadir: ../../share/freecad
-- docdir: ../../share/doc/freecad
-- includedir: include
-- libdir: ../../lib
-- cmake: 3.20.3
-- PyCXX found:
-- Headers: /home/jade/.cache/aurutils/sync/freecad-git/src/FreeCAD/src
-- Sources: /home/jade/.cache/aurutils/sync/freecad-git/src/FreeCAD/src/CXX
-- Version: 6.2.8
-- -- Found OCE/OpenCASCADE version: 7.5.0
-- -- OCE/OpenCASCADE include directory: /usr/include/opencascade
-- -- OCE/OpenCASCADE shared libraries directory: /usr/lib
-- VTK components: not found or used
CMake Error at /usr/lib64/cmake/vtk-9.0/VTK-vtk-module-find-packages.cmake:162 (find_package):
Could not find a configuration file for package "ospray" that is compatible
with requested version "1.8".
The following configuration files were considered but not accepted:
/usr/lib64/cmake/ospray-2.5.0/osprayConfig.cmake, version: 2.5.0
/usr/lib/cmake/ospray-2.5.0/osprayConfig.cmake, version: 2.5.0
/lib64/cmake/ospray-2.5.0/osprayConfig.cmake, version: 2.5.0
/lib/cmake/ospray-2.5.0/osprayConfig.cmake, version: 2.5.0
Call Stack (most recent call first):
/usr/lib64/cmake/vtk-9.0/vtk-config.cmake:131 (include)
cMake/FreeCAD_Helpers/SetupSalomeSMESH.cmake:45 (find_package)
CMakeLists.txt:58 (SetupSalomeSMESH)
-- Configuring incomplete, errors occurred!
Just tried to compile and I get broken OpenSCAD but not: AssertionError: 25.499999999999996 != 17.0 in check() mentioned by @greyltc in https://aur.archlinux.org/packages/freecad-git/#comment-807928
I think everything is sorted now. Please post here if you still have issues. If you're getting the AssertionError: 25.499999999999996 != 17.0 in check(), it's a known issue with OpenSCAD support and upstream is trying to fix it.
Just to confirm, getting similar issues:
Getting a mostly empty app window and the following messages in the log window:
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Arch/Resources/icons/ArchWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Draft/Resources/icons/DraftWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Drawing/Resources/icons/DrawingWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Fem/Resources/icons/FemWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Image/Resources/icons/ImageWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Inspection/Resources/icons/InspectionWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Mesh/Resources/icons/MeshWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/OpenSCAD/Resources/icons/OpenSCADWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/PartDesign/Resources/icons/PartDesignWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Part/Resources/icons/PartWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Path/Resources/icons/PathWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Plot/resources/icons/PlotWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Points/Resources/icons/PointsWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Raytracing/Resources/icons/RaytracingWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/ReverseEngineering/Resources/icons/ReverseEngineeringWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Robot/Resources/icons/RobotWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Ship/resources/icons/ShipWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Sketcher/Resources/icons/SketcherWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Spreadsheet/Resources/icons/SpreadsheetWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Start/Resources/icons/StartWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Surface/Resources/icons/Surface_Workbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/TechDraw/Resources/icons/preferences-techdraw.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Test/Resources/icons/TestWorkbench.svg
12:20:04 Cannot find icon: /usr/lib/freecad/share/Mod/Web/Resources/icons/WebWorkbench.svg
12:20:05 Wizard shaft module cannot be loaded
12:20:05 No module named 'PartDesignGui'
@greyltc Thanks a lot for the quick response. Unfortunately it's not yet working correctly. I now get the following error messages:
Cannot find icon: /usr/lib/freecad/share/Mod/Arch/Resources/icons/ArchWorkbench.svg
[... for all mods ...]
No module named 'StartGui'
FreeCAD seems to really rely on not having it's folder structure changed. Also having something like "StartGui.so" or "Mesh.so" in "/usr/lib" seems confusing to me because it suggests it's something "global" and not related to a specific program. What's your take on this?
Ack! sorry about that, should hopefully be fixed now!
@greyltc: with the latest changes in the PKGBUILD my FreeCAD doesn't find any modules (message: "No modules found in /usr/Mod"). It seems "/usr/bin/FreeCAD" used to be a symlink to "/usr/local/freecad/bin/FreeCAD" and FreeCAD uses the executable path (stripped of the executable name and the bin folder) to determine it's "home path" (see https://github.com/FreeCAD/FreeCAD/blob/master/src/App/Application.cpp line 2972). However with the new folder structure the FreeCAD executable sits directly in "/usr/bin" and it will therefore search in "/usr/Mod" (instead of "/usr/lib/freecad/Mod") for it's modules.
@bartus Oh yeah. The file layout here is totally wrong now (thought I checked that). Thanks for pointing that out. I'll fix it when I have a free minute.
@Woodhousezb if your check function is failing with AssertionError: 25.499999999999996 != 17.0 within 1 places (8.499999999999996 difference) then I guess that's upstream's bug. You can move to some commit that does not have this or try to help them understand/fix it, or build with --nocheck if you want to ignore the check function failure. I made a bug report on it here: https://tracker.freecadweb.org/view.php?id=4622
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 --nocheckif you don't care about the functionality that is being reported as failing in the check.