kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

I've had this problem the last couple of times that a new build of the
wxWidgets package was released.  You will have to checkout a copy of the
mingw package repo on github and rebuild the wxPython package with the
latest compiler (gcc 10) to fix the ABI warning.  It's not terribly
difficult just do the following:

* Launch the msys2 console.  This does not work with a mingw console.
* Run `cd /to/your/src/folder`
* Run `git clone https://github.com/msys2/MINGW-packages.git`
* Run `cd ./MINGW-packages/mingw-w64-wxPython`
* Run `makepkg-mingw`
* Wait a really long time for both 64 and 32 bit packages to build.
* Run `pacman -U mingw-w64-x86_64-wxPython-3.0.2.0-9-any.pkg.tar.xz` or
`pacman -U mingw-w64-i686-wxPython-3.0.2.0-9-any.pkg.tar.xz` depending
if you are using mingw64 or mingw32.
* Reconfigure your KiCad build.  You may have to do a clean configure.


On 5/25/20 9:33 AM, Brian Piccioni wrote:
> Unfortunately, while we seem to get past the libngspice-0.dll problem
> with the fix, the old workaround  for the python problem no longer works.
> 
> cmake -DCMAKE_BUILD_TYPE=Debug \
> -DKICAD_SCRIPTING=OFF\ <<<<<<<<<<<<<<<<<<<< I believe this used to get
> around the pyhton mismatch.
> -G "Eclipse CDT4 - Unix Makefiles" \
> -DCMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT=TRUE \
> -DCMAKE_PREFIX_PATH=C:/msys64/mingw64 \
> -DCMAKE_INSTALL_PREFIX=C:/msys64/mingw64 \
> -DDEFAULT_INSTALL_PATH=C:/msys64/mingw64 \
> -DMSYS=TRUE \
> ../kicad
> 
> 
> Throws the library mismatch error.
> 
> 
> $ cmake -DCMAKE_BUILD_TYPE=Debug \
>> -DKICAD_SCRIPTING=OFF\
>> -G "Eclipse CDT4 - Unix Makefiles" \
>> -DCMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT=TRUE \
>> -DCMAKE_PREFIX_PATH=C:/msys64/mingw64 \
>> -DCMAKE_INSTALL_PREFIX=C:/msys64/mingw64 \
>> -DDEFAULT_INSTALL_PATH=C:/msys64/mingw64 \
>> -DMSYS=TRUE \
>> ../kicad
> -- Eclipse version is set to 3.6 (Helios). Adjust CMAKE_ECLIPSE_VERSION
> if this is wrong.
> -- KiCad install dir: <C:/msys64/mingw64>
> -- Enabling warning -Wsuggest-override
> -- Enabling warning -Wduplicated-branches
> -- Enabling warning -Wduplicated-cond
> -- Enabling error for -Wvla
> -- Enabling warning -Wimplicit-fallthrough
> -- Enabling error for -Wreturn-type
> -- Enabling warning -Wshadow
> -- Check for installed GLEW -- found
> info: libngspice shared lib found: C:/msys64/mingw64/bin/libngspice-0.dll
> 
> -- Check for installed Python Interpreter -- found
> -- Python module install path: lib/python2.7/site-packages
> CMake Error at CMakeModules/FindwxPython.cmake:52 (message):
>   wxPython/Phoenix does not appear to be installed on the system
> Call Stack (most recent call first):
>   CMakeLists.txt:740 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also
> "C:/msys64/home/Msys_bjpic/FixedFormatting/debug/CMakeFiles/CMakeOutput.log".
> 
> See also
> "C:/msys64/home/Msys_bjpic/FixedFormatting/debug/CMakeFiles/CMakeError.log".
> 
> 
> 
> 
> On 2020-05-25 6:55 a.m., jp charras wrote:
>> Le 23/05/2020 à 17:55, jp charras a écrit :
>>> Le 23/05/2020 à 17:35, Wayne Stambaugh a écrit :
>>>> There is definitely something wrong but I'm not sure where the issue
>>>> is.
>>>>   I downgraded both cmake a couple of versions but cmake started
>>>> complaining about missing libraries.  I even modified Findngspice.cmake
>>>> with the absolute path to libngspice-0.dll and it still didn't work so
>>>> something is definitely broken.  I'm may try a full clean reinstall of
>>>> msys2 when I have a *lot* of free time so I don't know when that will
>>>> happen.  For all of you windows devs using msys2, you might want to
>>>> hold
>>>> off updating until this issue is resolved.
>>>>
>>>>
>>> I also tried the last msys version.
>>> I found 2 issues:
>>> this issue: libngspice-0.dll is not found even if it is in path.
>>> This is an issue but one can invoke cmake with option
>>> -DNGSPICE_DLL=<libngspice-0.dll full path>
>>> The other issue is the fact the last msys version comes with
>>> wxWidgets 3.05 compiled with gcc10
>>> but wxPython was not rebuild and there is an ABI issue.
>>>
>>>
>> I just committed a fix for the libngspice-x.dll issue.
>> I am not entirely convinced this is a msys issue.
>> However, the wxPython problem is a msys issue.
>>
> 
> _______________________________________________
> 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