Re: [Kicad-developers] Build 4955 - Failed to load shared library
Followup: Since my initial out of the box Winbuilder initial compiles - I've been hacking the mingw, makefile, and wxpython environment (along with other modifications) which did not work in order to compile with a newer GCC and newer Wxpython. I've since backed that out -- and ran a mingw32-make clean from the build directory. The latest time I built with SCRIPTING on - I no longer see a shared library error. Not sure what the effective change was - but reporting everything is OK. I can now run pcbnew, etc. with full scripting on. As far as general functionality - with scripting on or off I've been seeing pcbnew crash when I close pcbnew. I do not have a debug trace. Regards, Jason On Fri, Jun 27, 2014 at 7:57 PM, Jason Whiteman whitemanja...@gmail.com wrote: Thanks again for the continued support from the list. All previous environment snapshots I have sent were after running the setenv.bat script. My methodology for loading pcbnew is to try running direct from ./kicad/bin (from a sentenv.bat load) and also from using RunKicad.bat which loads kicad.exe first. I have sent bits and pieces of my environment as it applies to the suggested assumed missing dependency. Here is the full environment ( C:\ set env.txt- env.txt results) slightly censored only for what looks a mentor graphics key. Otherwise as-is. Therefore, there is some noise from other env variables for other packages. However, everything fed to kicad.exe and pcbnew.exe is below as a result of setenv.bat. ACTEL_FOR_ALTIUM_OVERRIDE= ADSK_3DSMAX_x64_2012=C:\Program Files\Autodesk\3ds Max Design 2012\ ALLUSERSPROFILE=C:\ProgramData AltiumPath=C:\Program Files (x86)\Altium Designer S09 Viewer\System AMDAPPSDKROOT=C:\Program Files (x86)\AMD APP\ APPDATA=C:\Users\MY-COMPUTER\AppData\Roaming AVR32_HOME=Y:\WinAVR-20100110 BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\bzr.exe BZR_HOME=Y:\Kicad_Build\kicad-winbuilder-3.4\profile BZR_PLUGIN_PATH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\plugins CALLDIR=Y:\Kicad_Build\kicad-winbuilder-3.4 CLASSPATH=.;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip CM2012DIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=MY-COMPUTER ComSpec=C:\windows\system32\cmd.exe configsetroot=C:\windows\ConfigSetRoot EDPATH=Y:\WATCOM\EDDAT FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Users\MY-COMPUTER ICONV_VER=1.9.2 ILBDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ ILLDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ ILMDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ INCLUDE=Y:\WATCOM\H;Y:\WATCOM\H\NT;Y:\WATCOM\H\NT\DIRECTX;Y:\WATCOM\H\NT\DDK KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad LenovoTestLogFile=preload.log LenovoTestPath=C:\prdv10\ LMC_HOME=E:\Xilinx91i\smartmodel\nt64\installed_nt64 LM_LICENSE_FILE=c:\lattice_license\license.dat LOCALAPPDATA=C:\Users\MY-COMPUTER\AppData\Local LOGONSERVER=\\MY-COMPUTER MGLS_LICENSE_FILE=c:\MentorGraphics\[censored - looks like a key].txt NUMBER_OF_PROCESSORS=2 OMP_NUM_THREADS=2 OS=Windows_NT Path=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar;Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\python;Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10;Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad;C:\windows\System32 PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.RB;.RBW PATH_BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar PATH_CMAKE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin PATH_ENV_BASE=Y:\Kicad_Build\kicad-winbuilder-3.4\env PATH_ICONV=Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin PATH_KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin PATH_KICAD_ROOT=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad PATH_MINGW=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin PATH_PATCH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin PATH_PROFILE=Y:\Kicad_Build\kicad-winbuilder-3.4\profile PATH_PY=Y:\Kicad_Build\kicad-winbuilder-3.4\env\python PATH_SWIG=Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10 PATH_TEE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee PATH_TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
I've tried a few different things with mixed results: 1) Tried moving the build environment to a new machine - entails: a. Starting fresh on a new machine with no other related build environments b. Downloaded and un-7z'd the latest winbuilder (3.4-2) c. Built from scratch with default parameters including SCRIPTING ON d. Machine is Win Server 2008 R2 Results: R1.1: Running on Win2k8 R2 - RunKicad.bat fails as Kicad.exe failed with a 0xC005 error in wxbase300u_gcc_cm.dll *Problem signature: * Problem Event Name: APPCRASH Application Name: kicad.exe Application Version: 0.0.0.0 Application Timestamp: 0473ae68 Fault Module Name: wxbase300u_gcc_cm.dll Fault Module Version: 3.0.0.0 Fault Module Timestamp: 52ce8e9f Exception Code: c005 Exception Offset: 000af358 OS Version: 6.1.7601.2.1.0.400.8 Locale ID: 1033 Additional Information 1: 4c0d Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433 Additional Information 3: 4c0d Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433 R1.2: Copied the root directory (including RunKicad), root/env (and all subdirectories - for RunKicad), and root/bin (and all subdirectories) to the original Win7 machine. The wxbase error did not present itself, but pcbnew.exe still failed in the same manner as the original compile on the win7 machine - shared library failure. Conclusions: compile/build is not as much as the issue, not a single-unit (toolchain land) failure. 2) Used SCRIPTING OFF to disable features that may be causing problems with the shared library issue a. Modified KiCadWinbuilder.cmake - changed set( SCRIPTING ON ) to set( SCRIPTING OFF ) as the sledge-hammer fix. Results: R2.1: Loading Kicad.exe (using RunKicad) on Win2k8 server failed the same as R1.1 - still see wxbase error. R2.2: Copying over binaries from Win2k8 to Win7 (as R1.2 above) and retried -- no longer see shared library failure. Conclusions: with loss of functionality, using SCRIPTING OFF will allow the binaries to work on my Win7 machine. However, the specific cause of the failure (missing component, etc) is not identified. Secondly, the new/broken behavior of the binaries on Win2k8 is troubling as it appears only a lucky target windows machine has allowed for me to run these binaries. Regards, Jason On Fri, Jun 27, 2014 at 12:40 PM, Dick Hollenbeck d...@softplc.com wrote: On 06/27/2014 12:01 PM, Brian Sidebotham 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. Brian, thanks for your involvement. I am now bowing out. I just wanted us to remember that it loads and runs fine under pcbnew.exe, and not kicad.exe. Your comment about setting the environment differently probably pertains to the difference in loading results also. Perhaps there's a difference in how the environment is setup for the specific process. Remember that the environment when the process runs, is what's critical. A batch file can add or remove settings to the environment that it starts with, before the process runs. So simply getting a snapshot from the registry is not necessarily sufficient to describe the runtime environment variable values that any particular process sees. Environment varialbe PATH is still my biggest suspicion, in concert with a difference in launching methodology. Out, Dick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
On 06/26/2014 04:14 PM, Jason Whiteman wrote: Team, I am new to the dev group and have compiled my first windows binaries today based on what was pulled using kicad-winbuilder-3.4 (Kicad BZR build 4955). The binaries were created fine - and I was able to load kicad.exe using RunKicad.bat My issue is the error: Failed to load shared library 'Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin\_pcbnew.kiface' (error 0: the operation completed successfully.) I have searched for this error and see it is not uncommon. However, in all threads I have read - the problem was with the makefile failing to copy the _*.kiface files to the kicad/bin directory. This is not the case here. I see the files have landed there: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 01:59 PM 6,596,731 _cvpcb.kiface 06/26/2014 01:59 PM 6,728,781 _eeschema.kiface 06/26/2014 01:59 PM 2,771,868 _gerbview.kiface 06/26/2014 01:59 PM17,465,298 _pcbnew.kiface 06/26/2014 01:59 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 01:59 PM 2,463,434 _pl_editor.kiface EEschema can load, pcb_calculator loads, bitmap2component loads, gerbview loads. However both PCBNew and CvPCB fail with the shared library error. No directory contains a space. I have checked the permissions of _pcbnew.kiface (which is complained as not found) and _eeschema.kiface (which has no complaints when loading eeschema.exe) and see no differences in permissions. I am attempting to load as administrator. Given the software is reporting a missing file that exists, what is the issue? Not that it necessarily makes any difference, but I am using the bzr-win-zip-2.6b1-1 binaries to pull (checkout) the source. This is not the cause of any issue since building was not a problem. Regards, Jason What should work is described below. I do not know why it is not working for you, you will have to determine that. The program is a process. The process consists on Windows of an *.exe and one or more DLLs. For all but kicad.exe, there may be one kicad DLL which has the *.kiface file extension. So pcbnew.exe will have its DLL named _pcbnew.kiface. eeschema.exe will have _eeschema.kiface. kicad.exe may also use _pcbnew.kiface, but can also use _eeschema.kiface concurrently or alone as well, plus others. The *.kiface files are found by examining the full path of the *.exe from within the *.exe code. That path is used to find the *.kiface file(s). This means that if you want to run kicad.exe, then all the *.kiface files that you will be loading must also be in that same directory. On linux if I do this from /usr/local/bin: $ dir kicad pcbnew eeschema *.kiface _cvpcb.kiface eeschema _eeschema.kiface _gerbview.kiface kicad _pcb_calculator.kiface pcbnew _pcbnew.kiface _pl_editor.kiface they all show in the same directory on linux, where kicad.exe is named kicad. Take care that you are then actually launching the copy of kicad.exe that you think you are. Maybe do it from the command line with full path as a test without the batch file, then examine what the batch file is doing in comparison. If you verify all the pieces are in place and it still fails with that same curious error message, we'll have to look at the wxWidgets code in more detail. That error message is a bit curious, as it essentially says that it succeeded. At that point we'd need to roll up our sleeves on Windows. Dick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
Le 27/06/2014 15:46, Dick Hollenbeck a écrit : On 06/26/2014 04:14 PM, Jason Whiteman wrote: Team, I am new to the dev group and have compiled my first windows binaries today based on what was pulled using kicad-winbuilder-3.4 (Kicad BZR build 4955). The binaries were created fine - and I was able to load kicad.exe using RunKicad.bat My issue is the error: Failed to load shared library 'Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin\_pcbnew.kiface' (error 0: the operation completed successfully.) I have searched for this error and see it is not uncommon. However, in all threads I have read - the problem was with the makefile failing to copy the _*.kiface files to the kicad/bin directory. This is not the case here. I see the files have landed there: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 01:59 PM 6,596,731 _cvpcb.kiface 06/26/2014 01:59 PM 6,728,781 _eeschema.kiface 06/26/2014 01:59 PM 2,771,868 _gerbview.kiface 06/26/2014 01:59 PM17,465,298 _pcbnew.kiface 06/26/2014 01:59 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 01:59 PM 2,463,434 _pl_editor.kiface EEschema can load, pcb_calculator loads, bitmap2component loads, gerbview loads. However both PCBNew and CvPCB fail with the shared library error. No directory contains a space. I have checked the permissions of _pcbnew.kiface (which is complained as not found) and _eeschema.kiface (which has no complaints when loading eeschema.exe) and see no differences in permissions. I am attempting to load as administrator. Given the software is reporting a missing file that exists, what is the issue? Not that it necessarily makes any difference, but I am using the bzr-win-zip-2.6b1-1 binaries to pull (checkout) the source. This is not the cause of any issue since building was not a problem. Regards, Jason What should work is described below. I do not know why it is not working for you, you will have to determine that. The program is a process. The process consists on Windows of an *.exe and one or more DLLs. For all but kicad.exe, there may be one kicad DLL which has the *.kiface file extension. So pcbnew.exe will have its DLL named _pcbnew.kiface. eeschema.exe will have _eeschema.kiface. kicad.exe may also use _pcbnew.kiface, but can also use _eeschema.kiface concurrently or alone as well, plus others. The *.kiface files are found by examining the full path of the *.exe from within the *.exe code. That path is used to find the *.kiface file(s). This means that if you want to run kicad.exe, then all the *.kiface files that you will be loading must also be in that same directory. On linux if I do this from /usr/local/bin: $ dir kicad pcbnew eeschema *.kiface _cvpcb.kiface eeschema _eeschema.kiface _gerbview.kiface kicad _pcb_calculator.kiface pcbnew _pcbnew.kiface _pl_editor.kiface they all show in the same directory on linux, where kicad.exe is named kicad. Take care that you are then actually launching the copy of kicad.exe that you think you are. Maybe do it from the command line with full path as a test without the batch file, then examine what the batch file is doing in comparison. If you verify all the pieces are in place and it still fails with that same curious error message, we'll have to look at the wxWidgets code in more detail. That error message is a bit curious, as it essentially says that it succeeded. At that point we'd need to roll up our sleeves on Windows. Dick Jason , Winbuilder build Kicad with option KICAD_SCRIPTING_WXPYTHON=ON. Therefore Cvpcb and mainly Pcbnew need wxPython and Python libs. If only Pcbnew (and Cvpcb) does not run ( _pcbnew.kiface exists but fails) I am pretty sure you have an issue with python (_pcbnew.kiface runs OK, but fails when trying to load python libraries or wxPython libs). kicad/bin *should contain* python and wxPython files (at least python.exe, libpython2.7.dll ./dll, ./lib, ./pylib) which are installed by winbuilder. FYI on my PC, wxPython libs are in winbuilder\kicad\bin\pylib\wx Moreever PYTHONHOME and PYTHONPATH should be set. This is mainly the purpose of lines: SET PYTHONHOME=%CD% SET PYTHONPATH=%CD% in RunKicad.bat. If you edit KicadWinBuilder.cmake and set KICAD_SCRIPTING_WXPYTHON=OFF and rebuild Kicad, Pcbnew and Cvpcb binaries do not use python at load time and should run. However, if there is an issue in python installation, footprint wizards and other python scripts will not run. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
Thanks for the feedback. Regarding Python, the PYTHONHOME and PYTHONPATH variables I believe are set in setenv.bat SET PATH_ENV_BASE=%CD%\env SET PATH_PY=%PATH_ENV_BASE%\python SET PYTHONHOME=%PATH_PY% SET PYTHONPATH=%PYTHONHOME% When I look in ./env/python, I see python.exe and its associated dll. Python works when I execute from within the home path, so I believe that should be ok. The options set by the makefile (shown during build process) are: KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON PYTHON_ROOT_DIR=Y:/Kicad_Buid/kicad- ... (I have a screenshot of the compile rest is cut off, but assume this is OK) BUILD_GITHUB_PLUGIN=ON One item to note: the help/documentation portion of the compile failed - something I was not concerned about. Is the help necessary for proper a proper load of the binary? My previous email did not display all files in the bin directory as I was focused on the _*.kiface files. The full listing (which shows python and other dlls landed fine) is as follows: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 05:20 PMDIR . 06/26/2014 05:20 PMDIR .. 06/26/2014 05:19 PM 803,328 bitmap2component.exe 06/26/2014 05:19 PM 434,176 cvpcb.exe 06/26/2014 05:20 PMDIR dll 06/26/2014 05:19 PM 854,016 dxf2idf.exe 06/26/2014 05:19 PM 485,888 eeschema.exe 06/26/2014 05:19 PM 485,376 gerbview.exe 06/26/2014 05:19 PM 436,736 idf2vrml.exe 06/26/2014 05:19 PM57,344 idfcyl.exe 06/26/2014 05:19 PM46,080 idfrect.exe 06/26/2014 09:42 AMDIR include 06/26/2014 05:19 PM 938,496 kicad.exe 06/26/2014 09:42 AMDIR lib 06/26/2014 02:24 AM 114,710 libbz2.dll 04/13/2013 05:06 PM 1,863,207 libpython2.7.dll 06/26/2014 05:19 PM 485,888 pcbnew.exe 06/26/2014 05:19 PM 485,376 pcb_calculator.exe 06/26/2014 05:19 PM 434,688 pl_editor.exe 06/26/2014 05:20 PMDIR pylib 04/13/2013 05:06 PM97,183 python.exe 06/26/2014 09:42 AMDIR scripting 06/26/2014 05:20 PM 3,789,000 wxbase300u_gcc_cm.dll 06/26/2014 05:20 PM 501,053 wxbase300u_net_gcc_cm.dll 06/26/2014 05:20 PM 285,311 wxbase300u_xml_gcc_cm.dll 06/26/2014 05:20 PM 3,168,534 wxmsw300u_adv_gcc_cm.dll 06/26/2014 05:20 PM 1,044,179 wxmsw300u_aui_gcc_cm.dll 06/26/2014 05:20 PM10,494,221 wxmsw300u_core_gcc_cm.dll 06/26/2014 05:20 PM 270,107 wxmsw300u_gl_gcc_cm.dll 06/26/2014 05:20 PM 1,537,596 wxmsw300u_html_gcc_cm.dll 06/26/2014 05:20 PM 320,341 wxmsw300u_media_gcc_cm.dll 06/26/2014 05:20 PM 1,621,339 wxmsw300u_propgrid_gcc_cm.dll 06/26/2014 05:20 PM 874,639 wxmsw300u_ribbon_gcc_cm.dll 06/26/2014 05:20 PM 2,662,331 wxmsw300u_richtext_gcc_cm.dll 06/26/2014 05:20 PM 3,153,480 wxmsw300u_stc_gcc_cm.dll 06/26/2014 05:20 PM 476,055 wxmsw300u_webview_gcc_cm.dll 06/26/2014 05:20 PM 2,379,160 wxmsw300u_xrc_gcc_cm.dll 06/26/2014 05:19 PM 6,596,731 _cvpcb.kiface 06/26/2014 05:19 PM 6,728,036 _eeschema.kiface 06/26/2014 05:19 PM 2,771,868 _gerbview.kiface 06/26/2014 05:19 PM17,465,298 _pcbnew.kiface 06/26/2014 05:20 PM17,442,611 _pcbnew.pyd 06/26/2014 05:19 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 05:19 PM 2,463,434 _pl_editor.kiface Since the initial report, I rolled over to build 4956 - still see the same error. I can try KICAD_SCRIPTING_WXPYTHON=OFF as a debug step. Regards, Jason On Fri, Jun 27, 2014 at 9:31 AM, jp charras jp.char...@wanadoo.fr wrote: Le 27/06/2014 15:46, Dick Hollenbeck a écrit : On 06/26/2014 04:14 PM, Jason Whiteman wrote: Team, I am new to the dev group and have compiled my first windows binaries today based on what was pulled using kicad-winbuilder-3.4 (Kicad BZR build 4955). The binaries were created fine - and I was able to load kicad.exe using RunKicad.bat My issue is the error: Failed to load shared library 'Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin\_pcbnew.kiface' (error 0: the operation completed successfully.) I have searched for this error and see it is not uncommon. However, in all threads I have read - the problem was with the makefile failing to copy the _*.kiface files to the kicad/bin directory. This is not the case here. I see the files have landed there: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 01:59 PM 6,596,731 _cvpcb.kiface 06/26/2014 01:59 PM 6,728,781 _eeschema.kiface 06/26/2014 01:59 PM 2,771,868 _gerbview.kiface 06/26/2014 01:59 PM17,465,298 _pcbnew.kiface 06/26/2014 01:59 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 01:59 PM 2,463,434
Re: [Kicad-developers] Build 4955 - Failed to load shared library
Jason, Likely it will work without python. Likely the _pcbnew.kiface cannot be loaded because something it needs cannot be found. While same path is used to find _pcbnew.kiface from kicad.exe, the technique used to load _pcbnew.kiface is done by Windows, not us. All its DLL dependencies must be met before it can be considered loadable or loaded. I think Windows still uses the *PATH* environment variable for this. I don't see where the PATH environment variable is being set in your batch file, it needs to point to the python.dll at least. On 06/27/2014 09:58 AM, Jason Whiteman wrote: Thanks for the feedback. Regarding Python, the PYTHONHOME and PYTHONPATH variables I believe are set in setenv.bat SET PATH_ENV_BASE=%CD%\env SET PATH_PY=%PATH_ENV_BASE%\python SET PYTHONHOME=%PATH_PY% SET PYTHONPATH=%PYTHONHOME% When I look in ./env/python, I see python.exe and its associated dll. Python works when I execute from within the home path, so I believe that should be ok. The options set by the makefile (shown during build process) are: KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON PYTHON_ROOT_DIR=Y:/Kicad_Buid/kicad- ... (I have a screenshot of the compile rest is cut off, but assume this is OK) BUILD_GITHUB_PLUGIN=ON One item to note: the help/documentation portion of the compile failed - something I was not concerned about. Is the help necessary for proper a proper load of the binary? My previous email did not display all files in the bin directory as I was focused on the _*.kiface files. The full listing (which shows python and other dlls landed fine) is as follows: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 05:20 PMDIR . 06/26/2014 05:20 PMDIR .. 06/26/2014 05:19 PM 803,328 bitmap2component.exe 06/26/2014 05:19 PM 434,176 cvpcb.exe 06/26/2014 05:20 PMDIR dll 06/26/2014 05:19 PM 854,016 dxf2idf.exe 06/26/2014 05:19 PM 485,888 eeschema.exe 06/26/2014 05:19 PM 485,376 gerbview.exe 06/26/2014 05:19 PM 436,736 idf2vrml.exe 06/26/2014 05:19 PM57,344 idfcyl.exe 06/26/2014 05:19 PM46,080 idfrect.exe 06/26/2014 09:42 AMDIR include 06/26/2014 05:19 PM 938,496 kicad.exe 06/26/2014 09:42 AMDIR lib 06/26/2014 02:24 AM 114,710 libbz2.dll 04/13/2013 05:06 PM 1,863,207 libpython2.7.dll 06/26/2014 05:19 PM 485,888 pcbnew.exe 06/26/2014 05:19 PM 485,376 pcb_calculator.exe 06/26/2014 05:19 PM 434,688 pl_editor.exe 06/26/2014 05:20 PMDIR pylib 04/13/2013 05:06 PM97,183 python.exe 06/26/2014 09:42 AMDIR scripting 06/26/2014 05:20 PM 3,789,000 wxbase300u_gcc_cm.dll 06/26/2014 05:20 PM 501,053 wxbase300u_net_gcc_cm.dll 06/26/2014 05:20 PM 285,311 wxbase300u_xml_gcc_cm.dll 06/26/2014 05:20 PM 3,168,534 wxmsw300u_adv_gcc_cm.dll 06/26/2014 05:20 PM 1,044,179 wxmsw300u_aui_gcc_cm.dll 06/26/2014 05:20 PM10,494,221 wxmsw300u_core_gcc_cm.dll 06/26/2014 05:20 PM 270,107 wxmsw300u_gl_gcc_cm.dll 06/26/2014 05:20 PM 1,537,596 wxmsw300u_html_gcc_cm.dll 06/26/2014 05:20 PM 320,341 wxmsw300u_media_gcc_cm.dll 06/26/2014 05:20 PM 1,621,339 wxmsw300u_propgrid_gcc_cm.dll 06/26/2014 05:20 PM 874,639 wxmsw300u_ribbon_gcc_cm.dll 06/26/2014 05:20 PM 2,662,331 wxmsw300u_richtext_gcc_cm.dll 06/26/2014 05:20 PM 3,153,480 wxmsw300u_stc_gcc_cm.dll 06/26/2014 05:20 PM 476,055 wxmsw300u_webview_gcc_cm.dll 06/26/2014 05:20 PM 2,379,160 wxmsw300u_xrc_gcc_cm.dll 06/26/2014 05:19 PM 6,596,731 _cvpcb.kiface 06/26/2014 05:19 PM 6,728,036 _eeschema.kiface 06/26/2014 05:19 PM 2,771,868 _gerbview.kiface 06/26/2014 05:19 PM17,465,298 _pcbnew.kiface 06/26/2014 05:20 PM17,442,611 _pcbnew.pyd 06/26/2014 05:19 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 05:19 PM 2,463,434 _pl_editor.kiface Since the initial report, I rolled over to build 4956 - still see the same error. I can try KICAD_SCRIPTING_WXPYTHON=OFF as a debug step. Regards, Jason On Fri, Jun 27, 2014 at 9:31 AM, jp charras jp.char...@wanadoo.fr mailto:jp.char...@wanadoo.fr wrote: Le 27/06/2014 15:46, Dick Hollenbeck a écrit : On 06/26/2014 04:14 PM, Jason Whiteman wrote: Team, I am new to the dev group and have compiled my first windows binaries today based on what was pulled using kicad-winbuilder-3.4 (Kicad BZR build 4955). The binaries were created fine - and I was able to load kicad.exe using RunKicad.bat My issue is the error: Failed to load shared library
Re: [Kicad-developers] Build 4955 - Failed to load shared library
On 27.06.2014 17:13, Dick Hollenbeck wrote: Jason, Likely it will work without python. Likely the _pcbnew.kiface cannot be loaded because something it needs cannot be found. While same path is used to find _pcbnew.kiface from kicad.exe, the technique used to load _pcbnew.kiface is done by Windows, not us. All its DLL dependencies must be met before it can be considered loadable or loaded. Hi Dick/Jason You could try this tool: http://dependencywalker.com/ to check what are the Kicad's DLL dependencies under Windows and what is missing. Regards, Tom ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
On 06/27/2014 10:20 AM, Tomasz Wlostowski wrote: On 27.06.2014 17:13, Dick Hollenbeck wrote: Jason, Likely it will work without python. Likely the _pcbnew.kiface cannot be loaded because something it needs cannot be found. While same path is used to find _pcbnew.kiface from kicad.exe, the technique used to load _pcbnew.kiface is done by Windows, not us. All its DLL dependencies must be met before it can be considered loadable or loaded. Hi Dick/Jason You could try this tool: http://dependencywalker.com/ to check what are the Kicad's DLL dependencies under Windows and what is missing. Regards, Tom Yep, that's the big hammer. But setting the PATH to the python*.dll will likely be the quicker fix. And of course that should be an additive change. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
Paths are set as follows (newline inserted in every 25 chars - windows console cut/paste): Path=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin;Y:\Kicad_Buil d\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin;Y:\Kicad_Build\kic ad-winbuilder-3.4\env\bazaar;Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin;Y :\Kicad_Build\kicad-winbuilder-3.4\env\python;Y:\Kicad_Build\kicad-winbuilder-3. 4\env\swig\swigwin-2.0.10;Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee;Y:\Kicad_B uild\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin;Y:\Kicad_Build\kicad-winb uilder-3.4\env\libxml2-2.7.8.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\i conv-1.9.2.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin;Y:\K icad_Build\kicad-winbuilder-3.4\kicad\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\ki cad;C:\windows\System32 PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.RB;.RBW PATH_BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar PATH_CMAKE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x8 6\bin PATH_ENV_BASE=Y:\Kicad_Build\kicad-winbuilder-3.4\env PATH_ICONV=Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin PATH_KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin PATH_KICAD_ROOT=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad PATH_MINGW=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin PATH_PATCH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin PATH_PROFILE=Y:\Kicad_Build\kicad-winbuilder-3.4\profile PATH_PY=Y:\Kicad_Build\kicad-winbuilder-3.4\env\python PATH_SWIG=Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10 PATH_TEE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee PATH_TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp PATH_TMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\tmp PATH_WIN=C:\windows\System32 PATH_XML2=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin PATH_XSLT=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin PATH_ZLIB=Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin PSModulePath=C:\windows\system32\WindowsPowerShell\v1.0\Modules\ PYTHONPATH=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin I believe python's dll is in the path. Regards, Jason On Fri, Jun 27, 2014 at 10:29 AM, Dick Hollenbeck d...@softplc.com wrote: On 06/27/2014 10:20 AM, Tomasz Wlostowski wrote: On 27.06.2014 17:13, Dick Hollenbeck wrote: Jason, Likely it will work without python. Likely the _pcbnew.kiface cannot be loaded because something it needs cannot be found. While same path is used to find _pcbnew.kiface from kicad.exe, the technique used to load _pcbnew.kiface is done by Windows, not us. All its DLL dependencies must be met before it can be considered loadable or loaded. Hi Dick/Jason You could try this tool: http://dependencywalker.com/ to check what are the Kicad's DLL dependencies under Windows and what is missing. Regards, Tom Yep, that's the big hammer. But setting the PATH to the python*.dll will likely be the quicker fix. And of course that should be an additive change. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
On 06/27/2014 11:27 AM, Jason Whiteman wrote: Paths are set as follows (newline inserted in every 25 chars - windows console cut/paste): Path=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin;Y:\Kicad_Buil d\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin;Y:\Kicad_Build\kic ad-winbuilder-3.4\env\bazaar;Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin;Y :\Kicad_Build\kicad-winbuilder-3.4\env\python;Y:\Kicad_Build\kicad-winbuilder-3. 4\env\swig\swigwin-2.0.10;Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee;Y:\Kicad_B uild\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin;Y:\Kicad_Build\kicad-winb uilder-3.4\env\libxml2-2.7.8.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\i conv-1.9.2.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin;Y:\K icad_Build\kicad-winbuilder-3.4\kicad\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\ki cad;C:\windows\System32 PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.RB;.RBW PATH_BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar PATH_CMAKE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x8 6\bin PATH_ENV_BASE=Y:\Kicad_Build\kicad-winbuilder-3.4\env PATH_ICONV=Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin PATH_KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin PATH_KICAD_ROOT=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad PATH_MINGW=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin PATH_PATCH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin PATH_PROFILE=Y:\Kicad_Build\kicad-winbuilder-3.4\profile PATH_PY=Y:\Kicad_Build\kicad-winbuilder-3.4\env\python PATH_SWIG=Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10 PATH_TEE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee PATH_TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp PATH_TMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\tmp PATH_WIN=C:\windows\System32 PATH_XML2=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin PATH_XSLT=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin PATH_ZLIB=Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin PSModulePath=C:\windows\system32\WindowsPowerShell\v1.0\Modules\ PYTHONPATH=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin I believe python's dll is in the path. Please name that path explicitly to confirm. This is not a matter of faith. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
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. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
On 06/27/2014 12:01 PM, Brian Sidebotham 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. Brian, thanks for your involvement. I am now bowing out. I just wanted us to remember that it loads and runs fine under pcbnew.exe, and not kicad.exe. Your comment about setting the environment differently probably pertains to the difference in loading results also. Perhaps there's a difference in how the environment is setup for the specific process. Remember that the environment when the process runs, is what's critical. A batch file can add or remove settings to the environment that it starts with, before the process runs. So simply getting a snapshot from the registry is not necessarily sufficient to describe the runtime environment variable values that any particular process sees. Environment varialbe PATH is still my biggest suspicion, in concert with a difference in launching methodology. Out, Dick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
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.sidebot...@gmail.com 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. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build 4955 - Failed to load shared library
Thanks again for the continued support from the list. All previous environment snapshots I have sent were after running the setenv.bat script. My methodology for loading pcbnew is to try running direct from ./kicad/bin (from a sentenv.bat load) and also from using RunKicad.bat which loads kicad.exe first. I have sent bits and pieces of my environment as it applies to the suggested assumed missing dependency. Here is the full environment ( C:\ set env.txt- env.txt results) slightly censored only for what looks a mentor graphics key. Otherwise as-is. Therefore, there is some noise from other env variables for other packages. However, everything fed to kicad.exe and pcbnew.exe is below as a result of setenv.bat. ACTEL_FOR_ALTIUM_OVERRIDE= ADSK_3DSMAX_x64_2012=C:\Program Files\Autodesk\3ds Max Design 2012\ ALLUSERSPROFILE=C:\ProgramData AltiumPath=C:\Program Files (x86)\Altium Designer S09 Viewer\System AMDAPPSDKROOT=C:\Program Files (x86)\AMD APP\ APPDATA=C:\Users\MY-COMPUTER\AppData\Roaming AVR32_HOME=Y:\WinAVR-20100110 BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\bzr.exe BZR_HOME=Y:\Kicad_Build\kicad-winbuilder-3.4\profile BZR_PLUGIN_PATH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\plugins CALLDIR=Y:\Kicad_Build\kicad-winbuilder-3.4 CLASSPATH=.;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip CM2012DIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=MY-COMPUTER ComSpec=C:\windows\system32\cmd.exe configsetroot=C:\windows\ConfigSetRoot EDPATH=Y:\WATCOM\EDDAT FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Users\MY-COMPUTER ICONV_VER=1.9.2 ILBDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ ILLDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ ILMDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\ INCLUDE=Y:\WATCOM\H;Y:\WATCOM\H\NT;Y:\WATCOM\H\NT\DIRECTX;Y:\WATCOM\H\NT\DDK KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad LenovoTestLogFile=preload.log LenovoTestPath=C:\prdv10\ LMC_HOME=E:\Xilinx91i\smartmodel\nt64\installed_nt64 LM_LICENSE_FILE=c:\lattice_license\license.dat LOCALAPPDATA=C:\Users\MY-COMPUTER\AppData\Local LOGONSERVER=\\MY-COMPUTER MGLS_LICENSE_FILE=c:\MentorGraphics\[censored - looks like a key].txt NUMBER_OF_PROCESSORS=2 OMP_NUM_THREADS=2 OS=Windows_NT Path=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar;Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\python;Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10;Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad;C:\windows\System32 PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.RB;.RBW PATH_BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar PATH_CMAKE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin PATH_ENV_BASE=Y:\Kicad_Build\kicad-winbuilder-3.4\env PATH_ICONV=Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin PATH_KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin PATH_KICAD_ROOT=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad PATH_MINGW=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin PATH_PATCH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin PATH_PROFILE=Y:\Kicad_Build\kicad-winbuilder-3.4\profile PATH_PY=Y:\Kicad_Build\kicad-winbuilder-3.4\env\python PATH_SWIG=Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10 PATH_TEE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee PATH_TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp PATH_TMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\tmp PATH_WIN=C:\windows\System32 PATH_XML2=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin PATH_XSLT=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin PATH_ZLIB=Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=AMD64 Family 20 Model 1 Stepping 0, AuthenticAMD PROCESSOR_LEVEL=20 PROCESSOR_REVISION=0100 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=KiCad-Winbuilder$P$G PSModulePath=C:\windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public PYTHONHOME=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin PYTHONPATH=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin QTJAVA=C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip QUARTUS_ROOTDIR=C:\altera\12.1_free\quartus
[Kicad-developers] Build 4955 - Failed to load shared library
Team, I am new to the dev group and have compiled my first windows binaries today based on what was pulled using kicad-winbuilder-3.4 (Kicad BZR build 4955). The binaries were created fine - and I was able to load kicad.exe using RunKicad.bat My issue is the error: Failed to load shared library 'Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin\_pcbnew.kiface' (error 0: the operation completed successfully.) I have searched for this error and see it is not uncommon. However, in all threads I have read - the problem was with the makefile failing to copy the _*.kiface files to the kicad/bin directory. This is not the case here. I see the files have landed there: Directory of Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin 06/26/2014 01:59 PM 6,596,731 _cvpcb.kiface 06/26/2014 01:59 PM 6,728,781 _eeschema.kiface 06/26/2014 01:59 PM 2,771,868 _gerbview.kiface 06/26/2014 01:59 PM17,465,298 _pcbnew.kiface 06/26/2014 01:59 PM 2,219,655 _pcb_calculator.kiface 06/26/2014 01:59 PM 2,463,434 _pl_editor.kiface EEschema can load, pcb_calculator loads, bitmap2component loads, gerbview loads. However both PCBNew and CvPCB fail with the shared library error. No directory contains a space. I have checked the permissions of _pcbnew.kiface (which is complained as not found) and _eeschema.kiface (which has no complaints when loading eeschema.exe) and see no differences in permissions. I am attempting to load as administrator. Given the software is reporting a missing file that exists, what is the issue? Not that it necessarily makes any difference, but I am using the bzr-win-zip-2.6b1-1 binaries to pull (checkout) the source. This is not the cause of any issue since building was not a problem. Regards, Jason ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
