Yes, you should be able to use OCC instead of OCE, but it is not yet well tested.
I don't understand what you mean with OCE breaking build systems. The prefix location and adding a new location does not break build systems.
Git Clone URL: | https://aur.archlinux.org/kicad-git.git (read-only, click to copy) |
---|---|
Package Base: | kicad-git |
Description: | Electronic schematic and printed circuit board (PCB) design tools |
Upstream URL: | https://kicad.org/ |
Licenses: | GPL |
Conflicts: | kicad, kicad-bzr |
Provides: | kicad |
Submitter: | Chocobo |
Maintainer: | nickoe |
Last Packager: | nickoe |
Votes: | 67 |
Popularity: | 0.000001 |
First Submitted: | 2015-10-08 16:39 (UTC) |
Last Updated: | 2024-07-16 22:49 (UTC) |
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 29 Next › Last »
Yes, you should be able to use OCC instead of OCE, but it is not yet well tested.
I don't understand what you mean with OCE breaking build systems. The prefix location and adding a new location does not break build systems.
Would it be possible to build this package using opencascade (https://aur.archlinux.org/packages/opencascade/) instead of oce? I do not really know which is the difference between these two packages, but they mostly look like the same thing, and opencascade installs a lot more cleanly.
I have both installed: oce for kicad-git, and opencascade for freecad. If they are the same thing, it would be good getting rid of one.
oce package installs under /opt and messes with LD_LIBRARY_PATH, breaking some build systems (opencascade installs under /usr). So if this can be done with opencascade instead oce, for me it would be a gain.
It works fine after the efa2a13eaa4e8b7090ef978ab5e203ae3c32668c commit. Thanks!
@nickoe I've read them. I just added that I can run without problems if I invoke kicad from build/kicad directly.
@palmitoxico, this is expected, read the comments.
There is something wrong with the packaging. I can run eeschema and pcbnew with no problems invoking kicad from the build/kicad directory (provided that you create symlinks to _eeschema.kiface and _pcbnew.kiface inside the build/kicad directory), but when running the installed package the pcbnew window doesn't show buttons / widgets and don't resize properly and it prints:
/usr/lib/python2.7/site-packages/wx-3.0-gtk3/wx/_core.py:16629: UserWarning: wxPython/wxWidgets release number mismatch warnings.warn("wxPython/wxWidgets release number mismatch")
After closing pcbnew, a segmentation fault occurs in Kicad.
Also, when running eeschema, trying to insert any component causes it to stop responding.
@orson
I will do that, thanks for your reply.
Sorry for the wrong post.
@mbl
I would rather move the discussion to the official bug tracker [1], this place is dedicated to package related discussions.
Can you try removing symbol libraries to see if it helps? Also, do you have wxpython or wxpython-gtk2 installed? If possible, please report it on the bug tracker with the questions answered.
Hi,
I have build kicad-git today. Eeschma freezes (for me) if I try to place a new component. Anyone an idea how to debug/fix this?
The problem was that even with KICAD_SCRIPTING_WXPYTHON = OFF, src/kicad-git/pcbnew/python/kicad_pyshell/init.py would be loaded and it imports "wx" which is wxWidgets causing the version mismatch problem.
I reported it upstream under https://bugs.launchpad.net/kicad/+bug/1760200 and will be fixed soon. As a hotfix, you can temporarily delete /usr/share/kicad/scripting/kicad_pyshell/init.py. Of course completely disabling scripting also solves it, but it would be disabling too much unnecessarily.
Pinned Comments