kicad-developers team mailing list archive

[Brian Piccioni <brian@xxxxxxxxxxxxxxxxxxxxx>]

Wayne

Thanks for the additional information. I mentioned the compile warnings because they appear to be different from the ones I got when I compiled 32 bit.

As for MSVC, I am a big fan and can see the benefits of moving to it. One advantage was that you wouldn’t have to install MSYS2 and all the other issues associated with that such as keeping it updated and in sync with the distributions. 

Thanks again

Brian 

From: Wayne Stambaugh
Sent: October 21, 2019 10:31 AM
Subject: Re: [Kicad-developers] Issues building PCBNew on Windows10/Msys:fatal exception

Brian,

On 10/21/19 9:24 AM, Brian Piccioni wrote:
> I'm updating this email in case somebody else has a similar problem.
> 
>  
> 
> I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad.
> It appear to run fine, except when I run PCBNew from a mingw64 terminal
> I get
> 
>  
> 
> $ pcbnew
> 
> C:/msys64/mingw64/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> UserWarning: wxPython/wxWidgets release number mismatch
> 
>   warnings.warn("wxPython/wxWidgets release number mismatch")

You should always see this warning.  The msys2 wxPython release is 3.0.2
and the wxWidgets release is 3.0.4 which causes the version mismatch.
Again, AFAIK, there this does not create any issues other than the fact
that wxPython is dead and has been replaced with wxPhoenix.  wxPhoenix
is wxPython for Python 3.  Unfortunately, the wxPython folks broke the
build scripts for wxPhoenix which means that you cannot build it on
msys2.  This *is* going to be a problem in the not too distant future
for windows users unless we either fix the wxPhoenix build scripts for
msys2 or switch to the free version of msvc to create windows builds.  I
prefer the former but we may not have any choice depending on manpower.

> 
>  
> 
>  
> 
> Interestingly, compiling does not generate "release number mismatch"
> warnings as happened when I did a 32 bit build.
> 
>  
> 
> I do, however, get these warnings:
> 
>  
> 
> C:\kicad-source\pcbnew\..\include\common.h(357) : Warning 317:
> Specialization of non-template 'hash'.
> 
> C:\kicad-source\pcbnew\..\include\common.h(365) : Warning 317:
> Specialization of non-template 'less'.
> 
> class_board.h(45) : Warning 315: Nothing known about 'std::unique_ptr'.

These are known issues with the code generated by SWIG to build the
Python scripting module.  AFAIK, they do not present any issues.

Cheers,

Wayne

> 
>  
> 
>  
> 
> (these are the only warnings I get compiling all of Kicad).
> 
>  
> 
> I will recompile wxPython and see if the PCBNew warnings go away though
> it is not pressing as everything works.
> 
>  
> 
> Thanks again
> 
>  
> 
> Brian
> 
>  
> 
> *From: *Wayne Stambaugh <mailto:stambaughw@xxxxxxxxx>
> *Sent: *October 20, 2019 10:09 AM
> *To: *kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> *Subject: *Re: [Kicad-developers] Issues building PCBNew on Windows
> 10/Msys:fatal exception
> 
>  
> 
> Hi Brian,
> 
>  
> 
> There is a long litany of things that can go wrong with msys2 builds but
> 
> I do not believe that the wxPython/wxWidgets mismatch is the problem.
> 
> Typically when I see issues like this, there has been a new gcc version
> 
> released and only one of the two dependency libraries have been compiled
> 
> with the new compiler which causes issues.  It's been a while but the
> 
> last time this happened, I had to recompile the wxPython package.  I
> 
> also noticed you are attempting to use 32 builds for debugging.  I
> 
> highly recommend that you debug using 64 bit builds.  Debug builds on
> 
> msys2 are massive and you will likely run into memory limit issues.  I
> 
> hope this helps.
> 
>  
> 
> Cheers,
> 
>  
> 
> Wayne
> 
>  
> 
> On 10/19/19 5:36 PM, Brian Piccioni wrote:
> 
>> Sorry if this is a bit long and thanks in advance for the help. I
> 
>> decided to move to a new laptop and create a debug version of Kicad so I
> 
>> can work on integrating my software. I believe I carefully followed the
> 
>> build instructions I suspect this may be related to a version mismatch
> 
>> but I don’t know how to fix it.
> 
>>
> 
>>  
> 
>>
> 
>> I installed Msys2, downloaded Kicad source and compiled a debug build.
> 
>> It compiled without errors but I get a warning
> 
>>
> 
>>  
> 
>>
> 
>>
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> 
>> UserWarning: wxPython/wxWidgets release number mismatch
> 
>>
> 
>>          warnings.warn("wxPython/wxWidgets release number mismatch")
> 
>>
> 
>>  
> 
>>
> 
>> I get the same error building the release and debug versions and the
> 
>> release version appears to work fine, except for complaints about
> 
>>
> 
>> version mismatch.
> 
>>
> 
>>  
> 
>>
> 
>> However, with the debug build I can run Kicad and invoke eeSchema and
> 
>> all the other applications from the Kicad menu except
> 
>>
> 
>> PCBNew and  the symbol editor. When I run these, I get errors:
> 
>>
> 
>>  
> 
>>
> 
>> Application failed to load:
> 
>>
> 
>>          IO_ERROR: Failed to load kiface library
> 
>> "C:\msys32\mingw32\bin\_pcbnew.kiface".
> 
>>
> 
>> from kiway.cpp : KiFACE() line:213
> 
>>
> 
>>  
> 
>>
> 
>> If I run PCBNew from the debug directory I get the same result but with
> 
>> details I can copy.
> 
>>
> 
>>  
> 
>>
> 
>> Details:
> 
>>
> 
>> 17:18:15: Failed to load shared library
> 
>> 'C:\kicad-source\build\debug\pcbnew\_pcbnew.kiface' (error 127: the
> 
>> specified procedure could not be found.)
> 
>>
> 
>> 17:18:15: IO_ERROR: Failed to load kiface library
> 
>> “C:\kicad-source\build\debug\pcbnew\_pcbnew.kiface”.
> 
>>
> 
>>  
> 
>>
> 
>> This PC has 32 GB of DRAM installed and
> 
>> 'C:\msys32\mingw32\bin\_pcbnew.kiface' is present.
> 
>>
> 
>>  
> 
>>
> 
>> When I run PCBNew standalone in msys2, I get this message
> 
>>
> 
>>  
> 
>>
> 
>> $ pcbnew
> 
>>
> 
>>
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> 
>> UserWarning: wxPython/wxWidgets release number mismatch
> 
>>
> 
>>          warnings.warn("wxPython/wxWidgets release number mismatch")
> 
>>
> 
>> Exception code=0xc0000005 flags=0x0 at 0x05A28FDE. Access violation -
> 
>> attempting to read data at address 0x00000000
> 
>>
> 
>> Segmentation fault
> 
>>
> 
>>  
> 
>>
> 
>> When I run this command
> 
>>
> 
>> $ pacman -Qs wx   I get
> 
>>
> 
>> local/mingw-w64-i686-wxPython 3.0.2.0-9
> 
>>
> 
>>          A wxWidgets GUI toolkit for Python (mingw-w64)
> 
>>
> 
>> local/mingw-w64-i686-wxWidgets 3.0.4-3
> 
>>
> 
>>          A C++ library that lets developers create applications for
> 
>> Windows, Linux and UNIX (mingw-w64)
> 
>>
> 
>>  
> 
>>
> 
>> Here is the version info:
> 
>>
> 
>>  
> 
>>
> 
>> Application: KiCad
> 
>>
> 
>> Version: 5.99.0-unknown, debug build
> 
>>
> 
>> Libraries:
> 
>>
> 
>>     wxWidgets 3.0.4
> 
>>
> 
>>     libcurl/7.66.0 OpenSSL/1.1.1d (Schannel) zlib/1.2.11 brotli/1.0.7
> 
>> libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.39.2
> 
>>
> 
>> Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
> 
>> wxMSW
> 
>>
> 
>> Build Info:
> 
>>
> 
>>     Build date: Oct 19 2019 09:19:25
> 
>>
> 
>>     wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
> 
>>
> 
>>     Boost: 1.71.0
> 
>>
> 
>>     OpenCASCADE Community Edition: 6.9.1
> 
>>
> 
>>     Curl: 7.66.0
> 
>>
> 
>>     Compiler: GCC 9.2.0 with C++ ABI 1013
> 
>>
> 
>>  
> 
>>
> 
>> Build settings:
> 
>>
> 
>>     KICAD_SCRIPTING=ON
> 
>>
> 
>>     KICAD_SCRIPTING_MODULES=ON
> 
>>
> 
>>     KICAD_SCRIPTING_PYTHON3=OFF
> 
>>
> 
>>     KICAD_SCRIPTING_WXPYTHON=ON
> 
>>
> 
>>     KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
> 
>>
> 
>>     KICAD_SCRIPTING_ACTION_MENU=ON
> 
>>
> 
>>     BUILD_GITHUB_PLUGIN=ON
> 
>>
> 
>>     KICAD_USE_OCE=ON
> 
>>
> 
>>     KICAD_USE_OCC=OFF
> 
>>
> 
>>     KICAD_SPICE=ON
> 
>>
> 
>>     KICAD_STDLIB_DEBUG=OFF
> 
>>
> 
>>     KICAD_STDLIB_LIGHT_DEBUG=OFF
> 
>>
> 
>>     KICAD_SANITIZE=OFF
> 
>>
> 
>>  
> 
>>
> 
>>  
> 
>>
> 
>>
> 
>> _______________________________________________
> 
>> Mailing list: https://launchpad.net/~kicad-developers
> 
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
> 
>> More help   : https://help.launchpad.net/ListHelp
> 
>>
> 
>  
> 
> _______________________________________________
> 
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
>  
> 

_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp