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] Spice netlist with netnumbers
@ jp charras, We wanted netlist with netnumbers to simulate the circuit using Ngspice. Ngspice is not able to recognize the netlist with netnames. Thanks Oscad team On Fri, Jun 27, 2014 at 5:20 AM, Rick Walker wal...@omnisterra.com wrote: Hi, I think the proper behavior is to use a net name if it was explicitly given in the schematic, otherwise use an automatically generated sequential integer with a possible prefix. Using net names instead net numbers allows a easy recognition of circuit lines. Thus, it is easier to write equations for to obtain graphs or executing meas scripts. Yes. If I label two signals final_output_p and final_output_m, I will expect to be able to graph them by those names. If I don't label them, I probably won't try to graph them in my simulation anyway. BTW, I have written a SPICE post processor that allows math expressions to be performed on the post processor piece-wise-linear output variables. You can add and subtract waveforms by saying things like: vnew = v1+v2/3 vnew2 = max(v1,v2) vint = integral(vnew + vnew2) The gr command will plot any expression or waveform. Multiple plots are separated by ; gr integral(delay(v1,10u)+max(v1,v3)); v5 There is a collection of measurement primitives. For instance you can measure the time of the nth zero crossing of a signal with t1=xcross(v1,3) If you wanted to know the value of v2 at that moment you could say: vm = v2(t1) It's very handy for evaluating the output of SPICE runs. https://www.omnisterra.com/walker/linux/post/ It uses the ascii plotting package: https://www.omnisterra.com/walker/linux/pdplot/intro.htm kind regards, -- Rick Walker ___ 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
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] Spice netlist with netnumbers
Hello Oscad team,
We wanted netlist with netnumbers to simulate the circuit using Ngspice.
Ngspice is not able to recognize the netlist with netnames.
I don't believe that is the case. Ngspice allows arbitrary
identifiers for node names. For example, this subckt runs fine
under the current ngspice release:
*
* transmission line model with skin loss
.subckt skinline in 0 out 0 z0=50 length=1 rdc=1 lint=1n
* hybrid sections at each end
x1 in x1in x1out x1eqout x1eqin thyb
x2 out x2in x2out x2eqout x2eqin thyb
* equalization circuits
x3 x1eqout x1eqin 0 skin6 length={length} rdc={rdc} lint={lint}
x4 x2eqout x2eqin 0 skin6 length={length} rdc={rdc} lint={lint}
* ballistic delay modelling
t1 x1out 0 x2in 0 td={length*lint/z0} Z0={z0}
t2 x2out 0 x1in 0 td={length*lint/z0} Z0={z0}
.ends skinline
*
Notice the use of names like x1equout and x2in to make it easy to
post process the nodes without using a graphical system.
I expect that the Oscad backend has some kind of historical limitation
to use integers for net names. This is not a limitation with Ngspice.
I suggest that kicad use the node names that the user gives them.
Any unnamed nets can be arbitrarily assigned sequential names
like node99 or just 99. Please do not override the explicit
names given in the schematic.
If the Oscad tools do not currently accept arbitrary ASCII strings for
node names, this should be fixed with a high priority. If the Oscad
internal bookkeeping requires integers for node numbers, then what is
needed is a simple symbol table to convert each incoming identifier to
an internal node number.
It will be very awkward if the end user cannot use symbolic node
names. This would break just about every modern tool flow that I know
of.
kind regards,
--
Rick Walker
___
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] [kicad-users] Re: Module editor upgrade
Mine also consistently crashes when switching to OpenGL and then opening the module editor from an empty PCB. I have used the GAL before (though maybe not the newest). This is on Ubuntu 12.04 64-bit with Intel integrated graphics. Backtrace and glxinfo attached. #0 0x7fffeb42a5e6 in EDA_DRAW_PANEL_GAL::GetBackend (this=0x5) at /home/kaspar/kicad_sources/branches/module_editor/include/class_draw_panel_gal.h:77 #1 0x7fffeb5a6f86 in FOOTPRINT_EDIT_FRAME::FOOTPRINT_EDIT_FRAME (this=0x299b440, aKiway=0x6d9b40, aParent=0x774d30) at /home/kaspar/kicad_sources/branches/module_editor/pcbnew/moduleframe.cpp:187 #2 0x7fffeb40a939 in PCB::IFACE::CreateWindow (this=0x7fffec030520, aParent=0x774d30, aClassId=5, aKiway=0x6d9b40, aCtlBits=2) at /home/kaspar/kicad_sources/branches/module_editor/pcbnew/pcbnew.cpp:135 #3 0x004739cf in KIWAY::Player (this=0x6d9b40, aFrameType=FRAME_PCB_MODULE_EDITOR, doCreate=true) at /home/kaspar/kicad_sources/branches/module_editor/common/kiway.cpp:291 #4 0x7fffeb56f9a1 in PCB_EDIT_FRAME::Process_Special_Functions (this=0x9bf2d0, event=...) at /home/kaspar/kicad_sources/branches/module_editor/pcbnew/edit.cpp:200 #5 0x76da0d35 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const, wxEvtHandler*, wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #6 0x76da0e9c in wxEventHashTable::HandleEvent(wxEvent, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #7 0x76da11d4 in wxEvtHandler::ProcessEvent(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #8 0x7fffeb84a182 in EDA_BASE_FRAME::ProcessEvent (this=0x9bf2d0, aEvent=...) at /home/kaspar/kicad_sources/branches/module_editor/common/basicframe.cpp:131 #9 0x76da1170 in wxEvtHandler::ProcessEvent(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 ---Type return to continue, or q return to quit--- #10 0x772ca9a9 in wxWindowBase::TryParent(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #11 0x77bc5e87 in wxAuiToolBar::OnLeftUp(wxMouseEvent) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-2.8.so.0 #12 0x76da0d35 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const, wxEvtHandler*, wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #13 0x76da0e9c in wxEventHashTable::HandleEvent(wxEvent, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #14 0x76da11d4 in wxEvtHandler::ProcessEvent(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #15 0x771fa878 in ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #16 0x759d7e78 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #17 0x753afca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x753c0d71 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x753c8d4e in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x753c9212 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x75af2231 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #22 0x759d6003 in gtk_propagate_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #23 0x759d6363 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ---Type return to continue, or q return to quit--- #24 0x7564acac in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #25 0x74ed2d13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x74ed3060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x74ed345a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x759d5397 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #29 0x771e77b8 in wxEventLoop::Run() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #30 0x7725e95b in wxAppBase::MainLoop() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #31 0x00455b39 in APP_KICAD::OnRun (this=0x714250) at /home/kaspar/kicad_sources/branches/module_editor/kicad/kicad.cpp:293 #32 0x76d51d4b in wxEntry(int, wchar_t**) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #33 0x0045534a in main (argc=1, argv=0x7fffea88) at /home/kaspar/kicad_sources/branches/module_editor/kicad/kicad.cpp:325 name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGIS_multisample,
Re: [Kicad-developers] [kicad-users] Re: Module editor upgrade
On 27 June 2014 17:16, Kaspar Emanuel kaspar.bu...@gmail.com wrote: Mine also consistently crashes when switching to OpenGL and then opening the module editor from an empty PCB. It actually doesn't matter what canvas I have it set to. It will crash when I try and open the module editor. ___ 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] [kicad-users] Re: Module editor upgrade
On 27 June 2014 17:23, Kaspar Emanuel kaspar.bu...@gmail.com wrote: On 27 June 2014 17:16, Kaspar Emanuel kaspar.bu...@gmail.com wrote: Mine also consistently crashes when switching to OpenGL and then opening the module editor from an empty PCB. It actually doesn't matter what canvas I have it set to. It will crash when I try and open the module editor. And it only happens with pcbnew started from the kicad launcher, not if using the pcbnew executable directly. ___ 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] [kicad-users] Re: Module editor upgrade
Got another segfault while trying to import a module. Backtrace attached. On 27 June 2014 18:52, Kaspar Emanuel kaspar.bu...@gmail.com wrote: On 27 June 2014 17:23, Kaspar Emanuel kaspar.bu...@gmail.com wrote: On 27 June 2014 17:16, Kaspar Emanuel kaspar.bu...@gmail.com wrote: Mine also consistently crashes when switching to OpenGL and then opening the module editor from an empty PCB. It actually doesn't matter what canvas I have it set to. It will crash when I try and open the module editor. And it only happens with pcbnew started from the kicad launcher, not if using the pcbnew executable directly. #0 0x7fffeec5ec33 in KIGFX::VIEW_GROUP::ViewDraw (this=0x49422e0, aLayer=56, aGal=0x1450f90) at /home/kaspar/kicad_sources/branches/module_editor/common/view/view_group.cpp:99 #1 0x7fffeec531cb in KIGFX::VIEW::draw (this=0x480ec30, aItem=0x49422e0, aLayer=56, aImmediate=false) at /home/kaspar/kicad_sources/branches/module_editor/common/view/view.cpp:624 #2 0x7fffeec54e19 in KIGFX::VIEW::drawItem::operator() (this=0x7fffafa0, aItem=0x49422e0) at /home/kaspar/kicad_sources/branches/module_editor/common/view/view.cpp:572 #3 0x7fffeec59b73 in RTreeKIGFX::VIEW_ITEM*, int, 2, float, 8, 4::SearchKIGFX::VIEW::drawItem (this=0x3356c60, a_node=0x4853dd0, a_rect=0x7fffaf00, a_visitor=..., a_foundCount=@0x7fffaf18: -19872) at /home/kaspar/kicad_sources/branches/module_editor/include/geometry/rtree.h:505 #4 0x7fffeec57b37 in RTreeKIGFX::VIEW_ITEM*, int, 2, float, 8, 4::SearchKIGFX::VIEW::drawItem (this=0x3356c60, a_min=0x7fffaf50, a_max=0x7fffaf60, a_visitor=...) at /home/kaspar/kicad_sources/branches/module_editor/include/geometry/rtree.h:159 ---Type return to continue, or q return to quit--- #5 0x7fffeec56278 in KIGFX::VIEW_RTREE::QueryKIGFX::VIEW::drawItem ( this=0x3356c60, aBounds=..., aVisitor=...) at /home/kaspar/kicad_sources/branches/module_editor/include/view/view_rtree.h:85 #6 0x7fffeec52f86 in KIGFX::VIEW::redrawRect (this=0x480ec30, aRect=...) at /home/kaspar/kicad_sources/branches/module_editor/common/view/view.cpp:592 #7 0x7fffeec53736 in KIGFX::VIEW::Redraw (this=0x480ec30) at /home/kaspar/kicad_sources/branches/module_editor/common/view/view.cpp:760 #8 0x7fffeecd0a93 in EDA_DRAW_PANEL_GAL::onPaint (this=0x1458bf0) at /home/kaspar/kicad_sources/branches/module_editor/common/draw_panel_gal.cpp:135 #9 0x772e3d35 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const, wxEvtHandler*, wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #10 0x772e40ff in wxEvtHandler::SearchDynamicEventTable(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #11 0x772e41b2 in wxEvtHandler::ProcessEvent(wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #12 0x7773c9aa in wxWindow::GtkSendPaintEvents() () ---Type return to continue, or q return to quit--- from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #13 0x7773ceb8 in ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #14 0x75f1ae78 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #15 0x75489ca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7549ad71 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x754a2d4e in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x754a3212 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x76035231 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #20 0x75f19660 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #21 0x75b75604 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #22 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #23 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ---Type return to continue, or q return to quit--- #24 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #25 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #26 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #27 0x75b755b3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #28 0x75b705a3 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #29 0x75b72741 in gdk_window_process_all_updates () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #30 0x75e9caf1 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #31 0x75b4fd56 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #32 0x751ccd13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x751cd060 in ?? () from
Re: [Kicad-developers] Module editor upgrade
Hi Orson The video ĺooks nice. :) I just tried to build it today, but it failed when I enabled the sripting. I don't know if you have tested that yourself, so I won't tell the details now. I did manage to build without scripting, but there are some segfaults. But I get no segfault by just switching to opengl. I get a segfault if I start pcbnew from the kicad app on a project. But if I open pcbnew directly it do not segfault and I am able to go to opengl and open the module editor just fine. But running from the kicad app, I get another bt compared to Kaspar, I have attached it. I happend when I hit the icon for the module editor in the top toolbar. Version: (2014-06-26 BZR 5056)-module_editor Release build wxWidgets: Version 3.0.1 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.9.0,STL containers,compatible with 2.8) Platform: Linux 3.15.1-1-ARCH x86_64, 64 bit, Little endian, wxGTK Boost version: 1.55.0 USE_WX_GRAPHICS_CONTEXT=OFF USE_WX_OVERLAY=OFF KICAD_SCRIPTING=OFF KICAD_SCRIPTING_MODULES=OFF KICAD_SCRIPTING_WXPYTHON=OFF USE_FP_LIB_TABLE=HARD_CODED_ON BUILD_GITHUB_PLUGIN=ON 2014-06-26 15:58 GMT+02:00 Maciej Sumiński maciej.sumin...@cern.ch: Ladies and gentlemen, We have just reached the next step of our development plan. We would like to offer you a refurbished module editor, extended with the GAL and the Tool Framework. Besides the new graphic engine, you will find there: - layer widget - to select the drawing layer before you start creating graphics (including Edge.Cuts layer) - drawing tools - already known from the layout editor (draggable items, point editor, line splitting, etc.) - copy and paste using reference points - feel the power of instant replication - align/distribute - to save you some time on precise mouse movements - pad enumeration tool - that is the missing piece in the lightning fast footprint creation process - DXF import - we do not blame you if you prefer other graphic utils (it is possible mostly due to efforts of Jean-Pierre Charras, the main author of DXF import code) We invite you to watch a short video, in which you may see the new features in action. To give you an example, there is a part on how to draw a QFN64 footprint in less than 2 minutes: https://vimeo.com/99235812 The code is available for testing in the repository: https://code.launchpad.net/~cern-kicad/kicad/module_editor After a period of testing, it will be merged to the product branch. You may help shortening the time by letting us know if everything works as expected. I feel obliged to say thank you to the KiCad community that gave us a few thoughts regarding improvements. We should ask you more often, you have great ideas. Regards, Orson ___ 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 $ gdb kicad GNU gdb (GDB) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-unknown-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from kicad...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/kicad warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /usr/lib/libthread_db.so.1. [New Thread 0x7fffe867c700 (LWP 29240)] [New Thread 0x7fffe7e7b700 (LWP 29241)] [New Thread 0x7fffe767a700 (LWP 29242)] [New Thread 0x7fffcebcc700 (LWP 29244)] [New Thread 0x7fffce3cb700 (LWP 29245)] [New Thread 0x7fffcdbca700 (LWP 29246)] Program received signal SIGSEGV, Segmentation fault. 0x7fffe680aca4 in KIGFX::VIEW::SetCenter(VECTOR2double const) () from /usr/bin/_pcbnew.kiface (gdb) bt #0 0x7fffe680aca4 in KIGFX::VIEW::SetCenter(VECTOR2double const) () from /usr/bin/_pcbnew.kiface #1 0x7fffe680c33c in KIGFX::VIEW::SetGAL(KIGFX::GAL*) () from /usr/bin/_pcbnew.kiface #2 0x7fffe687d72d in EDA_DRAW_PANEL_GAL::EDA_DRAW_PANEL_GAL(wxWindow*, int, wxPoint const, wxSize const, EDA_DRAW_PANEL_GAL::GalType) () from /usr/bin/_pcbnew.kiface #3 0x7fffe65180e6 in PCB_DRAW_PANEL_GAL::PCB_DRAW_PANEL_GAL(wxWindow*, int, wxPoint const, wxSize const,
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] Pl_Editor scrollbars
Coming from the 07-07-2013 BZR release for windows - the Pl_Editor is a new and welcome feature. I see the window defaults with the sheet border centered but the scroll bars are at max-right (for bottom scroll) and max-down (for side scroll). When zooming in, the center is zoomed (as expected) but the portion of the border which is now off screen since we've zoomed in to the right or bottom cannot be accessed because the scrollbars are pegged to full right and full bottom already. Therefore, zooming into the title block area does not appear possible unless there is another workaround I am unaware of. Actually - F4 seems to allow me to reorient the center. But the scrollbar behavior is still non-intuitive at best. Ultimately, the extents of the scrollbars should always follow the extent of the page (at a minimum) with possibly extra margin. Eeschema uses the same underlying scrollbar control functions and eeschema does not have an issue - so I suspect pl_editor_frame.cpp Comparing pl_editor_frame.cpp to schframe.cpp (eeschema's equiv) I see the following difference in BestZoom(): // PL_EDITOR Version dx = GetPageLayout().GetPageSettings().GetWidthIU(); dy = GetPageLayout().GetPageSettings().GetHeightIU(); // SCHFRAME Version dx = GetScreen()-GetPageSettings().GetWidthIU(); dy = GetScreen()-GetPageSettings().GetHeightIU(); = I'm wondering if the GetPageLayout() vs. GetScreen() in pl_editor_frame.cpp is causing the issue. Since, for another issue, I've switched to a debug build -- which is currently in the taking forever for a 1st build stage -- I do not yet have test results for the shotgun approach of swapping methods for dx and dy assignments. 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
