Package Details: kicad-git 9.0.0.rc1.r499.gf665760a8e-1

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-3.0-or-later
Conflicts: kicad, kicad-bzr
Provides: kicad
Submitter: Chocobo
Maintainer: nickoe
Last Packager: nickoe
Votes: 67
Popularity: 0.000000
First Submitted: 2015-10-08 16:39 (UTC)
Last Updated: 2025-01-07 22:16 (UTC)

Required by (26)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 29 Next › Last »

ILF commented on 2018-05-15 15:45 (UTC)

Was someone successful in building kicad with opencascade (OCC), instead of oce. I, too, would prefer to use opencascade because of freecad. When I try to use OCC, compile fails with a dependency on PTKernel, and it seems the PTKernel module is not part of opencascade since version 6.9.1.

doragasu commented on 2018-05-14 09:06 (UTC)

I do not know why, but several cross compilers fail if you define LD_LIBRARY_PATH.

You can test this e.g. by downloading crosstool-ng and trying to build any toolchain. Unless you unset LD_LIBRARY_PATH, build will fail.

nickoe commented on 2018-05-14 08:04 (UTC)

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.

doragasu commented on 2018-05-14 08:00 (UTC)

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.

palmitoxico commented on 2018-04-10 11:18 (UTC)

It works fine after the efa2a13eaa4e8b7090ef978ab5e203ae3c32668c commit. Thanks!

palmitoxico commented on 2018-04-04 14:04 (UTC)

@nickoe I've read them. I just added that I can run without problems if I invoke kicad from build/kicad directly.

nickoe commented on 2018-04-04 12:56 (UTC)

@palmitoxico, this is expected, read the comments.

palmitoxico commented on 2018-04-04 12:47 (UTC)

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.

mbl commented on 2018-04-03 18:25 (UTC)

@orson

I will do that, thanks for your reply.

Sorry for the wrong post.

orson commented on 2018-04-02 15:50 (UTC)

@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.

  1. https://bugs.launchpad.net/kicad

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 29 Next › Last »