@eworm
I'm unable to reproduce the error you reported. I have compiled and installed freecad along with freecad-svn and they work together just fine. ldd shows that the executables point to the respective libraries.
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.012167 |
| 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
- shared-mime-info
- verdict
- vtk (vtk-gitAUR)
- xerces-c
- yaml-cpp
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (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-gitAUR, openscad-qt6-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)
gborzi commented on 2011-09-22 16:28 (UTC)
gborzi commented on 2011-09-22 13:30 (UTC)
@eworm
thanks for reporting the problem. The svn suffix was added in order to have both versions of freecad running together. I'll fix it ASAP.
eworm commented on 2011-09-22 12:14 (UTC)
Ah, found the problem: freecad-svn tried to load libraries from freecad 0.11. Why do you use the suffix "-svn" for application and paths if it's not possible to install 'stable' and svn side by side?
eworm commented on 2011-09-22 10:36 (UTC)
The package built successfully, but I get an error starting the application: /usr/lib/freecad/Mod/Raytracing/libRaytracingGui.so.2: undefined symbol: _ZN3Gui17SyntaxHighlighterC2EP9QTextEdit
Any ideas what went wrong?
gborzi commented on 2011-09-19 12:21 (UTC)
Thanks Mickele,
I'll upload a new PKGBUILD ASAP.
mickele commented on 2011-09-19 11:17 (UTC)
python-qt has been renamed to python2-pyqt!
<deleted-account> commented on 2011-09-19 11:07 (UTC)
Hi all. I tried to compile freecad-svn but I'm missing python2-qt. Where can I get this package as I couldn't find it anywhere, neither in the official repos nor AUR.
<deleted-account> commented on 2011-08-18 08:43 (UTC)
@gborzi
Just compiled 4768-1 with !makeflags [ Arch32bit Atom330 ] on one core.
After 3 hours compilation done sucessfull.[ FreeCAD svn only of course :) ]
Thanks for your help.
gborzi commented on 2011-08-17 20:48 (UTC)
@spookyln
I've just finished compiling rev. 4768 with makeflags (-j9). Which revision have you tried to compile?
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.