Package Details: kicad-git 8.99.0.r1825.gb38357a5ea-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
Conflicts: kicad, kicad-bzr
Provides: kicad
Submitter: Chocobo
Maintainer: nickoe
Last Packager: nickoe
Votes: 67
Popularity: 0.000003
First Submitted: 2015-10-08 16:39 (UTC)
Last Updated: 2024-07-16 22:49 (UTC)

Required by (22)

Sources (1)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 Next › Last »

nickoe commented on 2014-04-15 20:58 (UTC)

I have published my version of this script, it is a bit hacky regarding the python stuff, but that does not work currently, use the pre-kiway tag if you want to test out the python scripting in kicad, that should work when you uncomment the python hax lines. The boost skip patch is needed to be able to skip boost and build with more than -j1. That will be fixed when drawing_tools from cern is merged. The multiline patch is just a simple patch I just submitted. https://github.com/nickoe/PKGBUILDs/tree/master/kicad-bzr

liquibyte commented on 2014-04-15 13:13 (UTC)

I keep coming back trying to build this because I'd like to try out some of the new features, I've been doing this for months. Alas, it never even comes close to building. I know it's not the maintainers fault but the upstream sources being broken like this makes things untennable for someone wanting to try this out. Until they stabilize the sources to not need special treatment and Ubuntu-centric, I'm calling this broken and out of date.

b_eagle commented on 2014-03-13 07:23 (UTC)

Installation goes fine, but when I try to execute any module I get this error: kicad: relocation error: kicad: symbol _ZTI10wxListBase, version WXU_3.0 not defined in file libwx_baseu-3.0.so.0 with link time reference How can I fix this??

danwood76 commented on 2014-02-13 08:34 (UTC)

The PKGBUILD doesn't build kicad with the github plugin so we are unable to use the github PCB libraries. This can be fixed by adding '-DBUILD_GITHUB_PLUGIN=ON' to the cmake line in the PKGBUILD.

keenerd commented on 2014-02-10 00:18 (UTC)

Apologies for the delay with getting this pkgbuild tuned up. I'd been working with the kicad release package, which has been fairly frustrating. The most recent release tarball (4024) seems more ubuntu-centric that usual and the previous version (4017) it is being very odd with wxgtk3. (While it successfully produces a package, the compilation stops at 45% and the package is not that useful.) This -bzr package is built with wxgtk3 and with Arch's Boost. It seems to work okay here but I'd like some more people to test it out. If you want stable we have the package in community. Please report if you have any issues that seem to be Boost related. BACK UP YOUR PROJECTS! Saves from kicad-bzr might not be fully compatible with Kicad in community. Long term, if the release tarballs keep being weird, I might switch the community package to a bzr tagged release.

CarlPoirier commented on 2014-02-03 17:47 (UTC)

This has been discussed at length on the developer's mailing list: https://lists.launchpad.net/kicad-developers/msg11959.html Wayne Stambaugh explains: "Newer versions of Boost would break builds and the CMake FindBoost() macro only tests for a minimum version not a specific version. Finally the decision was made to use CMake to download and build a specific version of Boost for the sanity of the lead developers."

Transfixer commented on 2014-02-03 17:06 (UTC)

The risk is only, if you use old boost.

orson commented on 2014-01-30 15:51 (UTC)

@queueRAM 1) There is a risk with the default boost. The KiCad main developers strongly advise to build the shipped boost, as it contains patches that solve problems that were found while using the default one with KiCad. 2) Yes, you need -DKICAD_SCRIPTING=ON, and then maybe -DKICAD_SCRIPTING_MODULES=ON or -DKICAD_SCRIPTING_WXPYTHON=ON - I am not sure about those two. 3) It is recommended, but not required - I guess it is up to you (but please note that I do not maintain any packages here, it's just my personal opinion).