kicad-developers team mailing list archive

[Jason Whiteman <whitemanjason@xxxxxxxxx>]

FYI - Y:\ is not a network drive.  It is an external USB-connected drive
(HDD).  I had moved the bin directory to C:\ in earlier tests suspecting
perhaps something hard-coded, but that did not help.  Granted - I simply
took the /kicad/bin directory (and sub-directory) to C:\kctst and ran
kicad.exe or pcbnew.exe from c:\kctst and received the same results.

Regarding a matter of faith - I said believe because I do not have a
complete list of dependencies listed for the python dlls mentioned.
However, I can say that in the path given:

Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin (1st kicad
build directory in path) - dir *python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin
(2nd ") - dir *python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar - (3rd ") - dir *python* -
contains filesize: 2,148,864 filename: python26.dll -- which is what I
believed to be the dll mentioned (python*).

Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin - (4th ") - dir *python*
- no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\python - (5th ") - dir *python* -
1,863,207 libpython2.7.dll and 97,183 python.exe - 2nd half which I believe
completes the list of "python" files although I have no exact list thus
requiring some amount of leaping.  Both of these files are also in the
/kicad/bin directory (Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin) per
the make process.  As a test - I also copied the python26.dll into the
/kicad/bin directory which did not change the results.

Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10 - (6th ") - dir
*python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee - (7th ") - dir *python* - no
results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin - (8th ")
- dir *python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin - (9th ") -
dir *python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin - (10th ") -
dir *python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin - (11th ") - dir
*python* - no results

Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin - (12th ") - dir *python* -
originally 1,863,207 libpython2.7.dll and 97,183 python.exe -  also added
2,148,864 python26.dll and 354,304 pythoncom26.dll manually.

Y:\Kicad_Build\kicad-winbuilder-3.4\kicad - (13th ") - dir *python* - no
results

=======

A more complete transfer of the tree to C:\ - I tried the following:

from Y:\Kicad_Build\kicad-winbuilder-3.4

xcopy /e /s *.* c:

And C: current directory is C:\kctst

Thus mirroring the entire winbuilder tree to c:\kctst
98456 File(s) copied
 -- took a while

New environment (abridged):

Path=C:\kctst\env\mingw-w64\mingw32\bin;C:\kctst\env\cmake\cmake-2.8.12.2-win32-
x86\bin;C:\kctst\env\bazaar;C:\kctst\env\patch\bin;C:\kctst\env\python;C:\kctst\
env\swig\swigwin-2.0.10;C:\kctst\env\tee;C:\kctst\env\libxslt-1.1.26.win32\bin;C
:\kctst\env\libxml2-2.7.8.win32\bin;C:\kctst\env\iconv-1.9.2.win32\bin;C:\kctst\
env\zlib-1.2.5\bin;C:\kctst\kicad\bin;C:\kctst\kicad;C:\windows\System32
PATH_PY=C:\kctst\env\python
PYTHONHOME=C:\kctst\kicad\bin
PYTHONPATH=C:\kctst\kicad\bin

Using RunKicad.bat or enterenv.bat then pcbnew.exe both generate the
"Failed to load shared library 'C:\ktst\kicad\bin\_pcbnew.kiface'"

It appears that Y:\ is not the source of issue.

Regards,
Jason


On Fri, Jun 27, 2014 at 12:01 PM, Brian Sidebotham <
brian.sidebotham@xxxxxxxxx> wrote:

> Hi Guys,
>
> I should first say, this is not typical of Winbuilder. Both pcbnew and
> cvpcb work fine for me on a fresh Windows 7 install using the github
> fp-lib-table. So there's clearly something different about your setup.
>
> Process monitor is (from sysinternals) is excellent at tracking
> dependency loading, so if you want to track what's getting loaded from
> where, that's the best tool for the job. If you use dependency walker
> make sure you run it from the console provided by enterenv.bat so that
> PATH is set the same as when kicad is run.
>
> I wonder what Y: is? Is winbuilder on a network drive? Can you move it
> to a local drive instead and run? I wonder if it's a permissions issue
> with regards to loading dependencies?
>
> Best Regards, Brian.
>