Hi, There!
I am running kicad-latest for testing purposes in my home directory:
~/SW/usr/local/bin/kicad
There is also kicad-4.0.1 in /usr/bin/kicad.
To test the latest stuff from you, I
1. open kicad-latest from a terminal/console:
[admin@black bin]$ pwd
/home/admin/SW/usr/local/bin
[admin@bl
Is there a reason you installed KiCad in ~/SW/usr/local/bin/kicad? That
seems like a strange place to install it. The cmake defaults work fine for
me and coexist just fine with a stable install!
How did you specify that install location?
Jon
On Thu, Jan 7, 2016 at 7:12 PM Clemens Koller wrote:
Hello, Jon!
On 2016-01-08 01:36, Jon Neal wrote:
> Is there a reason you installed KiCad in ~/SW/usr/local/bin/kicad?
I don't want to merge/sudo the test builds into my (production)
distribution. So, I just tried to stay in ~/SW.
> That seems like a strange place to install it.
> The cmake defau
Hmm, did you specify the prefix paths the first time you ran cmake? It
looks like it is still trying to install some file (here _cvpcb.kface)
to a default location and not your user folder. but the make
DESTDIR=something install works fine for me. It has done way pre 4.0.1
and still on latest produ
If the _*.kiface files are not in the same path as your executable
files, then this is your problem. The kiface (don't let the naming
confuse you, they are shared objects) files must reside in the same path
as the executable files due to the way they are loaded.
On 1/8/2016 7:41 AM, Nick Østergaa
Hi!
Ok, redo from scratch.
I'm cleaning up the build directory now...
$ git pull
$ git checkout -f
$ rm -r build
$ cat ./go.sh
#!/bin/bash
mkdir -p build/release
cd build/release
cmake -DCMAKE_BUILD_TYPE=Release \
-DKICAD_SCRIPTING=ON \
-DKICAD_SCRIPTING_MODULES=ON \
-DKICAD_SCR
Try using -DCMAKE_INSTALL_PREFIX=~/SW.
On 1/8/2016 8:11 AM, Clemens Koller wrote:
> Hi!
>
> Ok, redo from scratch.
> I'm cleaning up the build directory now...
>
> $ git pull
> $ git checkout -f
> $ rm -r build
> $ cat ./go.sh
> #!/bin/bash
> mkdir -p build/release
> cd build/release
> cmake -DC
Still the same with:
$ rm -r build
$ mkdir -p build/release
$ cd build/release
$ cmake -DCMAKE_BUILD_TYPE=Release \
-DKICAD_SCRIPTING=ON \
-DKICAD_SCRIPTING_MODULES=ON \
-DKICAD_SCRIPTING_WXPYTHON=ON \
-DCMAKE_INSTALL_PREFIX=~/SW \
../../
$ make -j8
$ make install
$ c
And:
$ rm -r build
$ mkdir -p build/release
$ cd build/release
$ cmake -DCMAKE_INSTALL_PREFIX=~/SW ../../
$ make -j8
$ make install
makes the Traceback go away.
So it seems it's related to the KICAD_SCRIPTING stuff...
Regards,
Clemens
On 2016-01-08 14:33, Wayne Stambaugh wrote:
> Try using -DC
I feel like spamming the list with my noise ;-)
On 2016-01-08 15:39, jp charras wrote:
> Looks like pcbnew.py (and perhaps _pcbnew.pyc) is not found ( not copied
> to the right folder).
That's what ended up in the bin directory:
$ pwd
/home/admin/SW/bin
$ ls -la
total 40984
drwxr-xr-x 2 admin ad
2016-01-08 14:11 GMT+01:00 Clemens Koller :
> Hi!
>
> Ok, redo from scratch.
> I'm cleaning up the build directory now...
>
> $ git pull
> $ git checkout -f
> $ rm -r build
> $ cat ./go.sh
> #!/bin/bash
> mkdir -p build/release
> cd build/release
> cmake -DCMAKE_BUILD_TYPE=Release \
> -DKICAD
Le 08/01/2016 15:19, Clemens Koller a écrit :
> Still the same with:
>
> $ rm -r build
> $ mkdir -p build/release
> $ cd build/release
> $ cmake -DCMAKE_BUILD_TYPE=Release \
> -DKICAD_SCRIPTING=ON \
> -DKICAD_SCRIPTING_MODULES=ON \
> -DKICAD_SCRIPTING_WXPYTHON=ON \
> -DCMAK
I figured out your issue. Unfortunately when you install from source,
the python modules are always installed in the python site package path
which will fail without root privileges on linux distros. You may have
missed the python module install failure. We may want to rethink this
in the future
Hello, Nick!
Recompiled from scratch with scripting enabled again...
On 2016-01-08 15:43, Nick Østergaard wrote:
> Verify on the install output that they everything are installed to ~/SW.
Ehrm... I cannot tell what "everything" is supposed to be. :-/
Attached is the result of:
$ pwd
/home/admin
Hello, Wayne, Kyle!
[CC: to Arch Kicad package maintainer]
On 2016-01-08 16:21, Wayne Stambaugh wrote:
> I figured out your issue. Unfortunately when you install from source,
> the python modules are always installed in the python site package path
> which will fail without root privileges on li
2016-01-08 16:43 GMT+01:00 Clemens Koller :
> Hello, Wayne, Kyle!
>
> [CC: to Arch Kicad package maintainer]
>
> On 2016-01-08 16:21, Wayne Stambaugh wrote:
>> I figured out your issue. Unfortunately when you install from source,
>> the python modules are always installed in the python site packag
Hello, Nick!
On 2016-01-08 17:03, Nick Østergaard wrote:
> Distro packagers are supposed to enable scripting, and when they
> generate a package it is installed in the proper location for python.
> AFIK
>
> Anyway, I did write to keenerd that the scripting is supposed to be
> enabled. But it does
I am building with this:
$ cmake ../kicad-source-mirror -DKICAD_SKIP_BOOST=ON
-DCMAKE_INSTALL_PREFIX=/opt/kicad-build
-DDEFAULT_INSTALL_PATH=/opt/kicad-build -DKICAD_SCRIPTING=ON
-DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON
$ make all
$ make install
That installs pcbnew.py in :
Hello, Strontium!
On 2016-01-09 06:52, Strontium wrote:
> I am building with this:
> $ cmake ../kicad-source-mirror -DKICAD_SKIP_BOOST=ON
> -DCMAKE_INSTALL_PREFIX=/opt/kicad-build
> -DDEFAULT_INSTALL_PATH=/opt/kicad-build -DKICAD_SCRIPTING=ON
> -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXP
On 1/10/2016 11:13 AM, Clemens Koller wrote:
> Hello, Strontium!
>
> On 2016-01-09 06:52, Strontium wrote:
>> I am building with this:
>> $ cmake ../kicad-source-mirror -DKICAD_SKIP_BOOST=ON
>> -DCMAKE_INSTALL_PREFIX=/opt/kicad-build
>> -DDEFAULT_INSTALL_PATH=/opt/kicad-build -DKICAD_SCRIPTING=O
2016-01-10 22:54 GMT+01:00 Wayne Stambaugh :
> On 1/10/2016 11:13 AM, Clemens Koller wrote:
>> Hello, Strontium!
>>
>> On 2016-01-09 06:52, Strontium wrote:
>>> I am building with this:
>>> $ cmake ../kicad-source-mirror -DKICAD_SKIP_BOOST=ON
>>> -DCMAKE_INSTALL_PREFIX=/opt/kicad-build
>>> -DDEFAUL
Hi!
>>> It gets more interesting when I add the path to pcbnew.py:
>>>
>>> $ PYTHONPATH=~/SW/lib/python2.7/site-packages ./pcbnew
>>
>> I believe you wanted to do:
>>
>> $ export PYTHONPATH=~/SW/lib/python2.7/site-packages ./pcbnew
>
> You don't need the export when you write the variable before
Hi,
Am 11.01.2016 um 00:31 schrieb Clemens Koller:
$ PYTHONPATH=~/SW/lib/python2.7/site-packages python
Python 3.5.1 (default, Dec 7 2015, 12:58:09)
[GCC 5.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>import sys
>>>print(sys.path)
['', '/home/admin/S
Ohh yeah, I did not notice that before. That must be why it can't find
it. The scripting thing does not support py3k. We should really try to
make it support both. I hope someone volunteers, I myself, does not
know what it takes in the swig context.
But I can tell that on my system (archlinux) I h
As far as i know wxPython, which kicad requires for python scripting,
does not support py3k.
There is https://github.com/wxWidgets/Phoenix but i'm not sure how
compatible that is with wxPython, or if it is compatible with py2k.
Steven
On 11/01/16 16:46, Nick Østergaard wrote:
Ohh yeah, I di
Hi Clemens,
I have been looking at your problem.
And I believe you are either running Arch, or there is possibly
something wrong with your python install.
PEP-0394 http://legacy.python.org/dev/peps/pep-0394/ says that the
"python" command should run the python2 interpreter installed on your
Hi Steven!
> And I believe you are either running Arch, or there is possibly
> something wrong with your python install.
I'm on Arch x84_64 -latest-ish.
> PEP-0394 http://legacy.python.org/dev/peps/pep-0394/ says that the
> "python" command should run the python2 interpreter installed on your
>
27 matches
Mail list logo
